Images per page

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

Field data PhoneDesktopAll Scope All sites Q2 2026 edition · Desktop 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
desktop field data

The typical page serves 21 images weighing 1.1 MB.

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 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 · desktop 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 97% 49ms
1–2 8,792 97% 49ms
3 7,196 98% 48ms
4 3,604 98% 49ms
5–7 11,587 98% 46ms
8–12 21,249 99% 45ms
13–19 30,042 99% 46ms
20–32 41,024 99% 47ms
33–52 30,382 99% 49ms
53–85 16,603 99% 54ms
86–139 7,554 99% 58ms
>p98 3,556 99% 59ms
Good Needs Improvement Poor Faded rows: under 100 sites

Images per page — n 21. p75 38. p99 177. At the low end (0): INP 49ms. At the high end (>p98): INP 59ms. 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 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 · desktop 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 97% 49ms
0.1–0.337 211 93% 48ms
0.337–1.13 314 98% 56ms
1.13–3.82 1,006 97% 57ms
3.82–12.9 2,715 98% 50ms
12.9–43.4 4,692 98% 49ms
43.4–146 10,282 98% 47ms
146–492 29,495 99% 48ms
492–1656 56,165 99% 49ms
1656–5579 49,479 99% 49ms
5579–18792 18,553 99% 49ms
>p98 3,529 99% 50ms
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 49ms. At the high end (>p98): INP 50ms. computed

The State of Web Vitals · Q2 2026 · 189,915 sites · desktop 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?

Passing LCP barely moves across the range: 83% at one end, 81% at the other. This signal does not separate passing sites from failing ones.

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