WooCommerce hosting for UK online shops

What does a WooCommerce shop need from its host?

WooCommerce is a WordPress plugin that adds products, a basket, a checkout and order management to a WordPress site. That makes WordPress ecommerce hosting a little different from hosting an ordinary site, because the server does different work for different pages.

A shop has two kinds of page. Catalogue pages, such as the home page, categories and product pages, look the same to every visitor, so they can be cached and served quickly. Personal pages, such as the basket, the checkout and the customer's account, are different for every shopper, so the server has to build them each time with PHP and database queries. Logged-in customers, stock checks and calls to payment and shipping services all add to that work.

When you compare WooCommerce hosting, these are the points to check on each host's own site:

For UK customers, location matters most for the uncached pages. Cloudways and WP Engine each list a London location on their own sites; see UK-based WordPress hosting.

Caching that leaves basket and checkout alone

Page caching stores a finished copy of a page and hands it to the next visitor without running WordPress again. It is the biggest single speed gain for most sites, but it would break a shop if it cached the wrong pages: one shopper could see another's basket, or a price that has since changed. Here is what each host says about it:

• Cloudways says its servers include Memcached, Varnish and Redis caching, and that its Breeze cache plugin "comes pre-installed on WooCommerce stores". On its Autonomous plans it adds Object Cache Pro, which it says keeps checkout and cart pages quick
• Krystal runs managed WooCommerce hosting on its Onyx platform with LiteSpeed caching, and pre-installs the LiteSpeed Cache plugin. Its help centre says other caching plugins should be removed, and that "Caching is not a one click solution", so test each change
• WP Engine lists the pages it never caches (store, cart, checkout and check-out) and adds more exclusions when it detects WooCommerce, including account password resets, the WooCommerce API and WooCommerce's basket cookies

One point matters for UK shops in particular. Many rename the cart page to /basket/, and WP Engine's WooCommerce guide says: "If you are using custom page URLs (EX: /basket) those pages will need to be excluded manually by reaching out to our Support team." Whichever host you choose, check that a renamed basket, checkout or account page is excluded from the cache, and test it on a staging copy: add something to the basket in one browser and make sure it does not appear in another. Do the same for trade pricing or a currency switcher. Our guide to fast WordPress hosting covers caching layers in general.

Finding slow extensions with performance tools

Most slow shops are slow for a reason you can find: an extension that runs a heavy query on every page, a shipping-rate lookup that waits on an outside service, or a stock sync that runs at the wrong moment. The hard part is knowing which one. Several hosts give you tools for this:

• Cloudways describes server and application monitoring for troubleshooting, and offers Object Cache Pro and Redis to take repeated work off the database
• Krystal says its platform shows live requests, error logs and resource usage, and combines LiteSpeed page caching with Redis object caching
• WP Engine offers application performance monitoring as an add-on on its Business and Enterprise plans, and Site Monitoring with alerts

A simple way to use any of these tools:

1. Reproduce the problem while the tool is recording: add products to the basket, choose a delivery option and go through checkout.
2. Look at the slowest requests and see where the time goes: PHP, database queries or calls to outside services.
3. Follow the trail to the plugin, theme function or external service responsible.
4. Try the fix on a staging copy: update, reconfigure or replace the extension.
5. Run the same journey again and compare the timings before you push the change live.

Common culprits are payment and shipping calls, product filters on large catalogues, stock syncs and reporting plugins. If the shop is busy rather than slow, the answer is more capacity; see WordPress hosting plans.

WooCommerce options at each host

Each host packages shop hosting in its own way: on cloud servers you choose, on a managed WooCommerce platform, or as an ecommerce product on a managed WordPress platform. This is how each host presents its shop options today:

Cloudways suits shops that want to pick a cloud server and scale it; Krystal and WP Engine run a managed platform where the host looks after the server. Plans, limits and prices are on each provider's own site.

Security for shops: firewall, SSL and malware help

Shops hold customer accounts and order history, and checkout pages attract automated traffic, so security is part of choosing a host. Each host describes its own layers:

