Start with plugins: deactivate and delete the ones you don't need. Then optimise your images, consider WebP because it's smaller, minify your CSS and JavaScript, and install a caching plugin. If you only have time for one fix, the official documentation points to caching as the biggest benefit for the smallest hassle.
The limit to know first: your theme and dynamic pages
Before you spend an afternoon on settings, look at what your site is built on. WordPress's own optimisation guide says a heavy, graphic-laden theme performs much worse than a fast, lightweight one.
The second limit is caching itself. It's the quickest win on this page, but it gets more complex when your pages carry a lot of dynamic content, the kind that changes for each visitor. If that describes your site, expect to spend more time on caching settings.
The speed fixes, in the order to try them
- Deactivate and delete any plugins you don't need.
- Disable the remaining plugins selectively to see which one affects server performance.
- Optimise every image, choosing the right format (JPG, PNG or GIF) and compression for each one.
- Consider a modern format such as WebP, which is smaller in size.
- Minify your CSS and JavaScript files.
- Install a caching plugin.
- Set the correct file headers on static files so browsers cache images, CSS and JavaScript.
- Run the latest versions of the operating system, web server, database and PHP.
- Add a CDN to mirror static files such as images across geographic regions.
Plugins come first because they're the first and easiest place to look. Every WordPress plugin you remove is one less thing to rule out, and the selective-disable test in step two turns a vague feeling of slowness into a named suspect.
Images come next. The documentation asks you to pick the right format and compression for each one, and our round-up of image optimisation plugins shows the tools that automate it.
Caching is where the quick fix lives. A caching plugin stores your posts and pages as static files, so the server does less work for each visitor. If you're choosing one, start with our guide to the best cache plugin for most sites.
Browser caching is a separate layer. By setting the right headers on files that don't change, you let each visitor's browser keep a copy of your images, CSS and JavaScript instead of fetching them again on every page.
The last two steps sit with your server. Keeping the operating system, web server, database and PHP up to date may sit with your host, so ask them. A CDN helps most when your visitors are spread across different regions, because it serves static files from closer to where they are.
Change one thing, then measure
It's tempting to work through the whole list in one sitting. Resist it. Make one change, load a few of your key pages, and note how they feel before moving on. If something breaks, you'll know which change did it, and if nothing improves, you've learned that step wasn't your bottleneck.
Still slow? Match the symptom to the fix
Every page is slow, even simple ones
Plugins are the first suspect: work back through step two.
Pages with lots of photos crawl
Check each image's format and compression. Switching to WebP, which is smaller in size, is worth trying for photo-heavy pages.
Your stylesheets and scripts are bulky
Minify the CSS and JavaScript files so there's less for each visitor's browser to download.
The site is quick for you but slow for visitors abroad
That's the job a CDN does: it mirrors static files such as images across geographic regions so they load from closer to the visitor.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
Repeat visits are as slow as the first one
Browsers may be fetching unchanged files fresh every time. Go back to step seven.
Caching is on but some pages still lag
Dynamic pages make caching more complex; review those pages separately.
The server lags even after a plugin clear-out
Ask your host whether the server software underneath your site is on its newest releases, and have them bring anything older up to date.
Nothing you change makes much difference
Then suspect the theme and test a lighter one.
If the problem goes beyond one setting, our broader walkthrough on making your whole website faster picks up from here.
As of Nov 2026, WordPress publishes its own optimization documentation, and it's the reference behind the steps here.
Frequently asked questions
What's the single quickest fix?
Caching. If you can only do one thing, install a caching plugin: the official guide rates it the best return for the least effort.
Can my theme slow WordPress down?
It can. If the plugin, image and caching fixes haven't moved the needle, test a lighter theme and compare how your key pages load.
Do I need a CDN?
Not for every site. It earns its place when your audience is international, since copies of your images and other unchanging files are kept in several parts of the world.
What's the difference between a caching plugin and browser caching?
One works on your server, the other in the visitor's browser. The plugin saves ready-made versions of posts and pages; browser caching lets repeat visitors reuse files that don't change.
Which image formats should I use?
Choose JPG, PNG or GIF to suit each image, and consider WebP as a smaller modern option.
