Images per page
How many images the page renders and their over-the-wire weight.
At a glance the headline numbers for Images per page
How many images the page renders and their over-the-wire weight.
The typical page serves 22 images weighing 1.1 MB.
Distribution & median CLS site count and median CLS at each level of images per page — n
Passing CLS by images per page — n which level passes the CLS most often
Images per page — n 22. p75 39. p99 178.9. At the low end (0): CLS 0.00. At the high end (>p98): CLS 0.00. computed
Distribution & median CLS site count and median CLS at each level of images per page — size
Passing CLS by images per page — size which level passes the CLS most often
Images per page — size 1.1 MB. p75 2.8 MB. p99 26.8 MB. At the low end (0 KB): CLS 0.00. At the high end (>p98): CLS 0.00. computed
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, 81% of sites pass the LCP. Where it is high, 72% do. The decline is gradual. There is no point where sites suddenly start failing.
Chrome field data from 94,910 sites, representing millions of real page loads. How we measured.