• Cloudways: a built-in server firewall, a WordPress vulnerability scanner, SSL certificates, and add-ons for Cloudflare Enterprise (DDoS mitigation at layers 3, 4 and 7) and malware protection
• Krystal: Intelligent Protection powered by Patchstack on every managed WordPress plan, malware scanning and removal, firewalls and DDoS protection
• WP Engine: a web application firewall, DDoS protection and automated backups, with its Global Edge Security add-on for managed WAF, bot management and advanced DDoS mitigation

Krystal and WP Engine both list ISO 27001, and WP Engine also lists SOC 2 Type II. Your side is keeping WooCommerce, its extensions and your theme up to date, limiting admin access and using two-factor sign-in; see secure WordPress hosting.

Can a host make your shop PCI DSS compliant?

PCI DSS is the card industry's security standard for any business that takes card payments. People search for PCI compliant WordPress hosting, but no host can make a shop compliant on its own: the standard covers how your business takes payments as well as where the site runs.

Most WooCommerce shops take cards through a payment gateway whose checkout fields send card details straight to the payment provider. WP Engine puts it this way: card payments "are processed by your chosen payment gateway ... which keeps cardholder data off your site and reduces your PCI DSS scope". Krystal's help centre makes the same point, adds that compliance is still required "just at a lower validation level", and says your payment provider decides which self-assessment applies to you.

Hosts describe their own part differently:

• Krystal says its Emerald, Sapphire, Diamond and Tanzanite web hosting plans are PCI DSS scan compliant, and that you stay responsible for compliance at site level
• WP Engine lists GDPR, ISO 27001 and SOC 2 Type II alignment for its eCommerce Solution, alongside the gateway point above

Questions worth putting to any host, using its own documentation and sales pages:

1. Does card data ever touch your servers with my chosen payment gateway, or is it handled entirely by the provider?
2. Which security standards does the host hold, and can I see its report or certificate?
3. If my provider asks for quarterly vulnerability scans, will the host adjust server settings when a scan flags something?
4. Which self-assessment questionnaire applies to my set-up? (Your payment provider answers this one.)

Backups and staging before you change the shop

Shops change often: WooCommerce itself, payment and shipping extensions, the theme and the checkout all get updates. Testing them on a copy first is the safest habit you can build. The care comes when you push changes back, because the live shop has taken orders since the copy was made, and orders live in the database.

That is why it matters whether a host lets you push only files, or choose individual database tables, rather than overwriting the whole live database:

The safe default is the same everywhere: send code changes as files only, leave the WooCommerce order and customer tables alone, back up just before you push, and push at a quiet time. Our guide to WordPress hosting with staging covers the whole workflow.

Moving a live shop without losing orders

If a customer orders on the old server after the copy is taken, that order never reaches the new one. A good move closes that gap, usually with a short maintenance window while the final copy is taken. WP Engine, for example, suggests a maintenance page before copying a store between environments, and Krystal says it updates DNS only once you are happy with the migrated site.

A typical shop move looks like this:

1. Pick a quiet time, using your sales data, and agree it with the new host if its team is doing the move.
2. List everything tied to your server or domain: payment gateway webhooks, shipping and stock integrations, IP allow lists, email sending and any API keys.
3. Put the shop into maintenance mode while the files and database are copied.
4. Test on the new host before switching: browse, add to the basket and complete a checkout with your payment gateway in test mode.
5. Update your DNS to point the domain at the new host, keeping your email (MX) and verification records as they are.
6. Take the shop out of maintenance mode, then watch new orders, order emails and webhooks for the first day.

Every host here offers migration help: Cloudways moves your first website, Krystal moves your first three sites, and WP Engine offers a migration plugin and managed migrations on Business plans. See moving a WordPress site to a new host.

Next step: compare shop-ready plans

Write down your shop's needs, then let the hosts' own pages show which plan fits:

• Traffic and busy periods: monthly visits, plus your peak days, because uncached checkouts at peak decide how much capacity you need
• Catalogue and database: number of products and variations, and whether filters and reports are heavy
• Basket and checkout addresses: so you can check that the host excludes them from its cache
• Integrations and location: services to update on a move, and where most of your customers are

Then read each host's shop page: Cloudways (opens in a new tab), Krystal (opens in a new tab) and WP Engine (opens in a new tab). Plans, limits and prices are on the provider's own site. For the wider picture, see our WordPress hosting comparison.