Images are the heaviest part of most WordPress pages: one uncompressed phone photo can weigh 5 MB, and a gallery page can easily pass 20 MB. If you want to optimize WordPress images properly, you do not need to be a developer or buy expensive software — the right workflow cuts image weight by 60–80% while keeping photos sharp.
This guide shows you how to optimize WordPress images step by step — resizing, formats, compression, WebP and AVIF, lazy loading, and CDN delivery — plus a comparison of the best plugins. Combine all seven steps, and you get the fastest way to optimize WordPress images on any budget.
In this guide
- Why images slow down WordPress sites
- Step 1: Resize before upload
- Step 2: Choose the right format
- Step 3: Compress without losing quality
- Step 4: Convert to WebP and AVIF
- Step 5: Enable lazy loading
- Step 6: Serve images through a CDN
- Step 7: Clean up your media library
- Best plugins compared
- Optimize without a plugin
- Measure the results
- Common mistakes
- FAQ

Why Images Slow Down WordPress Sites
Every image is a file the visitor’s browser must download. A 2,000-word blog post is roughly 15 KB of text, while one unoptimized hero photo can be 300 times heavier. With several large images, the browser spends most of its time downloading pictures instead of showing content.
Google’s Largest Contentful Paint (LCP) metric is very often an image — usually the hero image. A slow LCP hurts your rankings and your visitors’ patience, and bounce rates climb sharply past three seconds. That is why you should optimize WordPress images before anything else: heavy images are the most common cause of slow WordPress sites.
The problem starts before WordPress is involved. Phone cameras now produce files of 4–8 MB, and uploading them directly is the single biggest image mistake owners make. The fix is a repeatable workflow that takes a few minutes per article.
How to Optimize WordPress Images in 7 Steps
Follow them in order to cover size, format, compression, loading, and delivery.
Step 1: Resize Images Before You Upload Them
Resizing is the first step when you optimize WordPress images, and it costs nothing. An image only needs to be as wide as the space it will fill on screen. Most WordPress content areas are 700–1,200 pixels wide, so a 4,000-pixel-wide photo is roughly four times larger than it needs to be.
A hero image rarely needs more than 1,920 pixels wide; in-content images are fine at 1,200, thumbnails at 300–600. Resize with tools you already have — Photos or Paint on Windows, Preview on Mac — or a free browser tool such as Squoosh, which resizes and compresses in one step.
Resizing a 5 MB phone photo to 1,600 pixels wide typically brings it under 500 KB before you even compress it.
Step 2: Choose the Right Image Format
The format you choose decides how much quality you get per kilobyte. Using the wrong format can double or triple a file’s size for no visible benefit.
JPEG suits photographs: at quality 80–85, compression is invisible to most eyes. PNG suits logos, icons, and graphics with transparency — but avoid it for photos, where files run far larger than JPEG.
WebP beats both JPEG and PNG in most cases: a WebP photo is typically 25–35% smaller than the same JPEG at equal quality, supports transparency like PNG, and works in all modern browsers. AVIF compresses even better than WebP, often 30–50% smaller than JPEG, but browser support is not yet universal — use it alongside WebP or JPEG fallbacks.
Photographs go to JPEG or WebP; graphics and logos go to PNG or WebP. If you want to optimize WordPress images for the best possible speed in 2026, WebP should be your default format, with AVIF as a bonus where your plugin supports it.

Step 3: Compress Images Without Ruining Quality
Compression removes data from an image file to make it smaller. Lossless compression changes no pixels, but saves only 5–20%. Lossy compression discards some data — how JPEG works — and cuts file size by 60–80% with no visible difference on screen. Most WordPress sites should use lossy compression for photographs.
The sweet spot is quality 80–85. Below 70, blocky artifacts appear in skies and gradients; above 90, the file grows fast for almost no visible gain. Always keep your originals and compress copies for the web. Before bulk changes to your media library, read our WordPress backup guide first.

