diagnostic · one of 50 24-hour trial, then Pro
Images
Why is my page so heavy?
Images are usually most of a page’s weight and almost never most of its attention. This lists every one with the numbers that matter - what was downloaded against what is displayed - and ranks them by the gap, so the worst offender is at the top rather than somewhere in a waterfall.
Reach it Press ⌘ + K on any tab and type images. Ctrl + K on Windows and Linux
in the panel · 24-hour trial, then Pro
What this actually is
Before optimising anything, so effort goes where the bytes are, and after a redesign, when a component quietly starts rendering a hero image at thumbnail size while still downloading all of it.
Asked about this diagnostic
It flags an image that looks fine.
It is fine to look at and twice the size it needs to be. The reading is about bytes, not appearance - an 1800px file painted into a 400px box looks perfect and costs four times what it should.
Does it account for retina screens?
Yes. The threshold is against the rendered size times your device pixel ratio, so a 2× file on a 2× screen is correct and is not flagged.
Can it convert the images for me?
No. It tells you which ones and by how much; the conversion belongs in your build, where it happens once instead of on every request.
Why is the saving an estimate?
Because the browser only reports a transfer size for resources it fetched over the network this load. Anything served from cache is measured by dimensions alone, and the row says which of the two it used.
how to use images
- Open Images and let it sort by wasted bytes, descending.
- Read natural size against rendered size on the top row. That gap is the whole reading.
- Anything over twice its rendered size is flagged, so start there rather than in a waterfall.
- Use the overlay to find the element on the page before you change the markup.
written about at length
- layout 6 min What moves a page after it has loaded Layout shift is reported as one number and caused by one element. What actually moves a page after first paint, and how to name the element that did it.
- accessibility 7 min How to check a website for accessibility in ten minutes A ten-minute accessibility check: an automated scan, a keyboard pass, 400% zoom, contrast, headings, alt text and form labels, mapped to WCAG 2.2.
- layout 4 min Why srcset keeps picking the wrong image The sizes attribute is a promise about layout, made before layout exists. Get it wrong and a 200px avatar downloads the 1600px file on every device.
101 of these · no host permissions · 24 hours of all of them