The typical LCP image ships 101.4 KB over the wire

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

107,873

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 · Q2 2026 · 189,915 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 12556 25112

300–737 738–1810 1811–4448 4449–10926 10927–26840 26841–65934 65935–161973 161974–397901 397902–977476 977477–2401253 >p98

Good (≤200ms) Needs improvement Poor (>500ms) Site count

The State of Web Vitals · Q2 2026 · 189,915 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,099 100% 50ms

738–1810 657 98% 50ms

1811–4448 1,439 99% 51ms

4449–10926 3,947 99% 49ms

10927–26840 11,569 99% 49ms

26841–65934 22,158 99% 49ms

65935–161973 25,112 99% 48ms

161974–397901 21,309 100% 47ms

397902–977476 13,473 99% 47ms

977477–2401253 4,952 99% 47ms

>p98 2,158 99% 48ms

Good Needs Improvement Poor Faded rows: under 100 sites

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

The State of Web Vitals · Q2 2026 · 189,915 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 9610 19220

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.355 0.355–0.822 0.822–1.9 1.9–4.4 >p98

Good (≤200ms) Needs improvement Poor (>500ms) Site count

The State of Web Vitals · Q2 2026 · 189,915 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 168 94% 54ms

0.005–0.012 425 98% 52ms

0.012–0.029 1,865 98% 49ms

0.029–0.066 5,454 99% 48ms

0.066–0.153 19,220 99% 50ms

0.153–0.355 18,862 99% 50ms

0.355–0.822 12,346 99% 49ms

0.822–1.9 9,252 99% 49ms

1.9–4.4 5,000 99% 50ms

>p98 1,483 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.8 MP. At the low end (0.001–0.002): INP 52ms. At the high end (>p98): INP 51ms. computed

The State of Web Vitals · Q2 2026 · 189,915 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 12929 25857

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.098 0.098–0.188 0.188–0.362 0.362–0.696 >p98

Good (≤200ms) Needs improvement Poor (>500ms) Site count

The State of Web Vitals · Q2 2026 · 189,915 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 192 98% 51ms

0.004–0.007 761 96% 57ms

0.007–0.014 999 96% 52ms

0.014–0.026 2,277 98% 50ms

0.026–0.051 5,005 99% 47ms

0.051–0.098 20,230 99% 47ms

0.098–0.188 25,857 99% 50ms

0.188–0.362 15,506 99% 55ms

0.362–0.696 2,148 98% 48ms

>p98 1,492 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 · Q2 2026 · 189,915 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.

Go fix it Optimize the LCP image → LCP: resource load duration → Optimize images for Core Web Vitals →