Image Lazy Loading
Checks that below-the-fold images use loading="lazy" while above-the-fold do not.
What this check measures
We count images with and without `loading="lazy"`. Above-the-fold (LCP candidates) must NOT be lazy — lazy LCP images become slower. Below-the-fold SHOULD be lazy.
Why it matters
Correct lazy loading cuts initial page weight 50-80% on image-heavy sites. Wrong lazy (on LCP image) makes LCP hit the 2.5s threshold much harder.
How our audit detects it
Count <img> tags with and without loading="lazy". Flag hero images with lazy and below-the-fold images without.
Typical findings
- error_outlineHero image has loading="lazy" — LCP suffers.
- error_outlineAll 40 product thumbnails load eagerly — first paint delayed.
How to fix
Lazy-load everything below the fold. Add `loading="eager"` (or nothing) on the LCP element. Also add `fetchpriority="high"` on the LCP image for a boost.
Frequently asked questions
Is native lazy well-supported?expand_more
Want this checked on your site?
Pantra runs the full audit (SEO, Security, GEO, Performance, Schema, Technical, Images) in 10 seconds and generates stack-specific fix prompts.
Scan my siteRelated checks
SSR / Pre-rendering
Checks if the page is server-rendered or statically pre-rendered.
TechnicalHTTP Status Codes
Checks that pages return proper status codes — 200 for live, 404 for missing, 301 for moved.
TechnicalNo Client-Side Redirects
Checks that redirects happen server-side, not via JavaScript.
TechnicalViewport Meta Tag
Checks for <meta name="viewport" content="width=device-width, initial-scale=1">.