---
title: 'Best WooCommerce Hosting: Every Benchmark You''ve Read Measured the Wrong
  Page'
slug: best-woocommerce-hosting
excerpt: WooCommerce's own docs say Cart, Checkout and My Account must be excluded
  from caching — they 'need to stay dynamic'. So the cached-homepage speed tests that
  fill this search measured the one page a store doesn't sell from.
author: Axel Grubba
created_at: '2026-08-31T11:00:00Z'
updated_at: '2026-08-31T11:00:00Z'
categories:
- software
tags:
- comparisons
---

**Here is WooCommerce's own guidance on caching**, read on 18 August 2026. Exclude these pages from the cache:

> **Cart** · **My Account** · **Checkout**
>
> *"These pages need to stay dynamic since they display information specific to the current customer and their cart."*

**Those are the three pages a store actually sells from.** And they are, by design, the three that page caching cannot help.

**So consider what a typical "fastest WooCommerce hosting" benchmark measures:** a cached homepage, served from a static file, often from an edge node. **That number tells you how fast a host serves a file.** It tells you nothing about whether a checkout completes under load, because checkout never touches that path.

**The correct question is: how fast is PHP, and how fast is the database?** Those are what serve cart, checkout and my-account on every single request, for every single customer, uncached.

## What else WooCommerce tells you not to cache

The same document goes further, and these details matter for anyone configuring a host's caching layer:

**Database caching:** exclude `_wc_session_`. WooCommerce stores the customer's session there, and caching it serves one shopper another's state.

**Cookies to exclude:**

| Cookie | Purpose |
|---|---|
| `woocommerce_cart_hash` | Detects when cart contents change |
| `woocommerce_items_in_cart` | Tracks items in the cart |
| `wp_woocommerce_session_` | Unique per-customer code locating their cart in the database |

**The failure mode when this is wrong is the worst one in ecommerce:** a cached page served to the wrong customer, showing someone else's cart or account. **It's not a speed problem, it's a correctness problem** — and it's why "we cache everything aggressively" is not the boast some hosts think it is.

**Ask your host how it handles these exclusions.** A host that answers precisely is running a real WooCommerce platform.

## The version floor is higher than most hosts default to

WooCommerce publishes hard requirements, and for **WooCommerce 10.8 and later** they are:

| Component | Requirement |
|---|---|
| **WordPress** | **6.9 or greater** |
| **PHP** | **8.3 or greater** (tested up to 8.4) |
| **MySQL** | **8.0 or greater** |
| **MariaDB** | **10.6 or greater** |

**PHP 8.3 is a meaningful filter.** Plenty of hosting plans still default to 8.1 or 8.2, and a host that can't offer 8.3 can't run current WooCommerce.

**On the legacy path**, WooCommerce is explicit and worth quoting because it reads as a warning rather than a permission: it still works with PHP 7.4+ and MySQL 5.6+, *"However, these versions have reached their official End of Life and may expose your site to security"* risks.

**So: PHP 8.3 minimum, and treat anything lower as a reason to move**, not a configuration to accept.

## How to buy, given all that

**Prioritise, in this order:**

1. **PHP execution speed.** Every uncached cart and checkout request is PHP work. This is the number that decides whether checkout survives a sale.
2. **Database performance.** Cart and session operations are writes, and writes don't cache. NVMe and a properly resourced database tier matter more than they would for a blog.
3. **Object caching (Redis/Memcached).** This *does* help uncacheable pages, because it caches database query results rather than whole pages. **It's the caching layer that actually applies to WooCommerce**, and it's the one to ask about.
4. **Page caching, configured correctly.** Still valuable for product and category pages — most of your traffic — provided the three exclusions above are right.
5. **Edge/CDN.** Real for images and assets, largely irrelevant to checkout.

**The reason the expensive managed hosts are often worth it** isn't the speed claim on their homepage. It's that they configure the exclusions correctly, run object caching by default, and put the database somewhere sensible. **That's worth paying for — just not for the reason it's advertised.**

## The hosts

