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 · Desktop 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,713
sites measured
desktop 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 · 196,579 sites · desktop 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 13025 26049
300–737 738–1812 1813–4454 4455–10946 10947–26903 26904–66119 66120–162504 162505–399391 399392–981596 981597–2412500 >p98
Good (≤200ms) Needs improvement Poor (>500ms) Site count
The State of Web Vitals · October 2026 · 196,579 sites · desktop 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,143 100% 50ms
738–1812 682 98% 50ms
1813–4454 1,478 99% 51ms
4455–10946 4,079 99% 49ms
10947–26903 11,994 99% 49ms
26904–66119 23,027 99% 49ms
66120–162504 26,049 99% 48ms
162505–399391 22,044 100% 47ms
399392–981596 13,916 99% 47ms
981597–2412500 5,066 99% 47ms
>p98 2,235 99% 49ms
Good Needs Improvement Poor Faded rows: under 100 sites

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

The State of Web Vitals · October 2026 · 196,579 sites · desktop 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 63ms 125ms 188ms 250ms
200ms
0 9989 19977
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 · 196,579 sites · desktop 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.001–0.002 34 93% 52ms
0.002–0.005 174 94% 55ms
0.005–0.012 438 98% 52ms
0.012–0.029 1,912 98% 48ms
0.029–0.066 5,652 99% 48ms
0.066–0.153 19,977 99% 50ms
0.153–0.354 19,505 99% 50ms
0.354–0.819 12,803 99% 49ms
0.819–1.89 9,585 99% 49ms
1.89–4.38 5,206 99% 50ms
>p98 1,539 99% 51ms
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.001–0.002): INP 52ms. At the high end (>p98): INP 51ms. computed

The State of Web Vitals · October 2026 · 196,579 sites · desktop 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 13427 26854
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 · 196,579 sites · desktop 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.002–0.004 202 98% 51ms
0.004–0.007 792 96% 56ms
0.007–0.014 1,044 96% 52ms
0.014–0.026 2,350 98% 50ms
0.026–0.051 5,187 99% 47ms
0.051–0.097 20,904 99% 47ms
0.097–0.187 26,854 99% 50ms
0.187–0.36 16,087 99% 55ms
0.36–0.693 2,228 98% 48ms
>p98 1,545 100% 51ms
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.002–0.004): INP 51ms. At the high end (>p98): INP 51ms. computed

The State of Web Vitals · October 2026 · 196,579 sites · desktop 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, 73% of sites pass the LCP. Where it is high, 86% 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 196,579 sites, representing millions of real page loads · How we measured