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 INP site count and median INP at each level of images per page — n

0ms 63ms 125ms 188ms 250ms
200ms
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 (≤200ms) Needs improvement Poor (>500ms) Site count
The State of Web Vitals · Q2 2026 · 189,915 sites · all devices field datacorewebvitals.io/state-of-cwv
3

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

Images per page — nSitesPassing INPINP
0–4 27,940 91% 86ms
5–9 19,827 94% 80ms
10–14 22,004 96% 82ms
15–19 21,116 96% 83ms
20–24 18,466 96% 85ms
25–29 15,032 96% 86ms
30–34 12,107 96% 87ms
35–39 9,509 96% 88ms
40–44 7,471 96% 89ms
45–49 5,905 96% 89ms
50–54 4,805 95% 92ms
55–59 3,828 94% 93ms
60–64 3,097 94% 94ms
65+ 19,023 93% 98ms
Good Needs Improvement Poor Faded rows: under 100 sites

Images per page — n 21. p75 38. p99 177. At the low end (0–4): INP 86ms. At the high end (65+): INP 98ms. computed

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

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

0ms 63ms 125ms 188ms 250ms
200ms
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 (≤200ms) Needs improvement Poor (>500ms) Site count
The State of Web Vitals · Q2 2026 · 189,915 sites · all devices field datacorewebvitals.io/state-of-cwv
5

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

Images per page — sizeSitesPassing INPINP
0–499 58,179 92% 85ms
500–999 30,515 95% 86ms
1000–1499 20,139 95% 86ms
1500–1999 14,364 96% 87ms
2000–2499 10,613 96% 87ms
2500–2999 7,879 96% 87ms
3000–3499 6,229 96% 87ms
3500–3999 4,909 97% 87ms
4000–4499 4,071 96% 87ms
4500–4999 3,170 96% 87ms
5000–5499 2,836 97% 87ms
5500–5999 2,359 97% 87ms
6000–6499 1,999 96% 88ms
6500+ 18,176 96% 89ms
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): INP 85ms. At the high end (6500+ KB): INP 89ms. 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.

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