Making WordPress fast: caching, images and plugins
The changes that actually move the needle on WordPress speed, in priority order.
Most "slow WordPress" problems come from four things. Fix them in this order and you will usually beat a much bigger competitor's site.
1. Page caching (biggest win)
A page cache stores the finished HTML for logged-out visitors so WordPress does not rebuild the page on every request. It is the difference between a site that survives a traffic spike and one that falls over.
Good options: WP Super Cache, W3 Total Cache, or a host-level page cache. Avoid stacking two page caches — they fight each other.
2. Object caching (busiest sites)
WordPress makes the same database queries over and over. A persistent object cache keeps those results in memory. With Redis (or its BSD-licensed fork Valkey) plus the Redis Object Cache plugin, database load drops dramatically.
3. Images
Images are usually the largest thing on a page.
Resize before upload. A 4000px photo shown at 800px wastes bandwidth and hurts Core Web Vitals.
Compress. Lossy compression at sensible quality is invisible and saves 50–80%.
Modern formats. WebP or AVIF in place of JPEG/PNG.
Lazy-load below the fold — but never lazy-load the hero image, or you hurt Largest Contentful Paint.
4. Plugins and theme
Audit ruthlessly. Each active plugin adds PHP work and queries. Deactivate and delete what you do not use.
Choose a lightweight theme. A bloated multipurpose theme with a page builder can add more weight than everything else combined.
Avoid plugin overlap. Two SEO plugins, two caching plugins, two form plugins: pick one of each.
The infrastructure layer
If the site is on a VPS, the stack matters too:
PHP 8.x is meaningfully faster than 7.x — upgrade if you are behind.
OPcache should be on, with a sensible memory allocation.
HTTP/2 or HTTP/3 for parallel asset loading.
Enough RAM. If PHP-FPM workers are being killed, no amount of plugins will save you — see Sizing your server.
Measure before and after
Never optimise blind. Measure with a real tool (Lighthouse in your browser's devtools, or an external page-speed service) before and after each change, so you know what actually helped. Chasing a number without measuring is how sites end up with six half-configured caching plugins.
Related reading