The State of Web Image Optimization 2026

June 26, 2026·44 sites tested

We loaded 44 popular websites in a real headless browser and measured every image's natural (file) size against its rendered (on-screen) size — the same measurement our scanner runs. The picture is consistent with what we see on individual scans every day: oversized images are the norm, not the exception.

Key findings

• 68% of the 44 sites we tested shipped at least one image whose file is 4× or more the area it actually renders at — beyond any reasonable retina (2×) allowance.
• 45% of all measurable images (visible images with known natural dimensions) were oversized by that same bar.
• The median site's worst single image overshot its display size by 15× in area — often the hero or banner, which is frequently the Largest Contentful Paint element.
• Pages carry a median of 58 images, so a handful of oversized ones is easy to miss without a per-image audit.

Oversized images by segment

Share of sites in each category that shipped at least one oversized image. Smaller segments (shown with their site count) are indicative only.

Government and media/blog sites fared worst. Both tend to publish image-heavy pages through CMSes that upload at full camera/source resolution and resize only with CSS — the exact pattern that produces oversized images.

Format adoption (by file extension)

Across every image we collected, by the extension in the URL:

Even read generously, legacy JPG and PNG still dominate explicit URLs, and AVIF — the most efficient widely-supported format — is essentially absent from extension-declared images. There is a large, unclaimed bandwidth saving sitting in format choice alone.

Why this matters

An image downloaded much larger than it displays costs transfer, decode time, and memory — and when it is the LCP element, it directly drags Core Web Vitals on mobile. The fix is mechanical: right-size to the actual display dimensions, add srcset, and convert to a modern format. We cover the full workflow in this writeup.

Methodology

• 60 popular websites were selected across eight segments; 44 returned usable data (the remainder timed out or returned bot-challenge pages and were excluded).
• Each homepage was loaded in a real headless Chrome at 1366×900. We recorded every <img> and CSS background image with its natural and rendered dimensions.
• "Oversized" means natural area ≥ 4× rendered area (roughly 2× per dimension — beyond a 2×-retina allowance). Only visible images with known natural dimensions are counted as "measurable."
• All figures are aggregate. No individual site is named, and detectable oversizing is a performance observation, not a judgment of any specific site.

Citing this report? Please attribute to "Image Dimensions Analyzer (2026)" and link to this page. Every figure is "of the 44 sites we tested."