The typical LCP image ships 101.4 KB over the wire

1

At a glance the headline numbers for LCP image size

The LCP element: transfer size and natural / rendered pixel size.

101.4 KB

transfer size

on the typical page

0.2 MP

file pixels

on the typical page

0.1 MP

displayed pixels

on the typical page

107,873

sites measured

phone field data

The typical LCP image ships 101.4 KB over the wire. It carries 0.2 MP for 0.1 MP actually shown.

The State of Web Vitals · Q2 2026 · 189,915 sites · phone field datacorewebvitals.io/state-of-cwv

2

Distribution & median INP site count and median INP at each level of LCP image size — bytes

0ms 63ms 125ms 188ms 250ms

200ms

0 12556 25112

300–737 738–1810 1811–4448 4449–10926 10927–26840 26841–65934 65935–161973 161974–397901 397902–977476 977477–2401253 >p98

Good (≤200ms) Needs improvement Poor (>500ms) Site count

The State of Web Vitals · Q2 2026 · 189,915 sites · phone field datacorewebvitals.io/state-of-cwv

3

Passing INP by LCP image size — bytes which level passes the INP most often

LCP image size — bytesSitesPassing INPINP

300–737 1,099 96% 101ms

738–1810 657 92% 99ms

1811–4448 1,439 89% 104ms

4449–10926 3,947 89% 101ms

10927–26840 11,569 93% 99ms

26841–65934 22,158 93% 100ms

65935–161973 25,112 93% 97ms

161974–397901 21,309 95% 95ms

397902–977476 13,473 96% 95ms

977477–2401253 4,952 96% 96ms

>p98 2,158 94% 97ms

Good Needs Improvement Poor Faded rows: under 100 sites

LCP image size — bytes 101.4 KB. p75 290.5 KB. p99 3.4 MB. At the low end (300–737): INP 101ms. At the high end (>p98): INP 97ms. computed

The State of Web Vitals · Q2 2026 · 189,915 sites · phone field datacorewebvitals.io/state-of-cwv

4

Distribution & median INP site count and median INP at each level of LCP image size — natural mp

0ms 250ms 500ms 750ms 1000ms

200ms

500ms

0 9610 19220

0 0.001–0.002 0.002–0.005 0.005–0.012 0.012–0.029 0.029–0.066 0.066–0.153 0.153–0.355 0.355–0.822 0.822–1.9 1.9–4.4 >p98

Good (≤200ms) Needs improvement Poor (>500ms) Site count

The State of Web Vitals · Q2 2026 · 189,915 sites · phone field datacorewebvitals.io/state-of-cwv

5

Passing INP by LCP image size — natural mp which level passes the INP most often

LCP image size — natural mpSitesPassing INPINP

0 150 42% 763ms

0.001–0.002 34 85% 118ms

0.002–0.005 168 78% 126ms

0.005–0.012 425 70% 120ms

0.012–0.029 1,865 90% 97ms

0.029–0.066 5,454 93% 97ms

0.066–0.153 19,220 92% 99ms

0.153–0.355 18,862 92% 100ms

0.355–0.822 12,346 91% 99ms

0.822–1.9 9,252 93% 97ms

1.9–4.4 5,000 94% 99ms

>p98 1,483 92% 103ms

Good Needs Improvement Poor Faded rows: under 100 sites

LCP image size — natural mp 0.2 MP. p75 0.7 MP. p99 7.8 MP. At the low end (0): INP 763ms. At the high end (>p98): INP 103ms. computed

The State of Web Vitals · Q2 2026 · 189,915 sites · phone field datacorewebvitals.io/state-of-cwv

6

Distribution & median INP site count and median INP at each level of LCP image size — rendered mp

0ms 63ms 125ms 188ms 250ms

200ms

0 12929 25857

0 0.001–0.002 0.002–0.004 0.004–0.007 0.007–0.014 0.014–0.026 0.026–0.051 0.051–0.098 0.098–0.188 0.188–0.362 0.362–0.696 >p98

Good (≤200ms) Needs improvement Poor (>500ms) Site count

The State of Web Vitals · Q2 2026 · 189,915 sites · phone field datacorewebvitals.io/state-of-cwv

7

Passing INP by LCP image size — rendered mp which level passes the INP most often

LCP image size — rendered mpSitesPassing INPINP

0.001–0.002 24 70% 134ms

0.002–0.004 192 89% 104ms

0.004–0.007 761 86% 110ms

0.007–0.014 999 88% 101ms

0.014–0.026 2,277 92% 98ms

0.026–0.051 5,005 93% 96ms

0.051–0.098 20,230 93% 95ms

0.098–0.188 25,857 93% 101ms

0.188–0.362 15,506 90% 104ms

0.362–0.696 2,148 83% 98ms

>p98 1,492 91% 102ms

Good Needs Improvement Poor Faded rows: under 100 sites

LCP image size — rendered mp 0.1 MP. p75 0.2 MP. p99 1.0 MP. At the low end (0.001–0.002): INP 134ms. At the high end (>p98): INP 102ms. computed

The State of Web Vitals · Q2 2026 · 189,915 sites · phone field datacorewebvitals.io/state-of-cwv

8

Why this matters for the Core Web Vitals, and where to start fixing it

Three numbers describe the LCP image: the bytes over the wire, the pixels in the file, and the pixels actually shown. The gap between the last two is pure waste. An image with far more natural pixels than rendered pixels shipped resolution nobody saw, and the extra bytes stretched the load time.

Right-size first, then compress, then pick the format. Resizing the image to what is displayed saves more than recompressing a wrong-sized original ever will.

How does the weight of the LCP image affect the LCP?

LCP image size correlates with the LCP. Displayed pixels separates passing sites from failing sites the most. Where the displayed pixels is low, 70% of sites pass the LCP. Where it is high, 83% do. The rise is gradual.

Go fix it Optimize the LCP image → LCP: resource load duration → Optimize images for Core Web Vitals →