The typical LCP image ships 100.4 KB over the wire

LCP INP CLS

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

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

0ms 750ms 1500ms 2250ms 3000ms

2.5s

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 (≤2.5s) Needs improvement Poor (>4s) Site count

The State of Web Vitals · Q1 2026 · 94,910 sites · phone field datacorewebvitals.io/state-of-cwv

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

LCP image size — bytesSitesPassing LCPLCP

300–738 569 68% 2.0s

739–1814 331 82% 1.6s

1815–4460 725 81% 1.5s

4461–10966 2,079 83% 1.5s

10967–26963 6,117 85% 1.5s

26964–66297 11,864 85% 1.5s

66298–163013 13,074 83% 1.5s

163014–400821 11,138 80% 1.6s

400822–985550 7,005 77% 1.7s

985551–2423300 2,598 76% 1.7s

>p98 1,133 75% 1.8s

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): LCP 2.0s. At the high end (>p98): LCP 1.8s. computed

The State of Web Vitals · Q1 2026 · 94,910 sites · phone field datacorewebvitals.io/state-of-cwv

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

0ms 750ms 1500ms 2250ms 3000ms

2.5s

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 (≤2.5s) Needs improvement Poor (>4s) Site count

The State of Web Vitals · Q1 2026 · 94,910 sites · phone field datacorewebvitals.io/state-of-cwv

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

LCP image size — natural mpSitesPassing LCPLCP

0 84 59% 2.1s

0.001–0.002 20 80% 1.5s

0.002–0.005 86 78% 1.4s

0.005–0.012 233 76% 1.8s

0.012–0.029 904 81% 1.5s

0.029–0.066 2,897 84% 1.5s

0.066–0.153 10,063 85% 1.5s

0.153–0.354 9,980 86% 1.4s

0.354–0.818 6,482 85% 1.5s

0.818–1.89 4,802 84% 1.5s

1.89–4.38 2,592 80% 1.6s

>p98 783 80% 1.7s

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): LCP 2.1s. At the high end (>p98): LCP 1.7s. computed

The State of Web Vitals · Q1 2026 · 94,910 sites · phone field datacorewebvitals.io/state-of-cwv

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

0ms 750ms 1500ms 2250ms 3000ms

2.5s

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 (≤2.5s) Needs improvement Poor (>4s) Site count

The State of Web Vitals · Q1 2026 · 94,910 sites · phone field datacorewebvitals.io/state-of-cwv

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

LCP image size — rendered mpSitesPassing LCPLCP

0.002–0.004 98 69% 1.9s

0.004–0.007 420 69% 1.8s

0.007–0.014 511 76% 1.6s

0.014–0.026 1,193 80% 1.5s

0.026–0.05 2,632 82% 1.5s

0.05–0.097 10,116 84% 1.5s

0.097–0.186 13,957 85% 1.5s

0.186–0.357 8,182 87% 1.5s

0.357–0.687 1,136 86% 1.4s

>p98 782 82% 1.6s

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): LCP 1.9s. At the high end (>p98): LCP 1.6s. computed

The State of Web Vitals · Q1 2026 · 94,910 sites · phone field datacorewebvitals.io/state-of-cwv

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