Research · Auto repair
The image file that is larger than needed
On 4,208 of the 6,606 websites we analyzed, the largest homepage image was flagged as a larger file than needed. Because not every homepage had a usable image result, 64% is a conservative minimum.
The largest homepage image was bigger than it needed to be.
This is not an argument for removing useful photographs. The problem is the file delivered to the visitor: an image can look the same while making the connection carry more data than the page needs.
The format matters too
Among the 5,028 websites with a usable issue result, 2,734 used a legacy format instead of WebP or AVIF for the largest image. One image could carry two labels, so this overlaps with the larger-file result rather than forming a separate group.
How we got these numbers
We used the latest accessible homepage result for valid websites belonging to businesses categorized as auto repair and counted every website once for each distinct issue on its largest image.
There were 6,606 eligible websites. A usable largest-image issue was available for 5,028, or 76.1%. We excluded two records where the estimated saving exceeded the original image size. The headline divides the 4,208 confirmed larger-file results by all 6,606 eligible websites, making it a lower bound.
An honest limitation: these are the businesses we chose to analyze, not a random sample of the industry. An image may carry two issue labels, and a label does not quantify the exact change a repair would make to loading time or a performance score.
What to do about it
- Start with the largest homepage image. One file is faster to inspect than an entire media library.
- Match the file to its display size. Avoid sending more pixels than the page can show.
- Use an efficient format. WebP or AVIF may reduce file weight while preserving the photograph.
- Compare before and after. Keep the smallest file that still looks right on the page.