MediumPerformance

Images Not Served in Modern Format (WebP/AVIF)

Serving images as PNG or JPEG instead of WebP/AVIF means every image is 2-3× larger than it needs to be for supported browsers. Performance issues directly affect user retention and search rankings. This issue contributes to higher bounce rates, lower conversion, and poorer Core Web Vitals scores that disadvantage your app in Google search results.

What This Issue Means for Your App

Serving images as PNG or JPEG instead of WebP/AVIF means every image is 2-3× larger than it needs to be for supported browsers.

AI coding tools generate working code but do not optimize the output for delivery performance. Images are full resolution, JavaScript bundles are maximal, and caching is never configured — all creating a performance gap between development and production excellence.

Google's Core Web Vitals have been a confirmed ranking factor since 2021, and user expectations for load times continue to rise. Mobile users in particular are highly sensitive to performance — 53% abandon pages that take over three seconds to load, according to Google's own research. The specific manifestation of this issue in your app depends on how your codebase is structured, but the detection and remediation steps below apply to the overwhelming majority of vibe-coded applications.

The Real-World Consequences

“PNG → WebP conversion typically saves 25-35% file size. JPEG → WebP saves 25-34%. For image-heavy pages, this adds up to seconds of load time savings.”

Sites with this performance issue have measurably higher bounce rates than those that have fixed it. The issue does not remain theoretical once your app has real users — whether it is a security vulnerability that gets exploited, an SEO gap that limits discovery, or a performance problem that increases churn, the business impact is measurable and preventable.

The urgency of addressing this issue scales with your user count. A pre-launch app can fix issues without any user impact. A live app needs to balance fix speed with deployment risk — which is why having automated monitoring (like Pantra's daily scans) to catch these issues before launch is far preferable to discovering them after.

Why Vibe Coders Hit This Issue

Design tools export PNG and JPEG — converting to WebP requires an extra step developers typically skip when adding images directly to /public.

This is not a reflection of developer skill — it is a reflection of what AI coding tools optimize for. Lovable, Cursor, Bolt.new, v0, and Replit are all excellent at generating functional, working code. They are not designed to output security-hardened, SEO-optimized, production-ready applications by default. That gap is the reason tools like Pantra exist.

The solution is not to slow down your vibe coding workflow — it is to add systematic, automated checking that runs faster than you can build. A Pantra security scan takes under 60 seconds and catches issues that would otherwise take hours to find manually.

How to Detect This Issue

Before fixing, confirm whether this issue exists in your app. Use these detection methods to verify the current state:

1
Lighthouse → "Serve images in next-gen formats"
2
DevTools Network → filter by images → check Content-Type (image/png vs image/webp)

The fastest detection method is running a Pantra audit on your URL — the scan automatically checks for this and hundreds of other issues in under 60 seconds, providing severity-rated findings with specific fix prompts for your stack.

Step-by-Step Fix

Once confirmed, address this issue in the following order. Each step builds on the previous one — completing all steps ensures complete remediation rather than partial patching.

1
Use Next.js <Image> component — it automatically serves WebP to supported browsers
2
For images outside Next.js Image: convert manually using Sharp or Squoosh
3
Add images.formats: ["image/avif", "image/webp"] to next.config.js

After completing these steps, re-run your Pantra audit to verify the finding has been resolved. The daily monitoring feature will then alert you if the issue ever reappears due to a future code change.

Copy-Paste Fix Prompt

Copy this prompt directly into Lovable, Cursor, Claude, or ChatGPT to get an immediate, stack-specific fix for this issue. The prompt is designed to be precise enough to produce actionable code without requiring additional context.

Fix Prompt — paste into your AI coding tool

Convert all images in my app to be served as WebP. Replace <img> tags with Next.js Image components. Configure next.config.js to serve AVIF and WebP. Show how to convert existing /public images.

Pro tip: If you have Pantra's daily monitoring enabled, each finding in your scan report comes with a pre-generated fix prompt tailored to your detected tech stack — no copy-pasting required.

Frequently Asked Questions

Do all browsers support WebP?

WebP is supported by 97%+ of browsers as of 2025. AVIF is at 95%. Both are safe to use with fallbacks — Next.js handles this automatically.

How does Pantra detect this issue automatically?

Pantra's audit engine runs over 177 checks across Security, SEO, GEO, and Performance categories. This issue is detected by analyzing your app's HTTP responses, JavaScript bundle content, HTML structure, and configuration signals — all within a single scan that takes under 60 seconds.

What stack-specific fix prompts does Pantra provide?

Pantra detects your tech stack (Lovable, Cursor, Next.js, Bolt, etc.) and generates fix prompts tailored to that stack. The prompt above is a general version — Pantra's stack-specific prompts include exact file paths, component names, and framework-specific syntax for your project.

These issues frequently appear together with images not served in modern format (webp/avif). Addressing them as a group is more efficient than fixing each in isolation.

Poor Largest Contentful Paint (LCP)

High

Large Unoptimized Images

High

Below-Fold Images Not Lazy Loaded

Medium

Images Oversized for Their Display Size