Will It Vibe?Image optimization disabled globally
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
images.unoptimized: true turns off the next/image optimizer for the whole app, so every image is served at its original size and format. This defeats the main reason to use next/image and inflates page weight.
Why it matters
images.unoptimized: true disables the next/image optimizer for the entire application, so every image is served at its original resolution and format with no responsive sizing. This removes the main benefit of using next/image and inflates page weight across the whole site, not just one component.
How to fix it
Remove the global unoptimized: true setting. If a specific static export or single image genuinely cannot be optimized, set unoptimized only on that individual <Image> component rather than for all images. Make sure a loader or the default optimizer is configured for your deployment target.
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