Audit a page for next/image misuse before Lighthouse catches it

You are auditing every image on a specific page for next/image correctness, checking for the mistakes that hurt Core Web Vitals or fail silently in production without ever showing up as a build error.

PAGE OR COMPONENT CODE
app/blog/[slug]/page.tsx — a hero image plus several inline images inside the post body

EXTERNAL IMAGE DOMAINS
images.ctfassets.net (Contentful), cdn.example-cms.com

LAYOUT BREAKPOINTS
Hero image is full-width on mobile, roughly 60% width on tablet, and capped at 800px on desktop

CHECKLIST
Flag every plain img tag used for a content image, recommending conversion to next/image, unless there's a specific reason not to — an SVG icon, or an image whose dimensions genuinely can't be known ahead of time — and name that reason explicitly if you're leaving one as-is rather than silently skipping it. Identify the largest above-the-fold image, the likely LCP element, and confirm it has priority set to disable lazy loading; if it's currently lazy-loaded by default because priority is missing, flag that as a direct LCP regression at high severity, not a minor style note. Confirm every other next/image usage on the page does NOT have priority set — marking every image priority defeats the entire point of lazy loading and front-loads bandwidth for images the user may never actually scroll down to see. For any image using the fill prop, confirm its parent element has a defined position (relative or similar) and defined dimensions; fill combined with an unsized or statically-positioned parent causes the image to collapse to zero height or overflow its container unpredictably. For any image using explicit width and height instead of fill, confirm those values match, or are proportional to, the actual source image's real aspect ratio — mismatched dimensions cause either a distorted image or a layout shift the moment the real image loads and the browser reserves space based on values that don't match what actually renders. For any image sourced from an external domain, confirm that domain is listed in next.config's images.remotePatterns; flag any that aren't, since an un-allow-listed domain fails at request time in production, not at build time, meaning this specific mistake passes every local check and every CI build cleanly and only surfaces after deploy when a real request to that image actually gets made. For any image that resizes significantly across the breakpoints given above, confirm a sizes attribute is set so the browser downloads an appropriately sized file at each breakpoint rather than the largest variant everywhere regardless of how small the image actually renders on a given screen.

OUTPUT FORMAT
A findings table: Image or location | Issue | Severity — LCP-impacting, CLS-impacting, will-fail-in-prod, or minor | Fix.