PERF-008
The first content image is lazy-loaded
LowDefault severity · Performance · SEO, quality and performance
Last reviewed
What it checks
Images in the same section as the main heading (or marked hero, banner or cover) with loading="lazy".
Why it matters
The image most likely to be the largest element on screen waits until layout before downloading, which delays the Largest Contentful Paint.
Recommended fix
Remove loading="lazy" from the hero image (and add fetchpriority="high").
How to verify
Run Lighthouse and confirm the "LCP image was lazily loaded" warning is gone.
Example fix prompt
Generic prompt (your report adds the evidence)
Please fix this production issue in my app.
Issue PERF-008: The first content image is lazy-loaded
Site: https://your-app.example
First confirm the issue in the code or live config. If it is not present, say so and change nothing.
Task: Remove loading="lazy" from the first above-the-fold image in the evidence and add fetchpriority="high" (with next/image, set priority).
Constraints: make the smallest change that fixes this, keep the current design and behaviour, never paste secret values into code or chat, and tell me which files you changed.
Done when: Run Lighthouse and confirm the "LCP image was lazily loaded" warning is gone.