Images per page

How many images the page renders and their over-the-wire weight.

Field data PhoneDesktopAll Scope All sites Q2 2026 edition · All devices field outcomes
Metric LCP INP CLS
1

At a glance the headline numbers for Images per page

How many images the page renders and their over-the-wire weight.

21
image count
on the typical page
1.1 MB
image weight
on the typical page
2.8 MB
1 in 4 pages exceed this
image weight
190,130
sites measured
all-device field data

The typical page serves 21 images weighing 1.1 MB.

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

Distribution & median LCP site count and median LCP at each level of images per page — n

0ms 750ms 1500ms 2250ms 3000ms
2.5s
0 13970 27940
0–4 5–9 10–14 15–19 20–24 25–29 30–34 35–39 40–44 45–49 50–54 55–59 60–64 65+
Good (≤2.5s) Needs improvement Poor (>4s) Site count
The State of Web Vitals · Q2 2026 · 189,915 sites · all devices field datacorewebvitals.io/state-of-cwv
3

Passing LCP by images per page — n which level passes the LCP most often

Images per page — nSitesPassing LCPLCP
0–4 27,940 84% 1.4s
5–9 19,827 87% 1.3s
10–14 22,004 85% 1.4s
15–19 21,116 84% 1.5s
20–24 18,466 83% 1.5s
25–29 15,032 82% 1.5s
30–34 12,107 82% 1.6s
35–39 9,509 81% 1.6s
40–44 7,471 81% 1.6s
45–49 5,905 80% 1.6s
50–54 4,805 79% 1.7s
55–59 3,828 79% 1.7s
60–64 3,097 80% 1.7s
65+ 19,023 77% 1.7s
Good Needs Improvement Poor Faded rows: under 100 sites

Images per page — n 21. p75 38. p99 177. At the low end (0–4): LCP 1.4s. At the high end (65+): LCP 1.7s. computed

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

Distribution & median LCP site count and median LCP at each level of images per page — size

0ms 750ms 1500ms 2250ms 3000ms
2.5s
0 29090 58179
0–499 500–999 1000–1499 1500–1999 2000–2499 2500–2999 3000–3499 3500–3999 4000–4499 4500–4999 5000–5499 5500–5999 6000–6499 6500+
Good (≤2.5s) Needs improvement Poor (>4s) Site count
The State of Web Vitals · Q2 2026 · 189,915 sites · all devices field datacorewebvitals.io/state-of-cwv
5

Passing LCP by images per page — size which level passes the LCP most often

Images per page — sizeSitesPassing LCPLCP
0–499 58,179 86% 1.3s
500–999 30,515 85% 1.5s
1000–1499 20,139 83% 1.5s
1500–1999 14,364 82% 1.6s
2000–2499 10,613 81% 1.6s
2500–2999 7,879 79% 1.6s
3000–3499 6,229 78% 1.7s
3500–3999 4,909 78% 1.7s
4000–4499 4,071 79% 1.7s
4500–4999 3,170 76% 1.7s
5000–5499 2,836 77% 1.7s
5500–5999 2,359 77% 1.7s
6000–6499 1,999 78% 1.7s
6500+ 18,176 75% 1.8s
Good Needs Improvement Poor Faded rows: under 100 sites

Images per page — size 1.1 MB. p75 2.8 MB. p99 26.3 MB. At the low end (0–499 KB): LCP 1.3s. At the high end (6500+ KB): LCP 1.8s. computed

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

Why this matters for the Core Web Vitals, and where to start fixing it

Image count and image weight are the bulk of most pages. Those bytes compete with the LCP image for bandwidth: the browser downloads gallery thumbnails while the hero is still streaming. More images also means more decode work, and decoding is not free on a cheap phone.

Fewer, smaller, later. Cut the decorative ones, right-size the rest, lazy-load below the fold. The format and loading splits in the explorer show where to start.

How do images affect the Core Web Vitals?

Images per page correlates with the LCP. Image weight separates passing sites from failing sites more than image count does. Where the image weight is low, 86% of sites pass the LCP. Where it is high, 75% do. The decline is gradual. There is no point where sites suddenly start failing.

Related signals Iframes per page → Bytes by resource type → Stylesheet loading mix → Iframe loading → Chrome field data from 189,915 sites, representing millions of real page loads · How we measured