LCP priority hint
The strongest priority signal on the LCP element: preload, fetchpriority, preconnect, or none.
At a glance the headline numbers for LCP priority hint
The strongest priority signal on the LCP element: preload, fetchpriority, preconnect, or none.
86.2% of LCP images get no priority help at all.
LCP priority hint who uses what, and how fast each group loads
Little daylight between the groups: every variant sits near 48ms median INP. computed
Passing INP per LCP priority hint which group passes the INP most often
No variant stands out: pass rates sit between 98% and 99%. computed
Why this matters for the Core Web Vitals, and where to start fixing it
Browsers start most images at low priority, because most images do not matter. The LCP image is the exception, and without help the browser only finds out after layout. fetchpriority=high says it upfront. A preload moves the discovery earlier as well. None means the most important resource on the page starts at the back of the queue.
One hint on one image. Spraying fetchpriority=high across the page puts the queue right back where it started.
How does this affect the Core Web Vitals?
The choice barely moves the LCP: 87% pass at best, 85% at worst. This signal does not separate passing sites from failing ones.
The split is bigger on CLS. With Highprio, 82% of sites pass it. With Preload, 76% do.
Chrome field data from 189,915 sites, representing millions of real page loads. How we measured.