Image Weight Is Still the Number One Speed Problem
We run speed audits regularly, and the finding is monotonous: a homepage weighing eight megabytes, of which seven and a half are photos uploaded straight from a phone or a stock library at print resolution. The browser downloads all of it and then displays it at 800 pixels wide.
The three numbers to fix
- Dimensions. No image needs to be wider than about 2,000 pixels for a full-bleed background, 1,600 for a content image, or 800 for anything in a column. Resize before uploading.
- Format. WebP or AVIF instead of JPEG or PNG, typically 25 to 50% smaller at the same visual quality. Most platforms convert automatically now; confirm yours does.
- Compression. Quality 75 to 85 is indistinguishable from 100 for photographs and often half the size.
The techniques that matter after that
- Lazy loading for anything below the fold, so the browser fetches images as the visitor scrolls. Do not lazy load the hero image; that delays the one thing you want fast.
- Responsive images, so phones download phone-sized files. Most modern themes handle this; verify by loading a page on mobile and checking which file was requested.
- Explicit width and height so the layout does not jump as images arrive. Layout shift is both a ranking signal and a genuine annoyance.
Where the weight hides
Sliders and galleries load every slide whether or not anyone views it. Background images set in CSS skip most optimization pipelines. Logos exported as PNG at 3,000 pixels are common. And PDFs linked from the page do not slow the page, but a 40MB brochure will lose you the visitor who taps it on cellular data.
How to check yours
Open your homepage, open the browser's network panel, reload, and sort by size. The largest few files are your entire problem. On most small business sites, fixing the top five images cuts total page weight in half, and it takes about an hour with no design changes and no developer.
