WordPress powers a very large share of the web, including plenty of genuinely fast sites. So when yours is slow, that is something that was done to it rather than something it is. Six causes account for nearly all of it, and you can work out which one is yours in about twenty minutes.
1. The images
This is the first thing to check and usually the biggest single win. A photograph straight off a phone is often three to six megabytes and four thousand pixels wide, sitting in a slot that displays it at eight hundred. The browser downloads all of it.
Fixing it means resizing to the size actually displayed, converting to WebP, and compressing. An image plugin will do all three across the whole library in one pass. On a photo-heavy site this alone often halves the page weight.
2. Too many plugins, or the wrong ones
The count matters less than what they do. Twenty lightweight plugins can be fine; three heavy page builders and a slider plugin will not be. The ones that reliably cost the most are page builders, sliders, anything adding its own stylesheet and script to every page, and plugins that run database queries on every load.
Deactivate anything you are not using and then delete it. Deactivated plugins still sit on the server and are still a security liability — see website security basics.
3. Cheap shared hosting
On shared hosting your site sits on a machine with hundreds of others, and when one of them has a busy day everybody slows down. The symptom is distinctive: the page is slow to start rather than slow to finish. If the first byte takes two seconds and the rest loads quickly, the server is the problem and no amount of image optimisation will fix it.
That is a hosting decision rather than a WordPress one — see domain and hosting in Bangladesh.
4. No caching
Without caching, WordPress rebuilds every page from the database on every single visit. A caching plugin saves the finished page and serves that instead, which is often the difference between three seconds and under one.
This is the cheapest improvement available: one plugin, default settings, done in ten minutes. If your site has no caching plugin at all, do this before anything else.
5. A theme doing far more than you need
Multipurpose themes sold with "50+ demos" carry the code for all fifty, and much of it loads whether you use it or not. The same is true of a page builder laying out pages with deeply nested markup.
This is the hardest one to fix, because changing theme means rebuilding the pages. It is worth knowing it is the cause before you spend money elsewhere, though — if the theme is the problem, nothing else will rescue it.
6. A database nobody has cleaned
After a few years a WordPress database carries thousands of post revisions, expired transients, spam comments and leftover tables from plugins deleted long ago. It rarely causes a dramatic slowdown on its own, but it makes everything else worse and backups larger.
Finding out which one it is, in twenty minutes
- Run PageSpeed Insights on your slowest page and read the field data, which is real visitors, not the lab score. The opportunities list usually names the culprit outright.
- Check time to first byte. Slow TTFB means hosting or no caching. Fast TTFB with a slow finish means images, scripts or the theme.
- Test on mobile data, not office wifi. Most of your visitors are on a mid-range Android on a mobile connection, and that is the experience that counts — see how fast does your website need to be.
The order worth doing them in
Caching, then images, then remove unused plugins. Those three are cheap, safe and reversible, and together they fix the majority of slow WordPress sites. Only if the site is still slow afterwards is it worth looking at the theme or moving host — those are projects, and it is a waste to start one before the easy wins are taken.
If you would rather have this diagnosed than guessed at, it is part of what our WordPress customization work covers. Send us the URL and we will tell you which of the six it is.