Will It Vibe?Raw <img> instead of next/image
Part of Code Quality & Syntax, which counts for 20% of the overall score. When this check fires it deducts 4 points from that category, once per scan, no matter how many places it turns up.
What it detects
A plain <img> tag skips the next/image pipeline, so the image is not resized, lazy-loaded, or served in a modern format. On image-heavy pages this hurts Largest Contentful Paint and total bytes.
Why it matters
A plain <img> tag bypasses next/image, so the browser downloads the image at its full original size and format with no automatic lazy loading. On pages with several images this measurably worsens Largest Contentful Paint and total transfer size, which hurts both users on slow connections and Core Web Vitals scores.
How to fix it
Replace the <img> with the next/image component, import Image from "next/image", and provide width and height (or the fill prop with a sized parent). For images whose dimensions are unknown ahead of time, use fill with a container that has a defined aspect ratio.
The paid report includes a ready-to-paste prompt for your AI coding agent for every check it finds, pointed at the exact findings from your scan. See pricing
Does your repo trip this check?
Paste a GitHub URL or drop a project folder. Scans run in your browser and take seconds.
Scan your repo