Check explainer · v1
Image performance: why images shift, bloat and load late
Last reviewed
Images rarely fail loudly. They shift the page, arrive at twice the size they are shown, download megabytes the visitor never scrolls to — or return a 404 nobody notices. Five warning-level grades make each one visible.
How this check works
Five grades run on every rendered page. In-flow images — positioned in the layout and shown at least 16×16 CSS px — need both width and height attributes, or a CSS aspect-ratio, so the browser can reserve their space. A bitmap shown at 200 CSS px or wider without srcset warns when its natural width or height reaches 1.5× the displayed size times the device pixel ratio; SVG is skipped. Weight is graded per file (500 KiB) and across the first 100 sampled images (2 MiB total). Above the first viewport, loading="lazy" warns; below it, an image with neither loading="lazy" nor decoding="async" warns. The fifth grade marks an image broken when its response is 4xx/5xx, or when the element finished complete with naturalWidth 0 after a decode failure. Every grade is a warning and never fails the page; without the local render lane the result is na (insufficient_signal), not a pass.
What does a failure look like?
A hero image with no width, height or aspect-ratio; a 2400 px photo shown at 360 CSS px with no srcset; a gallery whose first 100 images total 3.4 MiB; a below-the-fold grid that sets neither loading nor decoding; a product thumbnail whose file now returns 404 — each finding is a warning, not a failed page.
How to fix it, step by step
- Reserve layout space on every in-flow image with width and height attributes that match its aspect ratio, or a CSS aspect-ratio rule when the size is fluid.
- Ship srcset and sizes for bitmaps shown at 200 CSS px or wider, so the browser can pick a file close to the displayed size at the visitor’s pixel ratio.
- Compress the heaviest files below 500 KiB, keep the first 100 images under 2 MiB in total, and set loading="lazy" plus decoding="async" only on images below the first viewport.
What does a pass or fail look like?
Good
All in-flow images reserve space, the first viewport is eager, the grid below it defers, every sampled image decodes, and the files total 740 KiB.
Fail
A 2,400 px hero is displayed at 360 CSS px with no srcset while the first viewport marks it loading="lazy" — two warnings on one image; a third image returns 404.
Frequently asked questions
Why does this report na instead of pass?
na means the audit had no measurement to judge. When the local render lane is off, the page came from a non-local lane, or byte sizes could not be measured, the grades report na (insufficient_signal); when a rule simply finds no eligible image, it reports na as not applicable. Either way, a missing result is not evidence that the page is fine.
Does the audit download the images?
It reads the images the headless browser fetched while rendering, using the compressed transfer bytes rather than the source file — so an image shrunk by your CDN is judged on what visitors receive. Weight samples the first 100 images; when the list is truncated, the finding says so.
What counts as a broken image?
A sampled image whose response is 4xx/5xx, or an element that finished loading complete with naturalWidth 0 after a decode failure. The audit reports up to five sources per finding; a missing image list reports na (insufficient_signal) rather than pass.
Can an image warning fail the page?
No. All five grades are warning-level: they flag layout-shift, waste, broken files or loading risk without changing a pass/fail verdict. Use them as a ranked fix list, not as blockers.
This rule is one of the checks the page scan runs. Run the free page scan
Free preview; no account needed.