Why Is My WordPress Site Slow? 9 Real Causes
Your WordPress site used to load fine. Now the dashboard takes an age to open, pages crawl into view a few seconds late, and a plugin update from a few weeks back may or may not be the reason. Something changed, but working out exactly what is usually the hard part.
Speed problems rarely have a single cause. They stack up: a bloated theme, plugins doing overlapping jobs, a database never cleaned out, and a hosting plan that was fine at launch but now carries more than it was sized for. This walks through the nine causes that show up most often, and what a genuine fix looks like versus a band-aid, alongside the rest of GoodHost’s WordPress hosting knowledge centre.
Short answer: A slow WordPress site is usually a combination of oversized images, too many active plugins, an uncleaned database, no caching, and a hosting plan running short on CPU, memory or entry processes. Test each cause on its own rather than guessing, and fix the biggest one first.
What actually makes a WordPress site feel slow?
Speed is really two different things: how fast the server generates the page, known as time to first byte, and how fast the browser then loads everything else, images, fonts, scripts and stylesheets. A site can fail at either stage, and the right fix depends on which one is actually the problem.
If the page starts appearing quickly but images pop in late, that points to the browser side. If nothing happens for a second or two before anything renders, that usually points back to the server, your hosting, your database or a plugin doing heavy work on every load. Free browser tools that report both numbers separately will tell you which category applies before you start changing anything.
What are the most common causes of a slow WordPress site?
Nine causes account for most WordPress speed complaints: oversized images, too many plugins, a bloated theme, no caching, a cluttered database, an under-resourced hosting plan, render-blocking scripts, an overloaded homepage, and third-party embeds such as fonts, chat widgets or trackers loading from slow external servers.
- Oversized images. A phone photo can be 4 to 8 MB. Displayed at 800 pixels wide, it should be a fraction of that.
- Plugin overload. Every active plugin adds database queries or scripts, whether or not it does anything on the current page.
- A heavy theme. Page builder themes with dozens of “features” often load CSS and JavaScript for options you never use.
- No caching. Without a caching layer, WordPress rebuilds the page from the database on every single visit.
- Database bloat. Years of post revisions, spam comments and orphaned transient data slow every query the site runs.
- Under-resourced hosting. If your plan’s CPU, memory or entry-process limit is too low, pages queue up and slow down for everyone.
- Render-blocking scripts. Scripts loaded in the page head force the browser to stop and wait before it can display anything.
- An overloaded homepage. Sliders, embedded videos and a dozen widgets on one page multiply every other problem here.
- Slow third-party embeds. Fonts, chat widgets and trackers pull from someone else’s server, and you have no control over how fast it responds.
Is your hosting plan itself the bottleneck?
Sometimes yes, and it is worth ruling out early, since no amount of plugin tidying fixes a plan genuinely out of resources. Most hosts sell plans by “visits per month”, a rough proxy for expected traffic, not a guarantee of what your site can do. GoodHost’s WordPress plans publish the actual container limits instead.
| Plan | Price/month + GST | vCPU | RAM | Entry processes | IO | IOPS |
|---|---|---|---|---|---|---|
| WP 10 | $45 | 400% | 4 GB | 40 | 8 MB/s | 4,000 |
| WP 20 | $79 | 600% | 6 GB | 60 | 12 MB/s | 6,000 |
| WP 50 | $169 | 800% | 8 GB | 100 | 16 MB/s | 8,000 |
If you are on a shared cPanel plan rather than a WordPress-specific one, the comparison changes again: shared hosting uses CloudLinux to isolate accounts on a shared server, a different resourcing model to a dedicated WordPress container. Our guide on WordPress hosting versus general web hosting covers that distinction.
How do you actually diagnose which cause applies to your site?
Work through it in order: run a free speed test tool first, deactivate every non-essential plugin and switch to a default theme to see if the numbers improve, check image sizes, then look at your hosting resource usage. Skipping straight to a guess wastes time.
- Run a browser-based speed test on your homepage and your slowest inner page, not just the homepage alone.
- Deactivate plugins one at a time and re-test until the slowdown reappears, to isolate the culprit.
- Check your hosting control panel for any resource usage warnings or throttling notices.
- Test with caching switched off, then on, to see how much difference it actually makes.
If your site runs WooCommerce, the diagnosis looks different again, since a store adds database load a brochure site never sees. Our piece on what a WooCommerce store actually needs from its hosting is worth reading if that is your situation.
What is a quick fix versus a real fix?
A quick fix buys you headroom without addressing the underlying cause: clearing the cache, deleting a few unused plugins, compressing a batch of images. A real fix changes the structural problem, usually the hosting resources or the theme, so the slowdown does not creep back in six months.
If you have already cleaned the database, compressed images and cut plugins down to what you actually use, and the site is still sluggish, that is a fair sign the hosting plan itself is the limiting factor. Our comparison of what actually makes WordPress hosting fast in Australia goes through the hosting side of that.
Frequently asked questions
Why is my WordPress dashboard slow even though the public site loads fine?
The dashboard runs far more database queries per page than a typical front-end page, so plugin bloat and database clutter often show up there first. If wp-admin is sluggish but the site itself is fine, look at your plugin count and database size before assuming a hosting issue.
Can too many revisions in WordPress slow a site down?
Yes. WordPress saves a new revision every time you update a post or page, and by default keeps them all indefinitely. On a site with years of edits, that can mean thousands of extra rows the database has to work through on ordinary queries.
Does switching themes actually improve WordPress speed?
Sometimes significantly, especially if you are moving away from a heavy page builder theme toward a lighter one. Test it on a staging copy first, since a theme change also affects layout and any custom styling you have added over time, not just loading speed.
Will a CDN fix a slow WordPress site on its own?
A content delivery network helps with static files like images and scripts loading faster for visitors far from your server, but it does not fix a slow database query or an under-resourced hosting plan. It is one piece of a fix, not the whole thing.
How often should I clean up my WordPress database?
There is no fixed rule, but checking in every few months and removing spam comments, old post revisions and unused transient data is reasonable for an active site. A site that publishes frequently or runs WooCommerce will accumulate clutter faster than a static brochure site.
If you have gone through the list above and your hosting resources are the piece still holding you back, it may be worth comparing your current plan against GoodHost’s performance hosting specs before deciding what to change next.