Your Images Are Too Big, and Someone Is Paying for That

The Size Problem Nobody Talks About

Nobody looks at a 6MB PNG and thinks "that's a problem." It's just a file sitting in a folder. It looks normal. You upload it, it shows up on your page, and everything seems fine on your 500Mbps home connection.

But image weight is the single biggest contributor to slow page loads, and slow page loads have real consequences—not just for your bounce rate, but for the people trying to use your site.

Not everyone has a fast connection. Not everyone is on WiFi. There are people visiting your site on mobile data plans with monthly limits, people in parts of the world where bandwidth is expensive and slow, people on older devices that struggle with large file transfers. When you serve a 6MB image to those people, you've made a choice on their behalf. You've decided that your unoptimized image is worth 6MB of their monthly data allowance.

I hope it was worth it.

The Fix Is Not Complicated

This is the part that genuinely surprises people: optimizing your images doesn't require a build pipeline, a Node.js script, a CDX configuration, or anything particularly technical. You just need the right tool.

The tool I use—and have used for years—is XnConvert. It's free. It's a proper desktop GUI. You drag your images in, pick your output format, and hit convert. That's it. No command line required. No setup. No dependencies to manage. Just a tool that does one thing well.

XnConvert is available on Windows, Mac, and Linux!

Why WebP

My format of choice is WebP, and I'm not going back. Converting a PNG to WebP can reduce file size by 25–50% at equivalent quality — and in cases where you're starting from a large, unoptimized PNG, you can see reductions well beyond that. I have personally watched files shrink dramatically. Same image, same quality to the human eye, a fraction of the weight.

WebP is supported everywhere that matters now. I have never, not once, had an issue with a WebP image failing to load in a modern browser. The format has been around long enough that the "but what about browser support?" concern is essentially a non-issue.

The Workflow

Here's how simple this is in practice:

That's the whole thing. You can batch convert an entire folder of images in one go. XnConvert also gives you options for resizing, quality settings, metadata stripping, and more—but changing the format to WebP is often all you need to do.

A Note on Caching

Caching is great. HTTP caching, CDN caching, browser caching—all of it is worth doing, and I'm not here to talk you out of it. But caching has a ceiling.

The first time someone visits your site, there is no cache. They're loading everything cold. And every time you update an image, the cache busts and they're loading it fresh again. Caching is a speed multiplier—but if the underlying file is 6MB, you're multiplying something that's already slow. Optimize the image first. Then cache it.

Above the Fold

While we're here—and this deserves its own post—image optimization is part of a larger conversation about page weight. Your page's "above the fold" content (everything visible before the user scrolls) needs to load first. Your user cannot see the JavaScript console. They cannot see the network tab. They can only see the screen, and if the screen is blank because you're loading a 6MB image before anything else renders, they're going to leave.

Don't load unused JavaScript. If you have to load it, defer it. Make sure the content that matters most loads first, and make sure that content is small enough to load fast. Images are the bulk of the work. Get those right, and you're most of the way there.

Go Optimize Your Images

You'd be surprised—or maybe you wouldn't—by how many sites, including some from organizations that really should know better, serve completely unoptimized images. Giant PNGs. Multi-megabyte JPEGs. Files that were clearly just uploaded straight from a camera or a design tool and never touched again.

It takes maybe ten minutes to run your images through XnConvert. There is no good excuse not to. Your users—especially the ones with slower connections and limited data—will notice the difference, even if they don't know why. Fast sites feel respectful. Slow sites feel careless. Which one do you want to be?

Key Takeaways