LCP image size

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

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

0.1 MP
Median (p50)
74,584 sites
0.2 MP
p75
1.0 MP
p99
Long tail
The State of Web Vitals · Q2 2026 · 189,915 sites · phone field datacorewebvitals.io/state-of-cwv
2

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

0.00 0.04 0.08 0.11 0.15
0.1
0 36874 73748
0–0 1+
Good (≤0.1) Needs improvement Poor (>0.25) Site count
The State of Web Vitals · Q2 2026 · 189,915 sites · phone field datacorewebvitals.io/state-of-cwv
3

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

LCP image size — rendered mpSitesPassing CLSCLS
0–0 73,748 89% 0.00
1+ 836 83% 0.00
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–0): CLS 0.00. At the high end (1+): CLS 0.00. computed

The State of Web Vitals · Q2 2026 · 189,915 sites · phone field datacorewebvitals.io/state-of-cwv
4

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.

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