Oversized Image Files

What This Means

One or more images on the page have file sizes significantly above the threshold for their display dimensions. The images are larger than necessary for their rendered size, consuming more bandwidth and adding to the total page weight.

Why It Matters for SEO

Large image files are one of the most common causes of slow page load times. Unoptimized images add hundreds of kilobytes or even megabytes to the total page weight, directly increasing time to first byte, total blocking time, and Largest Contentful Paint (LCP) — a Core Web Vitals metric that Google uses as a page experience ranking signal.

Many sites upload images at their original camera or export resolution (2000px+ wide, multiple megabytes) and rely on CSS to resize them for display. The user still downloads the full-size file even though a much smaller version is displayed.

What the Platform Checks

The platform records the file size of each image fetched during the crawl and compares it against the image's rendered display dimensions. Fires when an image's file size is significantly above the expected size for its display context.

How to Fix It

• Resize: Scale images to their maximum display size — if an image displays at 800px wide, serve it at 800px wide, not 3000px.
• Compress: Use image compression tools (Squoosh, TinyPNG, ImageOptim) to reduce file size without visible quality loss.
• Format: Convert to modern formats — WebP is typically 25-35% smaller than JPEG at equivalent quality.
• Responsive images: Use srcset to serve appropriately sized images for different screen sizes.
• CDN image optimization: CDN services (Cloudflare, Cloudinary, Imgix) can automatically resize, compress, and format-convert images on delivery.