Step 4: Convert Images to WebP and AVIF
When you optimize WordPress images, converting to WebP is the easiest speed win after resizing. Because WebP files are 25–35% smaller than equivalent JPEGs, a site that switches formats can shed a third of its image weight overnight.
WordPress has supported WebP uploads since version 5.8. The catch is that your existing JPEG and PNG uploads stay in their old formats unless you convert them. Most plugins bulk-convert your whole library to WebP in one run, with a JPEG fallback for older browsers.
AVIF works the same way, but fewer plugins support it — enable it as an extra format, not a replacement. Converting formats does not fix an oversized image: a 4,000-pixel WebP is still far heavier than a 1,200-pixel JPEG, so resize first.
Step 5: Enable Lazy Loading
Lazy loading is a simple way to optimize WordPress images for perceived speed: the browser loads only the images visible on screen, and fetches the rest as the visitor scrolls. Images below the fold load only when needed, which speeds up the initial load — especially for long articles.
WordPress has included native lazy loading since version 5.5, adding loading="lazy" to images automatically. Two details matter. First, your hero image should not be lazy-loaded — delaying it hurts Largest Contentful Paint. Second, always set width and height attributes on your images. Without them, the page layout jumps around as images load, which is measured as Cumulative Layout Shift (CLS).
Step 6: Serve Images Through a CDN
A CDN is the final step to optimize WordPress images for global visitors: it stores copies on servers worldwide and serves each visitor from the nearest one. If your hosting server is in Europe and a reader is in Australia, a CDN can cut image delivery time by more than half.
Many plugins include or integrate with a CDN; Cloudflare’s free plan caches your images at edge locations worldwide. Some plugins, such as Optimole, go further and resize images on the fly for each visitor’s screen.
You do not need a CDN on day one, but once traffic grows it is one of the cheapest speed upgrades available. For the other speed levers that work alongside image optimization, see our guide on how to speed up WordPress.
Step 7: Clean Up Your Media Library
WordPress keeps every image you have ever uploaded, including duplicates and unused files. Once a quarter, run a cleanup: use a plugin such as Media Cleaner to find unattached images and delete the ones you do not need.
Also limit thumbnail sizes: every upload creates several copies, and themes and plugins add their own. Go to Settings → Media in your dashboard and set the sizes you do not use to zero. A clean library makes it easier to optimize WordPress images going forward, so delete original full-size files you never display — if you keep backups elsewhere.
Best Image Optimization Plugins Compared
You could do every step above by hand, but a good plugin automates the repetitive parts: bulk compression, WebP conversion, lazy loading, and resizing on upload. Here is how the leading options compare.
| Plugin | Free plan | Paid plans from | WebP | AVIF | Best for |
|---|---|---|---|---|---|
| Smush | Unlimited images under 5 MB each | Pro via WPMU DEV membership — see the official pricing page for current rates | Pro only | Pro only | Free basic compression on any size library |
| ShortPixel | 100 credits per month | $9.99/month Unlimited ($8.33/month billed yearly); one-time packs from $19.99 | Yes | Yes | Best quality per kilobyte; flexible one-time packs |
| Imagify | 20 MB per month | $4.99/month billed yearly ($5.99 month-to-month), Growth plan | Yes | Yes | Simplest setup; pairs with WP Rocket |
| EWWW Image Optimizer | Unlimited local compression | $8/month ($80/year), Standard plan | Yes | Paid CDN only | Free unlimited compression, no quotas |
| Optimole | 2,000 visits per month, CDN and AVIF included | $22.90/month for 48,000 visits | Yes | Yes | All-in-one optimization plus CDN |
ShortPixel counts one credit per image, thumbnail, and WebP or AVIF copy, so 100 free credits cover roughly five or six photo uploads — which is why the $19.99 one-time pack of 30,000 credits is popular. EWWW is the only plugin here that compresses entirely on your own server, with no monthly quota — but your host needs the right image tools installed. Smush is the most installed, with over one million active installations, but WebP and AVIF need Pro.
For a small blog, EWWW’s or Smush’s free plan is enough. Weekly photo publishers get the best value from ShortPixel’s one-time packs or Imagify’s Growth plan, while Optimole is the simplest all-in-one choice if you want to optimize WordPress images and deliver them through a CDN in a single service. Check the official plugin pages on wordpress.org for ratings and compatibility, and Google’s image guidance at web.dev for the technical background.
How to Optimize WordPress Images Without a Plugin
If you prefer to keep your plugin count low, you can optimize WordPress images entirely by hand. The workflow is simple, it just takes more time per image.
Resize each photo to its display width, compress it in Squoosh — which lets you compare original and compressed versions side by side — then export as WebP and upload it, since WordPress accepts WebP natively.
The manual route gives you full control over quality, but it does not scale: fine for three images in a post, not for a 500-image gallery. Most owners end up with a hybrid — a plugin for bulk work, manual care for hero images. For a brand-new site, set the habit from day one — our tutorial on how to start a WordPress website covers the media settings to configure early.
How to Measure the Results
Do not guess — measure before and after. Run key pages through PageSpeed Insights first, note the score, LCP time, and page weight, then optimize and test again.
Expect visible results: page weight down 50–70%, LCP under 2.5 seconds on a decent host, and a PageSpeed score up 10–30 points. After you optimize WordPress images, PageSpeed Insights flags specific image issues, while GTmetrix shows a waterfall of each image’s download time. Test on a real phone connection too — mobile networks punish heavy images far more harshly than broadband.
Common Mistakes to Avoid
Even site owners who know they should optimize WordPress images trip over the same mistakes. Uploading full-resolution phone photos is the number one mistake — resize before upload, every time. Using PNG for photographs: a photographic PNG can be five times heavier than the same JPEG.
Forgetting the hero image: optimize it first, exclude it from lazy loading, and consider preloading it. Over-compressing is the opposite error: quality 40 might halve your file size again, but visitors will notice the artifacts, so stay in the 80–85 range for photos. Finally, ignoring the rest: slow hosting and too many plugins can keep a site slow even with perfect images.
Frequently Asked Questions
How do I optimize WordPress images for free?
The free way to optimize WordPress images starts with EWWW’s free plan for unlimited local compression, or Smush’s free plan for basic compression and lazy loading. Before uploading, resize images to their display width and compress them with Squoosh. WordPress also adds native lazy loading automatically, so the core workflow costs nothing.
What is the best image size for WordPress?
Full-width hero images should be 1,920 pixels wide at most. Standard in-content images work well at 1,200 pixels, and thumbnails at 300–600 pixels. Never upload images wider than 2,000 pixels unless you need a printable file.
Should I use WebP or AVIF in WordPress?
Use WebP as your default in 2026 — 25–35% smaller than JPEG and supported by all modern browsers. AVIF compresses even better, but support is not yet universal, so serve it alongside WebP rather than as your only format. Most plugins serve both automatically with a JPEG fallback.
Does lazy loading hurt SEO?
No — Google recommends it and WordPress builds it in. It improves loading speed, which helps rankings. The only risk is lazy-loading the hero image, which hurts Largest Contentful Paint, so exclude above-the-fold images.
How much can image optimization improve page speed?
On image-heavy pages, a proper workflow typically cuts total page weight by 50–70% and improves Largest Contentful Paint by one second or more. Many sites gain 10–30 PageSpeed points after they optimize WordPress images, resize oversized uploads, and convert to WebP.
The Verdict
If you want to optimize WordPress images for real speed gains in 2026, follow this order: resize before upload, convert to WebP, compress at quality 80–85, enable lazy loading, and serve through a CDN. A plugin such as ShortPixel or EWWW automates the repetitive work, but habits matter more than the tool — a resized, compressed WebP beats an unoptimized original. Start with your hero images and most visited pages, and make optimization part of every upload.
Prices checked: 20 November 2026. Prices change frequently — check each plugin’s official pricing page before you buy. Sources: wordpress.org plugin pages and Google’s image guidance at web.dev.