LCP image size

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

Field data PhoneDesktopAll Scope All sites October 2026 edition · All devices field outcomes
Metric LCP INP CLS
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
109,727
sites measured
all-device 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 · October 2026 · 193,102 sites · all devices 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 12773 25546
300–737 738–1812 1813–4454 4455–10946 10947–26903 26904–66122 66123–162510 162511–399409 399410–981645 981646–2412635 >p98
Good (≤200ms) Needs improvement Poor (>500ms) Site count
The State of Web Vitals · October 2026 · 193,102 sites · all devices 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,122 97% 88ms
738–1812 665 96% 88ms
1813–4454 1,467 93% 87ms
4455–10946 4,012 94% 84ms
10947–26903 11,805 95% 86ms
26904–66122 22,597 95% 87ms
66123–162510 25,546 95% 86ms
162511–399409 21,653 97% 85ms
399410–981645 13,668 97% 85ms
981646–2412635 4,997 97% 86ms
>p98 2,195 96% 87ms
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 88ms. At the high end (>p98): INP 87ms. computed

The State of Web Vitals · October 2026 · 193,102 sites · all devices 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 188ms 375ms 563ms 750ms
200ms
500ms
0 9791 19582
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.354 0.354–0.82 0.82–1.9 1.9–4.39 >p98
Good (≤200ms) Needs improvement Poor (>500ms) Site count
The State of Web Vitals · October 2026 · 193,102 sites · all devices 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 152 49% 259ms
0.001–0.002 34 92% 99ms
0.002–0.005 173 82% 97ms
0.005–0.012 433 78% 90ms
0.012–0.029 1,890 94% 84ms
0.029–0.066 5,538 96% 85ms
0.066–0.153 19,582 94% 87ms
0.153–0.354 19,179 94% 87ms
0.354–0.82 12,545 94% 86ms
0.82–1.9 9,401 95% 86ms
1.9–4.39 5,105 96% 87ms
>p98 1,508 95% 89ms
Good Needs Improvement Poor Faded rows: under 100 sites

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

The State of Web Vitals · October 2026 · 193,102 sites · all devices 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 13155 26309
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.361 0.361–0.695 >p98
Good (≤200ms) Needs improvement Poor (>500ms) Site count
The State of Web Vitals · October 2026 · 193,102 sites · all devices 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 88% 86ms
0.002–0.004 198 92% 90ms
0.004–0.007 780 90% 92ms
0.007–0.014 1,020 92% 87ms
0.014–0.026 2,310 95% 86ms
0.026–0.051 5,098 96% 84ms
0.051–0.098 20,529 96% 84ms
0.098–0.188 26,309 95% 87ms
0.188–0.361 15,814 92% 90ms
0.361–0.695 2,175 87% 86ms
>p98 1,520 93% 87ms
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 86ms. At the high end (>p98): INP 87ms. computed

The State of Web Vitals · October 2026 · 193,102 sites · all devices 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, 71% of sites pass the LCP. Where it is high, 83% do. The rise is gradual. The mechanism says more displayed pixels should cost LCP, but the fleet shows the opposite: bigger, better-built sites carry more of it and still pass. The cost is real per site; across sites it is drowned out by who builds them.

Related signals LCP loading attribute → LCP element type → LCP responsive markup → LCP discovery → Chrome field data from 193,102 sites, representing millions of real page loads · How we measured