Uncompressed and Non-Lazy-Loaded Images: How They Hurt Indexing and Performance
Key takeawayImages are the largest traffic component on e-commerce and content sites. Uncompressed files hurt transfer and LCP; missing dimensions hurt CLS; lazy-loading done wrong on above-the-fold images slows the first screen. All three point to the same root cause: the image pipeline is not being managed as a performance problem.
When this applies
- Stores with many product images and heavy page payloads
- Sites where CLS fails broadly in the GSC Page Experience report
- Sites clearly slower on mobile than desktop
- Sites using large numbers of uncompressed PNGs or full-resolution originals
| Issue | Direct consequence | Indirect impact | How to fix |
|---|---|---|---|
| Uncompressed / outdated formats | Large transfer payloads | Poor LCP, wasted bandwidth | WebP/AVIF plus sensible compression |
| No width/height or aspect ratio | Layout jumps during loading | CLS failures | Set width/height or aspect-ratio |
| Above-the-fold images not prioritized | Main content appears late | Poor LCP | Preload first-screen images; lazy-load the rest |
| Lazy-loading applied too broadly | Below-fold content appears late | Hurts both UX and crawling | Lazy-load only off-screen resources |
| Missing srcset | Oversized images on mobile | Poor LCP | Provide multiple resolutions with srcset |
| Responsive images without sizes | Different viewports download the same size | Double loss for crawling and UX | srcset plus sizes |
Step-by-step diagnosis
- In GSC's Page Experience report, isolate the URL set failing both CLS and LCP.
- Use PageSpeed Insights Opportunities to locate the specific image problems.
- Add width and height attributes to every <img>, or reserve space with CSS aspect-ratio.
- Switch the first-screen hero image to preload with no lazy-loading; enable lazy-loading only for off-screen images.
- Batch-convert to WebP or AVIF and compress to actual display size (do not serve a 2000px image into a 300px slot).
- Complete srcset and sizes so mobile devices download appropriate sizes.
- Re-test LCP and CLS after compression to confirm the improvement.
Common mistakes
- Adding lazy-loading to every image — delaying the first-screen hero directly worsens LCP.
- Compressing without setting dimensions — payload drops but CLS still fails.
- Using AVIF without fallback formats — some browsers still need WebP/JPEG.
- Turning images into background images — you lose srcset and dimension declarations.
- Optimizing only the homepage without touching templates — the problem lives in the template and repeats on every page.
- Ignoring caching and format support on third-party image domains (CDN image hosts).
FAQ
From which image should lazy-loading start?
The test is "outside the first screen." Above-the-fold images should not be lazy-loaded or LCP gets pushed back. A common pattern is prioritizing 1-2 first-screen images and deferring the rest.
WebP or AVIF — which to choose?
AVIF compresses better but encodes slower and has limited legacy browser support. The robust setup is AVIF + WebP + JPEG tiers delivered via <picture>.
Does setting width/height break responsive design?
No. width/height declare the intrinsic ratio; combined with max-width:100%; height:auto the image reserves space without stretching.
Version notes2026-11-20: first release, compiled from official Google documentation and public technical sources; updated as engine rules change. Engine behaviour details follow the latest official Google documentation.
Related reading
Core Web Vitals: The LCP / CLS / INP Optimization ManualHow Overseas Hosting Latency and Packet Loss Really Affect IndexingWhen CDN Rules Block Crawlers: A Troubleshooting GuideNon-Standard HTTPS Configurations and the Risks They CreateWhere Internal Link Equity Leaks Out: The Common PointsNote: this page is a summary of publicly documented search-engine rules and is for self-check reference only. Engine behaviour is subject to the latest official Google documentation; verify against your own Search Console data.