How blanket lazy loading regressed LCP from 2.2s to 3.5s and the fixes applied

Short summary

A developer shares how blanket lazy loading on all images caused LCP to regress from 2.2s to 3.5s on mobile. The hero image, always in the initial viewport, was flagged as lazy and fetched hundreds of milliseconds late. Fixing it required removing loading=lazy from above-the-fold images and adding explicit width/height attributes to prevent layout shift, recovering LCP to 2.3-2.5s.

• •Blanket loading=lazy on hero images caused LCP regression from 2.2s to 3.5s on mobile
• •Three mistakes: lazy loading above-the-fold images, missing width/height attributes, no fetchpriority
• •Fix: remove lazy from hero, add explicit dimensions, recover LCP to 2.3-2.5s

Generated with AI, which can make mistakes.