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
phone field data
The typical page serves 21 images weighing 1.1 MB.
The State of Web Vitals · Q2 2026 · 189,915 sites · phone 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
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 · phone 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 85% 104ms
5–9 19,827 91% 92ms
10–14 22,004 93% 92ms
15–19 21,116 94% 94ms
20–24 18,466 94% 95ms
25–29 15,032 94% 96ms
30–34 12,107 94% 98ms
35–39 9,509 94% 100ms
40–44 7,471 95% 102ms
45–49 5,905 93% 104ms
50–54 4,805 93% 104ms
55–59 3,828 91% 107ms
60–64 3,097 91% 108ms
65+ 19,023 89% 113ms
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 104ms. At the high end (65+): INP 113ms. computed
The State of Web Vitals · Q2 2026 · 189,915 sites · phone 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
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 · phone 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 88% 101ms
500–999 30,515 93% 97ms
1000–1499 20,139 93% 97ms
1500–1999 14,364 93% 98ms
2000–2499 10,613 94% 97ms
2500–2999 7,879 94% 98ms
3000–3499 6,229 94% 99ms
3500–3999 4,909 95% 98ms
4000–4499 4,071 94% 97ms
4500–4999 3,170 94% 98ms
5000–5499 2,836 96% 98ms
5500–5999 2,359 95% 97ms
6000–6499 1,999 93% 101ms
6500+ 18,176 94% 101ms
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 101ms. At the high end (6500+ KB): INP 101ms. computed
The State of Web Vitals · Q2 2026 · 189,915 sites · phone 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.
Chrome field data from 189,915 sites, representing millions of real page loads. How we measured.