Why it matters
Next 16 replaced priority with preload; the docs recommend loading="eager" or fetchPriority="high" for the LCP image in most cases. Deprecated props are removed in later majors and agents copy them forward.
How to fix it
For the single LCP image use fetchPriority="high" + loading="eager" (or preload). Don't combine preload with loading/fetchPriority, and mark at most one image per route.
Example
<Image src={hero} alt="…" fill sizes="100vw" fetchPriority="high" loading="eager" />References
More lint rules
void lint reports 67 rules in this category. Static source checks with no browser: Tailwind v4 silent failures, Next.js 16 API traps, React render-body bugs, accessibility markup, SEO files and motion hygiene.
page-level-use-client`"use client"` at the top of a page or layoutheavy-importHeavy dependency imported into client codeimg-rawRaw `<img>` in a Next.js appimg-missing-dimensionsImage without width/height (or fill / aspect-ratio)missing-altImage without `alt`google-fonts-linkGoogle Fonts loaded via `<link>` / `@import`font-display`@font-face` without `font-display`too-many-font-familiesMore than 3 font families loaded