The State of Web Vitals

LCP image size

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

Field data PhoneDesktopAll Scope All sites Q1 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.

100.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
56,633
sites measured
phone field data

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

The State of Web Vitals · Q1 2026 · 94,910 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 6537 13074
300–738 739–1814 1815–4460 4461–10966 10967–26963 26964–66297 66298–163013 163014–400821 400822–985550 985551–2423300 >p98
Good (≤200ms) Needs improvement Poor (>500ms) Site count
The State of Web Vitals · Q1 2026 · 94,910 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–738 569 96% 103ms
739–1814 331 91% 99ms
1815–4460 725 87% 104ms
4461–10966 2,079 89% 99ms
10967–26963 6,117 93% 99ms
26964–66297 11,864 93% 100ms
66298–163013 13,074 94% 96ms
163014–400821 11,138 95% 95ms
400822–985550 7,005 96% 94ms
985551–2423300 2,598 95% 95ms
>p98 1,133 94% 98ms
Good Needs Improvement Poor Faded rows: under 100 sites

LCP image size — bytes 100.4 KB. p75 290.3 KB. p99 3.6 MB. At the low end (300–738): INP 103ms. At the high end (>p98): INP 98ms. computed

The State of Web Vitals · Q1 2026 · 94,910 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 5032 10063
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.818 0.818–1.89 1.89–4.38 >p98
Good (≤200ms) Needs improvement Poor (>500ms) Site count
The State of Web Vitals · Q1 2026 · 94,910 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 84 46% 538ms
0.001–0.002 20 92% 110ms
0.002–0.005 86 83% 124ms
0.005–0.012 233 72% 117ms
0.012–0.029 904 90% 97ms
0.029–0.066 2,897 92% 96ms
0.066–0.153 10,063 92% 99ms
0.153–0.354 9,980 92% 100ms
0.354–0.818 6,482 91% 99ms
0.818–1.89 4,802 93% 97ms
1.89–4.38 2,592 93% 99ms
>p98 783 92% 104ms
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 538ms. At the high end (>p98): INP 104ms. computed

The State of Web Vitals · Q1 2026 · 94,910 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 6979 13957
0 0.001–0.002 0.002–0.004 0.004–0.007 0.007–0.014 0.014–0.026 0.026–0.05 0.05–0.097 0.097–0.186 0.186–0.357 0.357–0.687 >p98
Good (≤200ms) Needs improvement Poor (>500ms) Site count
The State of Web Vitals · Q1 2026 · 94,910 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.002–0.004 98 83% 113ms
0.004–0.007 420 90% 112ms
0.007–0.014 511 86% 99ms
0.014–0.026 1,193 92% 98ms
0.026–0.05 2,632 92% 96ms
0.05–0.097 10,116 93% 95ms
0.097–0.186 13,957 93% 100ms
0.186–0.357 8,182 90% 104ms
0.357–0.687 1,136 85% 99ms
>p98 782 91% 100ms
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 113ms. At the high end (>p98): INP 100ms. computed

The State of Web Vitals · Q1 2026 · 94,910 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, 69% of sites pass the LCP. Where it is high, 82% do. The rise is gradual.

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 94,910 sites, representing millions of real page loads · How we measured