What it is
Loading every image eagerly, including those far down the page, competes for bandwidth with the content people see first. Below-fold images should load only as they approach the viewport. All images load eagerly. Wastes bandwidth, slows initial load. Add loading=“lazy” below the fold (not on LCP image).
Why does no lazy-loading on below-fold images matter for AI search?
Wastes bandwidth, slows initial load.
How do you fix it?
Add loading=“lazy” below the fold (not on LCP image).
How do you find it on your site?
- Check whether below-fold images use loading=lazy.
- Confirm above-fold and LCP images stay eager, since lazy loading them would hurt.
- Add loading=lazy to images below the fold.
- Re-test that the LCP image is not accidentally lazy-loaded.
Which ranking and citation factors does it touch?
Deferring off-screen images frees bandwidth for the initial view, helping LCP. Just avoid lazy-loading the LCP image itself.
What is the impact?
Low. Inferred.
What is the evidence?
Lazy-load below-fold media for performance. web.dev, Core Web Vitals (Google)
Frequently asked questions about no lazy-loading on below-fold images
What does "No lazy-loading on below-fold images" mean?
All images load eagerly.
How do you fix no lazy-loading on below-fold images?
Add loading=“lazy” below the fold (not on LCP image).