“WordPress is slow” is the most repeated diagnosis on the internet, and it is almost never the right one. WordPress runs some of the fastest sites you visit every day. When a WordPress site is slow, something specific is slowing it down, and that something can be found. Here is where to look, in the order that actually pays off.
First, measure before you touch anything
Most speed projects fail because they start with fixes instead of measurements. Run your site through PageSpeed Insights or WebPageTest and look at two numbers: how long the server takes to answer (time to first byte), and how long the page takes to become usable. The first points at your hosting and backend. The second points at what the page is loading. Those are different problems with different fixes, and knowing which one you have saves you from paying to solve the wrong one.
Every “slow WordPress site” is slow for a specific, findable reason. Optimization plugins hide the symptom. Finding the reason removes it.
The four usual suspects
After years of these investigations, nearly every slow site I’ve opened up came down to one of the same four causes.
- Cheap hosting. Shared servers with hundreds of tenants answer in seconds, not milliseconds. If your time to first byte is over half a second on a simple page, no plugin will save you. Better hosting is often the cheapest fix per unit of speed.
- Plugin weight. Not the number of plugins, but what each one does on every page load. One badly written plugin that runs a slow database query everywhere outweighs twenty tidy ones. Deactivate suspects one at a time on a staging copy and re-measure.
- Unoptimized images. A single 4 MB hero photo undoes every other optimization on the page. Images should be resized to the size they display at, compressed, and served in a modern format. This is the most common problem and the easiest to fix.
- The theme itself. Page-builder themes load their entire toolbox on every page — sliders, icon packs, three copies of jQuery — whether the page uses them or not. If the theme is the problem, no amount of caching fully hides it.
What about caching plugins?
Caching helps, and you should have it. But caching is a multiplier, not a cure. It makes a fast site faster and makes a slow site’s homepage look acceptable while every uncached page — search, checkout, logged-in views — stays slow. If you install a caching plugin and your problem disappears, the problem is still there. It’s just wearing makeup.
The order to fix things in
Measure first. Fix hosting if the server is slow. Then images, because it’s an afternoon of work with a big payoff. Then audit plugins on a staging site. Replace the theme last — it’s the most expensive move, so make it only when the measurements point there.
If you’d rather have someone find the actual cause and hand you a prioritized fix-it plan in plain language, that is exactly the kind of technical review I do.