WordPress Image Optimisation Plugins: Which Ones Are Worth It
Images are almost always the heaviest thing on a WordPress page. Get them wrong and your site loads slowly regardless of what else you've done right. There are dozens of plugins claiming to fix this, and most of them overlap badly. Some genuinely help. Others just add weight to the admin side without doing much to the actual files. This is a plain look at which wordpress image optimisation plugins are worth installing, and where the real work actually sits.
On this page
Why Plugins Alone Won’t Solve It
A plugin can automate compression and convert formats. What it can’t do is fix an image that was uploaded at four times the size it needs to be. If someone drops a 4,000-pixel-wide photo onto a page where it displays at 800 pixels, no plugin fully recovers that. The best results come from getting the source file close to right before the plugin ever touches it.
That said, a solid plugin handles the tedious work automatically, and for most sites it makes a real difference. The question is which one, not whether.
ShortPixel: Still the Most Consistent
ShortPixel has been around long enough to be genuinely trusted. It compresses on upload, converts to WebP, and lets you bulk-process your existing media library. The free tier covers 100 images a month, which is fine for a small site. Beyond that you buy credits rather than paying a monthly subscription, which suits smaller operations who don’t want recurring costs for something that’s mostly a one-off task.
The lossy compression is good. Aggressive, but rarely noticeable on photographs at normal display sizes. For logos and flat graphics, switch it to lossless and leave it there. One setting that’s easy to miss, make sure it’s also processing your thumbnails, not just the full-size original. WordPress generates several versions of every image, and they all need compressing.
If you want to understand what the plugin is actually doing to your files under the surface, there’s more detail on what these tools tend to overlook that’s worth reading alongside this.
Imagify: Clean Interface, Good WebP Handling
Imagify is built by the same team behind WP Rocket, so it integrates cleanly if you’re already using that for caching. The free plan gives you 25MB of optimisation per month, which runs out quickly on an active site. The paid plans are subscription-based, so the cost compounds over time.
Where it earns its place is WebP delivery. It serves WebP to browsers that support it and falls back to the original for those that don’t, all without you configuring anything manually. For sites that haven’t touched their image formats yet, that alone tends to cut file sizes noticeably.
Smush: Popular, but Worth Knowing Its Limits
Smush is one of the most installed image plugins in the WordPress directory. It’s free, it’s well-supported, and it works. But the free version doesn’t convert to WebP and doesn’t use the most aggressive compression algorithms available. You get decent results on JPEGs but you’re not squeezing everything out of the files.
The pro version adds WebP and lazy loading, but at that price point you’re competing with ShortPixel credits, which go further for most sites. Smush is fine if you want something free and hands-off. Just know that it’s not the strongest tool in the box.
Lazy Loading: Built Into WordPress Now
WordPress has had native lazy loading since version 5.5. For most sites, that means you don’t need a plugin for this specific feature. Images below the fold load only when a visitor scrolls toward them, which cuts the initial page weight significantly.
Where a plugin still helps is in making sure lazy loading is applied consistently, including on images added through page builders or custom blocks that sometimes bypass the default behaviour. Check your site with the browser’s network tab open and filter by images. If everything loads at once on a long page, something is overriding the default. That’s the kind of thing worth digging into rather than assuming the plugin handled it. For a broader look at file size, format choices and lazy load working together, that covers the full picture.
The One Plugin Combination Worth Considering
Running two image plugins at once is usually a mistake. They compress the same files twice, conflict on WebP generation, and make it harder to diagnose problems. Pick one compression tool and stick with it.
If speed is a priority across the whole site, pairing a compression plugin with a caching plugin that handles critical CSS and deferred scripts does more than stacking multiple image tools. Images are important, but they’re one part of a larger picture. A site that’s getting faster without adding yet more plugins is often doing the right things at the server and code level, not just the media library.
What’s Not Worth Bothering With
Any plugin that promises to optimise images entirely on your server, without an external API, is worth treating with caution. Local compression is slower, uses your hosting resources, and typically doesn’t achieve the same file size reductions as a dedicated image processing service. The good plugins send files to an external API, compress them properly, and return the result. That’s not a concern, it’s how the better tools work.
Also skip anything that bundles image optimisation as a side feature inside a bloated multi-purpose plugin. You end up carrying a lot of overhead for one feature you actually needed.