// WEB DESIGN
Why Is My WordPress Site Slow? 8 Causes and the Fixes
WordPress itself is rarely the problem. Here is how to measure a slow site, the eight causes we find most often, the order to fix them in, and when patching stops being worth it.

Only about four in ten WordPress sites pass Google's Core Web Vitals on mobile. The 2024 Web Almanac put WordPress at 40%, against 57% for Wix, 60% for Squarespace and 73% for Duda. So if you are asking "why is my WordPress site slow?", you are far from alone, and the cause is rarely WordPress itself.
WordPress is the base layer. What sits on top of it sets the speed: the hosting plan, the theme, the plugins, the images and how long it has been since anyone tidied up. Most slow sites we are asked to look at have three or four of these problems at once, which is why fixing only one of them tends to disappoint.
Below: how to measure the problem properly, the eight causes we find most often, the order to fix them in, and the point at which patching a WordPress site costs more than rebuilding it.
Is the site slow, or does it only feel slow?
Measure before you change anything. A site can feel slow on your office Wi-Fi and be fine for customers. More often it is the other way round: quick on your laptop, painful on a mid-range phone on mobile data, which is how most of your visitors see it.
Open PageSpeed Insights, paste in your address and look at the two parts of the report. The top part is real-user data from Chrome visitors over the last 28 days. The lower part is a one-off lab test on a simulated phone. Google ranks on the real data. The lab test is what helps you find the causes.
Google judges three numbers, the Core Web Vitals. According to web.dev, a page is in good shape when:
- Largest Contentful Paint (LCP), the time until the main content appears, is 2.5 seconds or less;
- Interaction to Next Paint (INP), how quickly the page responds to a tap or click, is 200 milliseconds or less;
- Cumulative Layout Shift (CLS), how much the layout jumps around while loading, is 0.1 or less.
These are measured at the 75th percentile, so three in four real visits have to hit the target, not just yours. Test more than the home page. Check a service page, a blog post and, if you sell online, a product page and the checkout. A slow home page with a fast blog points to a different cause than a site that is slow everywhere.
One more quick test: open the admin area. If the dashboard and the editor are slow too, the problem almost always sits on the server (hosting, PHP, database). If only the public pages drag, start with the theme, the images and the scripts.
Eight reasons your WordPress site is slow
These are the causes we run into most when a client asks us to look at a slow site, roughly from most to least common.
1. Cheap or overcrowded hosting
The cheapest shared plans put hundreds of sites on one server. When a neighbour gets a burst of traffic, your site waits its turn. The giveaway is a long time to first byte (TTFB): the browser sits idle before the server sends anything at all. No plugin can fix a server that answers slowly. We cover what to look for in how to choose a web hosting provider.
2. An outdated PHP version
WordPress runs on PHP, and newer PHP versions run the same code faster. WordPress.org recommends PHP 8.3 or newer and warns that older versions have reached end of life and may expose the site to security risks. We still regularly find sites on PHP 7.x, because nobody touched the setting after launch. Most hosting panels let you switch in a minute, but try it on a copy first: old plugins sometimes break on new PHP.
3. A heavy theme or page builder
Multipurpose themes promise every layout imaginable, and they load the code for all of it on every page: sliders, animations, icon sets, several font families. Page builders such as Elementor or Divi add their own layer of markup and scripts on top. It looks fine in the demo and weighs several megabytes on a real page. For reference, the Web Almanac puts the median WordPress page at 2,047 KB on mobile.
4. Too many plugins, or the wrong ones
What plugins do matters more than how many there are. One badly written plugin that runs heavy database queries on every page can do more harm than twenty small ones. Watch for plugins that load their scripts site-wide when you need them on one page (contact forms and sliders are frequent offenders), several plugins doing the same job, and plugins with no update in a year or more. The free Query Monitor plugin shows which plugins slow down each page.
5. Uncompressed images
A photo straight off a phone or a stock library can weigh several megabytes. Put ten of them in a gallery and the page turns into a download. Images should be resized to the size they are shown at, saved as WebP or AVIF, and loaded only when the visitor scrolls to them. WordPress has lazy-loaded images by default since version 5.5, but it can't shrink a file that was uploaded too big.
6. No page caching
Without caching, WordPress builds every page from scratch on every visit: it runs PHP, queries the database and assembles the HTML. A page cache keeps the finished page and serves it in milliseconds. Many hosts offer caching at server level; if yours doesn't, a caching plugin does the job. Pages for logged-in users, the basket and the checkout usually skip the cache, which is why a shop can feel slow even when its home page is quick.
7. A bloated database
After a few years the database collects thousands of post revisions, spam comments, expired temporary data and tables left behind by plugins you deleted long ago. On its own this rarely makes a site crawl, but on weak hosting it adds up, especially in the admin area. A clean-up and a cap on revisions belong in routine website maintenance.
8. Third-party scripts
Chat widgets, Facebook and TikTok pixels, embedded maps and YouTube videos, cookie banners, review badges. Each one loads code from someone else's server, and you have no say over how fast that server is. These scripts are a common reason for a poor INP score, because they keep the browser busy just as a visitor tries to tap something. Remove what nobody uses and load the rest only when it is needed.
Fix it in this order
The order matters, because the early steps make the later ones easier to judge. This is the sequence we follow:
- Measure and write the numbers down. Record LCP, INP and CLS for four or five key pages, so you can see what each change does.
- Take a backup and set up a staging copy. Never test speed fixes on the site your customers are using.
- Fix the server first. Move to better hosting if response times are poor, switch to a supported PHP version and turn on server caching.
- Compress and resize images. Convert the heaviest ones to WebP and replace oversized uploads.
- Cut plugins. Deactivate them one at a time on the staging copy, measure, and delete what you don't need.
- Deal with the theme. If the theme or page builder carries most of the weight, no setting will fix it. This is where you choose between a lighter theme and a rebuild.
- Trim third-party scripts. Keep the ones that bring in business and delay the rest.
- Measure again after four weeks. Real-user data in PageSpeed Insights and Google Search Console covers the last 28 days, so judge the result a month later, not the next morning.
Steps one to five are routine work. On a site that is a few years old but was built sensibly, they are often enough. If you have done all five and the site is still slow, the problem is in the foundation.
When to stop patching and rebuild
Every WordPress speed fix removes something that shouldn't be there. Sooner or later there is nothing left to remove without taking the site apart. These are the signs we look for:
- The theme is the bottleneck. The design depends on a heavy multipurpose theme or a page builder, and replacing it means rebuilding every page anyway.
- Speed keeps slipping back. You fix it, a plugin updates, and three months later the scores are red again.
- The site relies on plugins nobody maintains. Every PHP or WordPress update breaks something, so the updates stop happening.
- You pay for hosting you shouldn't need. The server keeps getting upgraded to hide problems in the code.
- A redesign is due anyway. If the site needs new content and a new look, speeding up the old one means paying twice.
If several of these apply, a rebuild usually costs less over two or three years than patching it again and again. That can mean a lean, carefully built WordPress site or a different stack. For marketing sites we build on Next.js: pages are generated in advance and served from a CDN, so no PHP runs and no database is queried when someone visits. We set out the trade-offs in Next.js vs WordPress for business websites.
Either way, decide on numbers. Add up what the current site costs you each year in hosting, maintenance and lost enquiries, and set that against a one-off build with lower running costs. Our marketing site service and pricing page give indicative figures.
The verdict
A slow WordPress site is almost never slow because of WordPress. It is slow because of cheap hosting, an old PHP version, a theme that loads everything, plugins nobody reviewed and images nobody compressed. Fix those in order and most sites become fast enough for Google and for customers. Start with the server and the images: they are cheap to fix and usually give the biggest gain.
Then be honest about the result. If you have done the routine work and the theme or page builder still carries most of the weight, more plugins and a bigger server won't change that. That is the moment to price a rebuild, not another round of optimisation.
Frequently asked questions
Why is my WordPress site suddenly slow?
A sudden slowdown usually follows a change: a plugin or theme update, a new plugin, a spike in traffic or a problem on your host's server. Check what changed in the last few days, look at your host's status page, and test with recently added plugins switched off on a staging copy.
Do too many plugins slow down WordPress?
They can, but quality matters more than quantity. One poorly coded plugin can slow every page, while a dozen small, well-built ones may have no visible effect. Remove the plugins you don't use and check which ones load code on every page.
Will a caching plugin fix a slow WordPress site?
It helps a lot with pages that look the same for every visitor. It won't fix a slow server, a heavy theme or oversized images, and pages such as the basket and the checkout usually aren't cached at all.
Is WordPress slower than other platforms?
A clean WordPress install is quick. In practice, WordPress sites pass Core Web Vitals less often than sites on some hosted builders, because they are more often built with heavy themes, lots of plugins and cheap hosting.
How fast should a website load?
Google's targets: the main content appears within 2.5 seconds, the page responds to a tap within 200 milliseconds, and the layout stays stable while it loads. They are measured across three in four real visits.
Should I fix my WordPress site or rebuild it?
Fix it if the slowdown comes from hosting, images, caching or a few bad plugins. Rebuild if the theme or page builder is the main problem, if speed keeps slipping back after fixes, or if a redesign is due anyway.
Is a slow site costing you enquiries?
Send us your address. We'll test your key pages, tell you what is slowing them down and whether a fix or a rebuild makes more sense, and send a written proposal with a fixed price.
Start the conversation →