Fast WordPress hosting: what really makes a site quick

Why 'fastest' depends on your site, not just the host

Ask which is the fastest WordPress hosting and you will find many answers, usually based on someone else's test site. Your own site's speed depends on three things working together:

• Distance: how far requests travel between your visitors and the server or cache
• Work per request: whether a page comes from a cache or has to be built by PHP and the database each time
• What the page carries: the size of images, fonts and scripts, and how many plugins and third-party services run

A host controls the first two and gives you tools for the third. That is why a site can feel slow on well-specified hosting, and why moving a well-built site to a host with a nearby data centre and good caching can make a clear difference.

Speed claims on hosting websites are measured on the host's chosen sites, plans and test locations, so they do not tell you how your site will behave. We do not compare hosts' speed claims here. Instead, the sections below explain each part of the speed puzzle, what our picks say they provide, and how to run a fair test of your own.

Does server location affect speed for UK visitors?

Every uncached page request travels to the server and back, so distance adds delay. For a site whose visitors are mostly in the UK, hosting in the UK keeps that delay short.

All three of our picks list a UK location. Cloudways lists London on each of its five cloud providers, and Manchester on Vultr, and asks you to choose a location when you launch each server. WP Engine lists London among its European data centre regions. Krystal says its managed WordPress hosting runs on its own UK infrastructure, and its technology page names a data centre in East London.

Location matters most for pages that cannot be cached: a logged-in WordPress admin, a shopping basket, a checkout or an account page. For everything else, caching closer to the visitor does most of the work. Our UK-based WordPress hosting guide looks at location in more detail.

Page caching, edge caching and the CDN

Caching is the single biggest factor in WordPress speed. Without it, every visit runs PHP and a set of database queries to build the page. With it, most visitors get a ready-made copy. There are three main layers:

• Page caching stores whole pages on the server, so PHP and the database are skipped for most visitors
• Object caching (often Redis or Memcached) keeps database results in memory, which helps pages that cannot be fully cached, such as baskets and account areas
• A CDN and edge caching serve files, and sometimes whole pages, from locations close to each visitor

Pages that must stay personal need care. WP Engine's caching documentation, for example, says pages named cart, checkout or store, the WordPress admin and logged-in sessions are excluded from its cache by default, with extra exclusions added when it sees WooCommerce on a site. Krystal pairs LiteSpeed page caching with Redis object caching on its premium managed plans, which helps pages that cannot be fully cached. Our WooCommerce hosting guide covers shops in more depth.

Most managed hosts handle caching for you, and some restrict caching plugins that would clash with their own. WP Engine lists caching plugins that conflict with its platform among its disallowed plugins. Krystal says it does not recommend adding another caching plugin alongside its pre-configured LiteSpeed Cache. Cloudways pre-installs its own Breeze cache plugin. Check each host's rules before you move a site that relies on a caching plugin.

Caching and CDN at each host

Here is what each of our picks says about caching and content delivery, in its own terms:

Each host explains its options on its own site: Cloudways (opens in a new tab), Krystal (opens in a new tab) and WP Engine (opens in a new tab). Where a feature is an add-on, check the cost on the host's site before you plan around it.

Server stack: web server, PHP versions, HTTP/3 and compression

The software on the server decides how efficiently each request is handled. The details hosts publish vary, but these are the parts worth checking:

• Web server: Cloudways describes its Lightning Stack as NGINX with PHP-FPM; Krystal's managed platform is built around LiteSpeed caching
• Database: Cloudways lists MariaDB 10.11 or 11.4; whichever host you choose, check the database version suits your plugins
• PHP versions: Cloudways offers PHP 7.4 to 8.4; WP Engine lets you manage the PHP version from its dashboard
• Protocols and compression: ask whether the host or its CDN supports HTTP/3, TLS 1.3 and Brotli compression, which help pages reach browsers efficiently
• Storage: Cloudways and Krystal describe NVMe storage
• Isolation: Krystal gives each site dedicated resources; WP Engine's Business plan has isolated resources; Cloudways gives you your own cloud server

Isolation matters for speed as well as security: on a crowded shared server, a busy neighbour can slow your site down. Our guide to shared vs VPS WordPress hosting explains the trade-offs.

Finding slow plugins: host performance tools

When a page is slow even though the hosting is well set up, the cause is usually a plugin, a theme function, a heavy database query or a call to an outside service. Finding it by switching plugins off one by one is slow and risky on a live site. Several hosts give you tools for this:

• WP Engine has a Performance Insights page in its User Portal, and lists application performance monitoring as an add-on on its Business and Enterprise plans
• Cloudways lists server and application monitoring across its plans
• Krystal says its managed platform shows live information on requests, error logs and resource usage

Whichever host you use, a plugin such as Query Monitor can also show slow queries and hooks. Once you have found the culprit, test the fix on a staging copy before pushing it live.

Does hosting speed affect SEO?

Search engines use many signals to rank pages, and page experience is one factor among many. Content that answers the searcher's question, a sound site structure and links from other sites all matter too. Faster hosting will not move a page up the results on its own.

What speed does reliably is help the people who arrive. Pages that load quickly are easier to use, especially on mobile, and that helps with the things you care about: enquiries, sales and sign-ups. Google Search Console and PageSpeed Insights show how real visitors experience your pages through Core Web Vitals, and a host with a nearby data centre and good caching gives you a strong base for improving them.

What you can do on your side: themes, images and plugins

Hosting provides the foundation, and a few changes on your side make the most of it:

• Choose a lightweight theme and avoid page builders that load large scripts on every page, unless you use their features
• Size and compress images before upload, and use modern formats such as WebP or AVIF
• Audit your plugins: remove anything unused, and use your host's performance tools to spot the slow ones
• Limit third-party scripts such as chat widgets, trackers and embedded feeds, which load from other servers
• Host fonts sensibly: fewer font families and weights mean fewer files to download
• Keep WordPress, plugins, themes and PHP up to date, testing updates on staging first
• Follow your host's caching rules: use the caching it provides and only the caching plugins it supports

Running a shop? Our WooCommerce hosting guide covers the extra care that baskets and checkouts need.

How do you test hosting speed fairly?

Speed tests vary from run to run, so a single result proves very little. A fair test compares like with like:

1. Choose three or four real pages: the home page, a typical content page and a product or checkout page if you have one.
2. Use the same tool and the same test location for every run, ideally one close to your real visitors.
3. Run each test several times and look at the typical result, not the single quickest one.
4. Record time to first byte, Largest Contentful Paint and Interaction to Next Paint.
5. Test both cached pages (logged out) and uncached pages (logged in, or with items in a basket).
6. Create a staging copy on each host you are considering and run the same tests before you switch DNS.
7. Test again a week after the move, once caches are warm and real traffic is flowing.

Published benchmarks can be a starting point, but check how they were run: which plan, which site, from where and under what load. Your own pages on your own plan are the test that matters. For how cloud infrastructure fits in, see our guide to WordPress cloud hosting.

Next step: test hosts with your own pages

The practical way to find the fastest WordPress hosting for your site is to try your own pages on the hosts you are considering:

• Shortlist hosts with a data centre close to your visitors and the caching your site needs, using our WordPress hosting comparison
• Check trial terms on each host's own site, so you can test without committing; Cloudways and Krystal each describe a trial, and Krystal also lists a money-back period on its standard hosting
• Move a staging copy using the host's migration help, then run the same tests on each
• Choose on your results, alongside support, backups and how each host bills

Our picks for UK WordPress hosting summarises the three hosts, and our managed WordPress hosting guide explains what the host takes off your hands.