LCP 3.2s -> 1.7s with one fetchpriority attribute

LCP 3.2s -> 1.7s with one fetchpriority attribute
LCP (largest contentful paint) here was a hero image discovered late by the preload scanner.
— Image sat below two render-blocking stylesheets in source order. Browser fetched it at default priority, behind 4 other requests.
— Added fetchpriority="high" to the LCP img: request started 1100ms earlier in the waterfall.
— No preload tag needed. The byte count (84KB AVIF) never changed.
— Resource load delay: 1400ms -> 260ms. Render delay unchanged at ~400ms.
LCP breaks into 4 sub-parts; load delay was 60% of the total here.
Takeaway: 1.7s LCP, 1.5s saved from request ordering alone.