A WordPress site that loads slowly is usually slow for two or three reasons stacked together, and the most common one sits underneath WordPress: the hosting. The quickest route is to measure the server response time first, then work up through caching, PHP, the database, images and plugins, changing one thing at a time. If the server itself is slow, no plugin will fix it, and the answer is a plan that suits your site. Our WordPress hosting comparison is built for that decision.
TL;DR
- WordPress is not slow by nature. Sites slow down as hosting, plugins, themes, images and scripts pile up, according to the WordPress.org developer documentation.
- Measure before you change anything. Test several pages, on mobile and desktop, and record the results.
- Check server response time (TTFB) first. If it is high on every page, the cause is the server or the hosting plan, not your theme.
- Then fix in order: caching, PHP version, database, images, plugins and external scripts.
- Make each change on a staging copy or after a backup, and retest the same page afterwards.
Table of Contents
- Why slow sites are usually a stack of problems
- Step 1: Measure before you touch anything
- Step 2: Check server response time (TTFB)
- Step 3: Decide whether your hosting plan is the bottleneck
- Step 4: Switch on caching and check it works
- Step 5: Update PHP and tidy the database
- Step 6: Fix images first on the front end
- Step 7: Audit plugins, theme and external scripts
- Step 8: Rule out abusive traffic
- What a typical fix looks like
- Our view: start with the server
- Choosing a faster home for your site
- FAQ
- Sources
Why slow sites are usually a stack of problems
The official WordPress guidance lists the usual suspects: the hosting environment, how WordPress is configured, software versions, theme and plugin weight, and the number and size of images. It also warns that without a caching solution, page requests stack up and can overwhelm the web or database server (WordPress.org, Optimization).
That matters because most people fix the wrong thing first. They install a speed plugin, delete a few other plugins, and see little change, because the real delay is the time the server takes to build the page. A sensible order of work saves you hours:
- Server and hosting
- Caching
- PHP and database
- Images and front-end code
- Plugins, theme and third-party scripts
The rest of this guide follows that order.
Step 1: Measure before you touch anything
Changing settings at random wastes time and can make things worse. Take a baseline first.
- Pick three or four representative pages: the homepage, a blog post, a product or service page, and, if relevant, the checkout.
- Run each through Google PageSpeed Insights, which the WordPress.org learning resources recommend for specific feedback. WebPageTest and the speed tools built into Chrome and Firefox also work.
- Test on mobile and desktop, and repeat each test a couple of times. One run can be a fluke.
- Write down three numbers per page: Time to First Byte (TTFB), Largest Contentful Paint (LCP, how long the main content takes to appear) and Total Blocking Time (how long scripts freeze the page).
If every score looks fine but the site still feels slow to you, the problem may be your own device, browser or connection rather than the site.
Step 2: Check server response time (TTFB)
TTFB is the time between a browser asking for a page and receiving the first byte back. PageSpeed Insights labels it “Server response time”. It is the clearest signal of whether the problem is the server or something you built on top of it. Our plain-English explainer on what TTFB means covers the basics.
Two tests narrow it down:
- Test several pages. If only some pages have a high TTFB, the cause is likely something those pages share, such as a particular plugin or query. If all pages are slow, look at the server or site-wide configuration.
- Test a static file. Upload a plain HTML file to your hosting and time it. If TTFB is high even for that, the server is the problem. If it is low, the delay is in how WordPress builds pages, meaning PHP, the database or plugins. This method comes from WP Engine’s TTFB troubleshooting guide.
You can also run a quick check with our TTFB speed checker and see how UK hosts compare on the UK hosting speed map.
Other things push TTFB up: server distance from your visitors, a saturated server on a busy shared plan, slow DNS and heavy database work. The WordPress learning pages note that distance between visitor and data centre adds latency, which is why a UK business with mostly UK customers should look at UK-based servers (WordPress.org, Improving Site Performance).
Step 3: Decide whether your hosting plan is the bottleneck
Hosting type is one of the biggest factors in WordPress speed. The official overview points out that shared, VPS, dedicated, managed and cloud hosting behave differently, and that on shared hosting performance can drop when other sites on the server get busy (WordPress.org).
Signs your plan is the limit:
- TTFB is high on every page, including a static file.
- Speed varies a lot by time of day, with the slowest periods matching peak traffic.
- The slowdown appeared when traffic grew, or after you added a shop, a membership area or a page builder.
- Your hosting dashboard shows CPU or RAM regularly hitting the plan’s limit. A sudden jump in CPU can mean more PHP work, a plugin process, more uncached requests or higher traffic. A jump in RAM can mean heavier plugin activity or dynamic pages that bypass the cache.
- The wp-admin area is also slow, not just the public pages.
If several of these fit, move to a plan with more headroom rather than trimming a site that is already lean. Which type suits you depends on the site:
| Your situation | Plan type to look at |
|---|---|
| Small brochure site or blog, modest traffic | Shared hosting or WordPress hosting |
| Business site that needs updates, backups and speed handled for you | Managed WordPress hosting |
| Online shop with a busy checkout | WooCommerce hosting |
| Developer wanting control over the server | VPS hosting |
| High traffic, large or demanding sites | Dedicated servers or enterprise WordPress hosting |
When you compare, look at where the data centre is, the storage type (SSD or NVMe), whether server-level caching is included, and what the renewal price is after the introductory term. Our reliability score checker helps with the uptime side of that decision.
Step 4: Switch on caching and check it works
Without caching, WordPress rebuilds every page from PHP and database queries for every visitor. Full-page caching stores the finished HTML and serves it instead, which is why it is often the single biggest improvement for public pages.
How to do it:
- Use the caching built into your hosting plan if it has one, or a single reputable caching plugin. Never run two page-caching plugins together.
- Clear the cache after major changes. Most caching plugins add a purge button to the admin bar at the top of the dashboard.
- Check it is working: open the page in a private window, view the page source and look for the HTML comment that caching plugins typically add (example from a plugin’s documentation). The result is also visible in your TTFB, which should drop sharply on the second request.
Logged-in users, carts and checkout pages are normally excluded from page caching, so test as a logged-out visitor. For a shop, your hosting matters even more, because those pages cannot be fully cached.
Step 5: Update PHP and tidy the database
PHP is the language WordPress runs on, and the server runs a particular version of it. Running an old version is a known cause of slow page generation. Your hosting control panel normally lets you pick the PHP version. Test the upgrade on a staging copy first, because an old plugin or theme can break on a newer version.
The database matters because WordPress queries it for almost every page. The official guidance notes that a bloated database slows dynamic pages because more and slower queries are needed (WordPress.org). Common sources of bloat are:
- thousands of old post revisions
- expired temporary data (transients) and spam comments
- leftover tables from plugins you deleted
- too much “autoloaded” data, which WordPress loads on every single request. WP Engine suggests keeping it below roughly 0.8 MB (WP Engine).
Take a full backup before any database cleanup. If you are not comfortable working in the database, a managed WordPress plan that handles routine maintenance is the safer route.
Step 6: Fix images first on the front end
If TTFB is fine but the page still takes a long time to show its main content, look at what the browser has to download. Images are the usual culprit: a photo straight from a phone or camera can be several megabytes and thousands of pixels wide.
- Resize images before uploading. A full-width image rarely needs to be wider than about 2,000 pixels.
- Use modern formats such as WebP or AVIF, which are often much smaller than a JPEG at similar quality.
- Keep lazy loading on for images below the fold, so they only load as the visitor scrolls. Do not lazy-load the main image at the top of the page, as that delays LCP.
- Check your largest pages in PageSpeed Insights for the images it flags as oversized.
Bulk-compression plugins can process your existing media library, but take a backup first.
Step 7: Audit plugins, theme and external scripts
The number of plugins matters less than what each one does. One badly written plugin can slow every page, while twenty light ones may do no harm. The WordPress guidance specifically names resource-heavy themes and large numbers of plugins as causes of a heavy load (WordPress.org).
A safe way to audit:
- On a staging copy, deactivate plugins one at a time and retest the same page after each.
- Use a profiling plugin such as Query Monitor to see which plugins run the slowest database queries.
- Delete plugins you do not use, rather than just deactivating them.
- Review external scripts: chat widgets, tracking pixels, ad code, social feeds and web fonts each add requests to other servers. Keep only those that earn their place.
- If you use a heavy multipurpose theme or page builder, check whether a lighter theme would deliver the same design.
When you delay or defer scripts, test forms, menus, sliders and checkout afterwards, because this is where sites most often break.
Step 8: Rule out abusive traffic
Sometimes the load is not your visitors. The WordPress documentation lists abusive traffic as a cause of slowdowns, including repeated login attempts, image hotlinking and denial-of-service attacks (WordPress.org). If your hosting statistics show sudden spikes in requests to the login page or to a single file, block the source or limit login attempts, and ask your host what protection the plan includes.
What a typical fix looks like
Here is an illustrative example, not a client case. A small UK business site has a TTFB of over a second on every page, including a static test file. The images are fine and the plugins are modest. The pattern points to the server, so changing the theme would achieve little. Moving to a plan with server-level caching and a UK data centre addresses the cause. A second site has a low static-file TTFB but a high TTFB on its shop pages. That points to dynamic content, so the fix is a PHP update, database cleanup and a plan sized for WooCommerce.
The diagnosis decides the remedy. That is why measuring first matters.
Our view: start with the server
Most guides to slow WordPress sites begin with plugins and images. We think that is the wrong order. If the server answers slowly, every other fix is working against a handicap, and site owners can spend weeks tuning a site that needs a different plan.
We compare UK hosting on price, renewal cost, performance and support, and we publish the tools so you can see the numbers yourself: a TTFB checker, a speed map by location and a reliability score. Our aim is to help you choose hosting that suits your site, and to avoid the surprise of a renewal price that jumps once the introductory term ends.
For most small business owners, the practical path is simple. Measure TTFB, fix caching and images, and if the server is still the bottleneck, choose a plan built for WordPress. Developers get the same logic with more control: a VPS or dedicated server where you set the stack yourself.
Dylan
Choosing a faster home for your site
If your tests point to the server, our hosting comparison pages set out UK plans for WordPress, managed WordPress, WooCommerce, VPS and dedicated servers side by side, with renewal costs shown so you know the long-term price. Choose the type that matches your traffic and technical comfort, then check your site’s speed again after the move.
If you are also comparing domain names for a new site, our domain price comparison shows registration and renewal costs across common extensions.
Affiliate disclosure: we earn a commission if you buy a hosting plan or domain through links on this site.
FAQ
Why is my WordPress site loading so slowly?
Usually it is several causes together: an underpowered or overcrowded hosting plan, no caching, a heavy theme, large images and too many or poorly written plugins. Measure TTFB and test several pages to see whether the server or the site itself is at fault.
Is WordPress itself slow?
No. WordPress performance depends on hosting, configuration, software versions, themes, plugins and images, according to the official developer documentation. Sites tend to slow down as these pile up over time, and a well-maintained site on suitable hosting can be fast.
How do I clear the cache in WordPress?
Most caching plugins add a purge or clear cache button to the admin bar at the top of the dashboard. Hosting-level caches usually have a purge option in the hosting control panel. Clear the cache after changing themes, plugins or settings, then check the page in a private window.
Which hosting is fastest for WordPress?
It depends on your traffic, location and budget, but look for a UK data centre if your visitors are in the UK, SSD or NVMe storage and server-level caching. Our WordPress hosting comparison ranks UK options, and the speed map shows TTFB by location.
Sources
- WordPress.org developer documentation: Optimization
- WordPress.org Learn: Improving Site Performance, an overview
- WP Engine support: Troubleshoot High Time to First Byte (TTFB)
- WordPress.org plugin directory: AJO One-Click Cache Cleaner
