
Image Handling: Why It Wrecks Your Page Speed
Oversized images are the single biggest cause of slow, ugly pages. Here's how to format, size and serve them correctly, no plugins required.
Open your site's network tab and sort by file size. Most of the time, the biggest items on the page are images, usually by a wide margin. A single unoptimised photo can be heavier than every line of CSS, JavaScript and HTML combined.
This is the quiet cause behind most "why is my site slow" complaints. Not the hosting. Not the framework. The images.
The good news is that image handling is one of the most fixable problems on the web. You don't need a developer to make real progress, just an understanding of what's actually going wrong.
Why images cause the damage they do
A modern phone camera produces images that are 12 megapixels or larger, often 3-5MB per file straight out of the camera roll. A web page rarely needs to display an image larger than 1,500-2,000 pixels wide. If you upload the camera-original file to your CMS and drop it into a page, the browser downloads the full multi-megabyte file and then shrinks it down with CSS, wasting almost all of that download.
Multiply that by five or six images on a single page, and you've built a page that has to pull down 15-20MB before it's even usable. On a mobile connection, that's seconds of waiting, sometimes much longer, and every second of delay affects Core Web Vitals scores and, with them, your search ranking signals. Google has published Core Web Vitals as part of its ranking systems for years now, so slow images are not just a UX problem, they're an SEO problem too.
There's also a layout problem that has nothing to do with file size. If an image doesn't have a width and height (or an aspect-ratio) defined in the HTML, the browser doesn't know how much space to reserve for it while it loads. The rest of the page jumps around as images pop in. This is measured directly as Cumulative Layout Shift, one of the three Core Web Vitals, and it's almost always an image problem.
If you want the fuller picture of what else affects load times, the sub-2-second performance playbook covers the rest of the stack. Images are just the part that's usually worst.
The fixes you can do yourself today
Resize before you upload. Most image editors, including free ones, let you export at a specific pixel width. Match the image's export size to the largest size it will actually display at on your page. A hero banner that's 1,600px wide on screen doesn't need a 4,000px source file.
Use a compressed, modern format. JPEG and PNG are still common, but WebP and AVIF produce smaller files at equivalent visual quality, and both are supported by every major browser released in the last several years. Many image editing tools and CMS platforms can export directly to WebP now. If yours can't, free online converters exist, and compressing a batch of images takes minutes.
Compress even after resizing. Resizing alone isn't enough. Run images through a compression pass, lossy compression at 70-85% quality is usually visually indistinguishable from the original but can cut file size dramatically. Most CMS platforms and photo editors have this built in as an export slider.
Set explicit width and height attributes. In plain HTML this looks like <img src="..." width="1600" height="900">. In most page builders there's an equivalent field. This single change stops the layout jump that CLS measures, even before you've touched file size.
Use loading="lazy" on anything below the fold. This is a native browser attribute, no plugin needed, that tells the browser to skip downloading images until the user scrolls near them. It's supported in all current major browsers. It won't help your largest hero image, which should load eagerly, but it meaningfully cuts initial page weight on long pages.
Serve the right image for the device. A desktop hero image doesn't need to be the same file sent to a phone screen that's a third of the width. The srcset and sizes attributes let the browser choose from several sizes automatically. If your CMS supports responsive images natively, turn that setting on. If you're hand-coding, this is worth the extra markup.
Checking your own work
You don't need expensive tools to audit this.
- Open any page in Chrome, right-click, choose Inspect, go to the Network tab, reload, and sort by size. Images at the top of that list, measured in megabytes rather than kilobytes, are your priority list.
- Run the page through Google's PageSpeed Insights. It will flag "Properly size images" and "Serve images in next-gen formats" by name if either is a problem, with specific savings estimates per image.
- Check the Cumulative Layout Shift score in the same report. A high score with images on the page almost always points back to missing width/height attributes.
Fix the three or four heaviest images on your homepage first. That's usually where most of the damage is concentrated, since homepages tend to accumulate hero banners, logo strips and decorative photography over time.
Where this connects to the rest of your site
Image weight rarely travels alone. Pages with oversized, unoptimised images are often the same pages that haven't been touched structurally in years, the kind of site that also has brittle mobile layouts or accessibility gaps. If you're reviewing images, it's worth checking your mobile layout against 2026 expectations and your WCAG 2.1 AA accessibility checklist at the same time, since missing alt text on images is one of the most common accessibility failures found in audits.
None of the fixes above require rebuilding your site. They're edits you can make to the images you already have, one page at a time, with free tools.
If you'd rather not do this page by page, SOSEI rebuilds sites from an existing URL and handles image sizing, formats and layout as part of that process, then keeps it current on a subscription as standards shift. But even if that's not on your radar right now, resizing and compressing your heaviest images this week is a genuinely useful afternoon's work.