The State of Web Vitals

Images per page

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

Field data PhoneDesktopAll Scope All sites Q2 2026 edition · Phone 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
189,915
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
200ms
0 20512 41024
0 1–2 3 4 5–7 8–12 13–19 20–32 33–52 53–85 86–139 >p98
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 8,326 81% 118ms
1–2 8,792 85% 104ms
3 7,196 86% 101ms
4 3,604 89% 93ms
5–7 11,587 90% 92ms
8–12 21,249 93% 91ms
13–19 30,042 94% 93ms
20–32 41,024 94% 96ms
33–52 30,382 94% 102ms
53–85 16,603 91% 109ms
86–139 7,554 90% 114ms
>p98 3,556 85% 119ms
Good Needs Improvement Poor Faded rows: under 100 sites

Images per page — n 21. p75 38. p99 177. At the low end (0): INP 118ms. At the high end (>p98): INP 119ms. 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
200ms
0 28083 56165
0 0.1–0.337 0.337–1.13 1.13–3.82 3.82–12.9 12.9–43.4 43.4–146 146–492 492–1656 1656–5579 5579–18792 >p98
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 8,782 84% 111ms
0.1–0.337 211 86% 93ms
0.337–1.13 314 86% 112ms
1.13–3.82 1,006 80% 122ms
3.82–12.9 2,715 82% 107ms
12.9–43.4 4,692 82% 106ms
43.4–146 10,282 87% 100ms
146–492 29,495 91% 96ms
492–1656 56,165 93% 97ms
1656–5579 49,479 94% 98ms
5579–18792 18,553 94% 101ms
>p98 3,529 93% 102ms
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 KB): INP 111ms. At the high end (>p98): INP 102ms. 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.

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, 80% of sites pass the LCP. Where it is high, 74% do. The decline is gradual. There is no point where sites suddenly start failing.

Go fix it Optimize images for Core Web Vitals → Defer offscreen images → Page speed on a budget →
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