How to Speed Up WordPress: A Step-by-Step Guide

A slow WordPress site costs you visitors, conversions, and search rankings. This guide walks you through seven practical steps — from measuring your current performance to fine-tuning your cache — so you can shave seconds off your load time without touching a line of server config.

Measure your current performance
Before you change anything, take a baseline. Open PageSpeed Insights, GTmetrix, or WebPageTest and run a test on your homepage, a blog post, and a product page. Write down your scores and the three biggest bottlenecks the tools flag. You will re-test after every step so you know exactly what moved the needle.
Install a caching plugin
Caching is the single highest-impact change you can make for typical shared and VPS hosting. A good caching plugin generates static HTML copies of your pages and serves them instead of hitting PHP and the database on every request. Install the plugin, enable page caching, and re-run your performance test — you should see a measurable improvement immediately.
Optimise your images
Images often account for 50–70% of page weight. Run every image on your site through a compression tool — lossy compression at 80–85% quality is visually imperceptible and can cut file sizes by half. Convert JPEGs and PNGs to WebP format for an additional 25–35% saving. If you have hundreds of images, use a bulk-optimisation plugin instead of doing it manually.
Minify and combine CSS and JavaScript
Most caching plugins include a minify/combine option under their advanced settings. Enable CSS minification first and re-test — modern themes rarely break on CSS minification alone. Then enable JS minification. Be cautious with "combine JS": page-builder-heavy sites (Elementor, Divi) can break unpredictably. If something looks wrong after combining, disable that one option and re-test.
Clean up your database
Over time your database fills with post revisions, spam comments, transients, and orphaned metadata. A database cleanup plugin will sweep these out and optimise your tables. Run a cleanup every 3–6 months. Most tools have a dry-run mode so you can preview what will be deleted before committing.
Set up a CDN
A Content Delivery Network serves your static assets — images, CSS, JS, fonts — from edge servers close to your visitors. If your hosting does not include a CDN, Cloudflare has a free tier that takes five minutes to set up. Enable "Auto Minify" and "Brotli compression" in the Cloudflare dashboard for additional free gains.
Re-test and monitor ongoing performance
Run the same three tests you did in step 1 and compare the numbers. Your mobile PageSpeed score should be at least 20 points higher. Set up automated monitoring — GTmetrix and PageSpeed Insights both offer scheduled tests — so you are alerted the moment performance regresses rather than finding out from a customer.

The problem
[fill with real experience — do not fabricate]
Most WordPress performance guides recommend installing three caching plugins, a CDN, and hoping for the best. Site owners end up with conflicting configurations and no way to measure whether any of it worked. [fill with real experience — do not fabricate: describe a concrete before/after scenario, e.g. "a client came to us with a 12-second LCP on mobile after activating every optimisation checkbox in their theme."]
How we approached it
[fill with real experience — do not fabricate]
[fill with real experience — do not fabricate: describe the methodology. Which test stack did you use? Which hosting environment? How many page types were tested? What was the benchmark tool sequence? E.g. "We tested on a Cloudways 2 GB VPS with Astra + WooCommerce demo content. Each plugin was measured cold (no cache) and warm (cached), three runs each, discarding the first run."]
What we found
[fill with real experience — do not fabricate]
[fill with real experience — do not fabricate: concrete observations from real testing. E.g. "WP Rocket shaved 2.3s off LCP out of the box. W3 Total Cache needed 45 minutes of configuration to match that result. The single biggest lever across all plugins was image optimisation — more than caching itself."]
Who this helps
This guide is written for site owners and freelancers on shared or mid-tier VPS hosting who want measurable speed improvements without hiring a DevOps engineer. If you are on fully managed hosting (Kinsta, WP Engine), most of the caching steps are handled at the server level — skip to image optimisation and monitoring.

[Author name][Role, e.g. Senior WordPress Developer]