Hero image missing fetchpriority=high: LCP fix

What it means

The first significant <img> in the page body — the likely LCP element — has no fetchpriority="high" attribute. Without the hint the browser assigns the image a default network priority, so it can queue behind other resources and delay the LCP paint.

Why it matters

The preload scanner discovers the LCP image early, but it then competes for bandwidth with scripts, stylesheets and other images at default priority. Google's LCP optimisation guidance recommends fetchpriority="high" on the LCP image to promote it in the resource queue; the attribute exists specifically for cases where the browser cannot infer that an image matters more than its peers. This is a low-severity nudge, not a measured regression.

How to fix it

1. Add fetchpriority="high" to the hero <img> element.
2. Confirm the image also has explicit width and height to prevent layout shift.
3. Do not apply fetchpriority="high" to more than one or two images per page — overuse dilutes the signal.

When it's not a problem

fetchpriority is a hint, not a requirement, and its absence is not a failure. Pages whose LCP element is text, a CSS background, or a video poster gain nothing from it on an <img>. Crawlinx applies the same first-content-image heuristic as images.no_lazy_lcp_candidate; where that image is not the true LCP, this notice can be ignored.

How common is it?

10204 audited sites in our corpus currently show this issue. The breakdowns below show which platforms, gatekeepers, verticals and countries are most exposed.