WordPress image optimisation in 2026 is not just about compression. It is about format, sizing, delivery, and what happens after the file leaves the origin. This guide walks through the full pipeline so your images land smaller, arrive faster, and look identical.
Pick the right format first
AVIF is the smallest. WebP is the safest fallback. JPEG and PNG are the legacy formats you only fall back to when nothing else works. Most modern WordPress plugins generate AVIF and WebP automatically from a single source upload.
Browser support for AVIF crossed ninety five percent in 2024. There is no real reason not to use it for new content in 2026.
Generate the right sizes
WordPress generates several image sizes by default to power srcset. The trick is to make sure the largest size is no bigger than the largest place that image is ever displayed. If your widest column is 1200 pixels wide, you do not need a 2400 pixel original.
Resize uploads on upload, not on display. Display time resizing is what slow plugins do.
Deliver from the edge, not the origin
Once images are small and properly sized, the next step in wordpress image optimisation is delivery. Serving a perfectly optimised image from a server in Sydney to a visitor in Berlin is still slow. Defyn Media Offload pushes the file to S3 compatible storage and serves it through a CDN, so the visitor pulls bytes from a city near them.
This single step often cuts perceived load time more than every other optimisation combined.
Lazy load below the fold
Add loading=”lazy” to images below the fold. WordPress does this for you by default since version 5.5. The exception is your LCP image, which must load eagerly and should usually have fetchpriority=”high”.
Mixing eager and lazy correctly is what separates good optimisation from cargo culting.
Measure with PageSpeed and WebPageTest
PageSpeed Insights is fast. WebPageTest is honest. Run both. PageSpeed tells you what Google sees. WebPageTest shows you the waterfall a real user experiences.
If both agree your images are the bottleneck, fix the pipeline. If they disagree, trust WebPageTest.
Frequently asked questions
Is wordpress image optimisation worth it for a small blog?
Yes. The same Core Web Vitals signals that affect large sites affect small ones. Image optimisation moves the needle even at low traffic.
Does AVIF replace WebP?
In practice yes, but keep WebP as a fallback for older browsers. Most plugins generate both.
Do I need a separate image CDN?
Not usually. A standard CDN in front of your object storage handles images well enough for almost every site.
Will Smush or ShortPixel do this for me?
They handle compression. They do not move your files off the origin. You still need an offload plugin for that step.
Related reading
- WordPress LCP optimisation guide
- Core Web Vitals and media delivery
- Defyn Media Offload on WordPress.org – the plugin behind most of the techniques above.