**[Nexcess](https://findstack.com/go/nexcess)** — **fully managed WooCommerce is its core product**, not an add-on to shared hosting, and it's the platform we'd ask the caching-exclusion question first. **The natural default for a store on revenue** where you want the stack configured by someone who's done it before.

**[Kinsta](https://findstack.com/go/kinsta)** — premium managed WordPress with a strong performance reputation. **We have not verified its current WooCommerce pricing, PHP versions or object-caching configuration**, so evaluate it against the checklist above rather than the marketing.

**[Rocket.net](https://findstack.com/go/rocket-net)** — managed WordPress built on Cloudflare's enterprise network, positioned squarely on speed. **Worth asking specifically how it treats cart and checkout**, because an edge-first architecture is strongest on exactly the pages WooCommerce says not to cache — and that's where the interesting answer lies.

**[Cloudways](https://findstack.com/go/cloudways)** — managed servers on DigitalOcean or AWS **from $11 for 2GB**, with published SLA tiers of 12 hours on the free tier down to 2 hours at roughly $500/month. **Read the exclusions before relying on it for a store**: debugging custom code and **application-level security issues are out of scope on every tier**, and [on a WooCommerce site that covers your plugins and your checkout](/resources/is-cloudways-worth-it).

**[Liquid Web](https://findstack.com/go/liquid-web)** — names WooCommerce explicitly among its managed applications and **publishes the clearest support-scope matrix of any host we've examined**, stating exactly which tier stops troubleshooting your server. **For a store carrying revenue, a documented boundary beats a vague promise.**

**[SiteGround](https://findstack.com/go/siteground)** — widely used for WooCommerce. **We could not read its pages from either of our vantage points** — it returned 403 in the US and geo-redirected in Europe — so we have **no verified pricing or specifications** to offer, and we're not going to characterise it from memory.

**[Hostinger](https://findstack.com/go/hostinger)** — **the budget end**: $10.99 renewal on shared Premium, or **$11.99 for a 4GB VPS** if you'd rather own the stack. **Viable for a small store**, though [its terms carry no support commitment](/resources/hostinger-support-review), so you'd be configuring the exclusions yourself. Check the PHP version is 8.3 or higher before committing.

## How we checked this

**The caching guidance is quoted from WooCommerce's own documentation** on configuring caching plugins, read on 18 August 2026: the instruction to exclude **Cart**, **My Account** and **Checkout**, the reason that *"These pages need to stay dynamic since they display information specific to the current customer and their cart"*, the advice to exclude `_wc_session_` from database caching, and the three cookies — `woocommerce_cart_hash`, `woocommerce_items_in_cart` and `wp_woocommerce_session_` — with the purposes WooCommerce gives for each.

**The version requirements are from WooCommerce's server requirements page**, which states them for **WooCommerce 10.8 and later**: WordPress 6.9+, PHP 8.3+ tested to 8.4, MySQL 8.0+ or MariaDB 10.6+, plus the legacy note that PHP 7.4+ and MySQL 5.6+ still work but have reached End of Life.

**There is no load test in this article, and the brief was built around one.** It specified hitting cart, checkout and my-account at 100, 250 and 500 concurrent sessions across seven hosts and publishing p95 response times and error rates. **We hold no accounts at these providers** — and separately, **driving 500 concurrent sessions at infrastructure we don't own is not something we'd do to companies we then earn commission from**, account or not. **So the entire quantitative half of the intended article is missing**, and you should weigh that: what's here is the methodological argument and the vendor documentation, not evidence about which host is fastest.

**We are confident the argument is right and cannot show you the numbers.** That's an uncomfortable position for a "best hosting" page and we'd rather state it than dress up a ranking as a test.

**On the hosts:** Cloudways' SLA tiers and out-of-scope list, and Liquid Web's support matrix, were verified earlier in this series. **SiteGround was unreachable from both our German and US vantage points**, so it carries no figures. **We have not verified Kinsta's, Nexcess's or Rocket.net's current WooCommerce pricing, PHP versions or caching configuration at all** — their entries describe published product positioning, nothing more. Hostinger's prices are figures established across this series rather than re-read today.

**We also did not verify** which of these hosts actually exclude the three pages correctly by default, which was the obvious follow-up question. **That would need an account on each and a test store**, and it's the thing we'd most want to know.

**What we did not do:** run a WooCommerce store, install a caching plugin, measure a checkout, generate load, or hold an account with any provider here.

The host links above are affiliate links. **The article's central advice — ask how your host handles WooCommerce's three cache exclusions — is free, applies to whatever host you're already on, and may well tell you that you don't need to move.**

## FAQ

**What's the best hosting for WooCommerce?**

One with fast PHP, a properly resourced database and object caching — because cart, checkout and my-account can't be page-cached. Managed WooCommerce specialists configure this correctly, which is their real value.

**Why don't speed tests reflect my store's performance?**

Because most measure a cached homepage. WooCommerce's own documentation says Cart, My Account and Checkout must be excluded from caching, so those benchmarks test a path your customers don't use when buying.

**What are WooCommerce's server requirements?**

For WooCommerce 10.8 and later: WordPress 6.9+, PHP 8.3+ (tested to 8.4), and MySQL 8.0+ or MariaDB 10.6+. PHP 7.4 still works but is End of Life.

**Which pages should not be cached in WooCommerce?**

Cart, My Account and Checkout. Also exclude `_wc_session_` from database caching, and the `woocommerce_cart_hash`, `woocommerce_items_in_cart` and `wp_woocommerce_session_` cookies.

**Does a CDN speed up WooCommerce checkout?**

Not meaningfully. A CDN serves assets and cached pages; checkout is uncacheable by design and runs PHP and MySQL on your origin every time.

**Is Redis worth it for WooCommerce?**

Yes — object caching stores database query results rather than whole pages, so unlike page caching it does help the uncacheable pages. It's the caching layer that actually applies here.

**Is managed WooCommerce hosting worth the money?**

Often, but for the unglamorous reason: correct cache exclusions, object caching by default and a sensible database tier. Not for the headline speed figure.