Responsive Images Architecture: AVIF, WebP, srcset & Zero-CLS Ratios
Serving desktop 2400px JPEGs to mobile devices ruins LCP while omitted dimensions trigger cumulative layout shifts across product grids.
Dmitry K., Technical SEO Lead · SEO Space
Indexation benchmark targets
- Modern codecs
- AVIF -> WebP -> JPEG
- Hero LCP sizing
- < 100 KB mobile
Matching Byte Size to Device Viewport with srcset & sizes
Shipping a single 400 KB desktop hero photo to every mobile visitor inflates Time to First Paint and bloats LCP p75 across cellular networks.
Pairing `<picture>` source negotiation (AVIF first, WebP fallback) with precise `srcset` width descriptors and `sizes` media conditions guarantees each viewport downloads optimal byte budgets.
<picture>
<source type="image/avif" srcset="/img/hero-480.avif 480w, /img/hero-960.avif 960w" sizes="(max-width: 768px) 100vw, 960px" />
<img src="/img/hero-960.webp" width="960" height="540" fetchpriority="high" decoding="async" alt="Architecture overview" />
</picture> Eliminating CLS & Preserving Google Images Crawling
Always include intrinsic `width` and `height` HTML attributes (or CSS `aspect-ratio`) alongside meaningful `alt` text and clean `<img>` fallback `src` URLs for Googlebot Image.
- Never use `loading="lazy"` on the hero LCP image or top visible above-the-fold cards.
- Keep standard descriptive filenames and an accessible JPEG/WebP `<img src>` fallback inside `<picture>`.
- Ensure ImageObject JSON-LD references canonical high-resolution >=1200px wide variants.
Image Format & Loading Policy Matrix
Apply consistent encoding and fetch priority rules across hero banners, catalog grids, and article diagrams.
| Slot Type | Format Stack | Loading & Priority |
|---|---|---|
| Hero LCP Banner | AVIF + WebP fallback | eager + fetchpriority="high" |
| Above-Fold Product Grid | AVIF + WebP fallback | eager + explicit aspect ratio |
| Below-Fold Diagrams | AVIF / lossless WebP | loading="lazy" + width/height |
Need this indexation setup audited on your domain?
Send your website URL. We check raw HTML parity, log crawl hits, canonical discipline, and sitemap architecture manually within 24 hours.