LCP 2.9s -> 1.5s by un-lazy-loading one image

LCP 2.9s -> 1.5s by un-lazy-loading one image
A portfolio site set loading="lazy" on every image — including the hero, which was the LCP element.
— Lazy-loaded LCP images get deprioritized; the hero waited until layout settled.
— Removed lazy from above-fold, kept it below-fold, added fetchpriority="high" on the hero.
LCP image request start: 1,300ms | 180ms
p75 LCP: 2.9s | 1.5s
Takeaway: blanket lazy-loading cost 1,120ms on the one image you most want eager.