The State of Web Vitals

LCP image size

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

Field data PhoneDesktopAll Scope All sites October 2026 edition · Phone 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
111,007
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 · October 2026 · 195,336 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 12931 25862
300–737 738–1811 1812–4451 4452–10937 10938–26874 26875–66036 66037–162265 162266–398721 398722–979744 979745–2407443 >p98
Good (≤200ms) Needs improvement Poor (>500ms) Site count
The State of Web Vitals · October 2026 · 195,336 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,137 96% 101ms
738–1811 676 92% 100ms
1812–4451 1,473 89% 104ms
4452–10937 4,058 89% 101ms
10938–26874 11,914 93% 99ms
26875–66036 22,860 93% 100ms
66037–162265 25,862 93% 97ms
162266–398721 21,906 95% 95ms
398722–979744 13,842 96% 94ms
979745–2407443 5,058 96% 96ms
>p98 2,221 94% 97ms
Good Needs Improvement Poor Faded rows: under 100 sites

LCP image size — bytes 101.4 KB. p75 290.2 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 · October 2026 · 195,336 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 188ms 375ms 563ms 750ms
200ms
500ms
0 9922 19843
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.819 0.819–1.89 1.89–4.38 >p98
Good (≤200ms) Needs improvement Poor (>500ms) Site count
The State of Web Vitals · October 2026 · 195,336 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 153 44% 621ms
0.001–0.002 34 85% 118ms
0.002–0.005 173 78% 126ms
0.005–0.012 436 69% 121ms
0.012–0.029 1,903 90% 97ms
0.029–0.066 5,623 93% 97ms
0.066–0.153 19,843 92% 99ms
0.153–0.354 19,420 92% 100ms
0.354–0.819 12,668 91% 99ms
0.819–1.89 9,521 93% 97ms
1.89–4.38 5,175 94% 99ms
>p98 1,529 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.7 MP. At the low end (0): INP 621ms. At the high end (>p98): INP 103ms. computed

The State of Web Vitals · October 2026 · 195,336 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 13327 26653
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.097 0.097–0.187 0.187–0.36 0.36–0.693 >p98
Good (≤200ms) Needs improvement Poor (>500ms) Site count
The State of Web Vitals · October 2026 · 195,336 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 200 89% 104ms
0.004–0.007 786 86% 111ms
0.007–0.014 1,039 88% 101ms
0.014–0.026 2,335 92% 98ms
0.026–0.051 5,156 93% 96ms
0.051–0.097 20,772 93% 95ms
0.097–0.187 26,653 93% 101ms
0.187–0.36 15,992 89% 104ms
0.36–0.693 2,220 83% 98ms
>p98 1,538 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 · October 2026 · 195,336 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. 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.

Go fix it Optimize the LCP image → LCP: resource load duration → Optimize images for Core Web Vitals →
Related signals LCP loading attribute → LCP element type → LCP responsive markup → LCP discovery → Chrome field data from 195,336 sites, representing millions of real page loads · How we measured