What separates WooCommerce hosting from ordinary hosting is not disk space. It is that three pages of your shop can never be cached, and those three are exactly where the money changes hands.
Cart, checkout and my-account render differently for every visitor. So each time somebody opens one, the request goes all the way down: PHP runs, the database is queried. A product page can be cached. The moment a customer decides to buy cannot.
Which means the things that matter are these
- Concurrent PHP workers. This is the number that decides how many people can sit in the checkout queue at once. When they run out, the next person waits.
- A persistent object cache. WooCommerce fires a lot of repeated queries per page. Without one, every single one of them reaches the database every time.
- Write speed on disk. Every order, every stock change and every login is a write. A shop writes far more than a brochure site does.
- How the plan behaves at its ceiling. Some hosts queue you, some return an error page. Ask which, before the sale day rather than during it.
Disk space is almost never the bottleneck, and it is precisely the figure printed largest in the hosting advert.
A page can only be cached if it is identical for everyone
That sentence is obvious, and most of the trouble comes from ignoring it. A page cache stores HTML output so PHP does not have to run next time. If the output differs per person, storing it means showing one shopper's basket to another.
So your shop has two halves that behave nothing alike: a public half that should be cached and should be fast, and a private half that must never be cached and needs a real server behind it. Good hosting for a shop means hosting that can carry the second half.
How to check your own setup
One command, no tooling:
curl -sI https://example.com/ | grep -i "cache"On the front page you should see some sign of caching. Run the same command against your cart and account paths, where you should not. If it comes back the other way round, either your public pages are needlessly uncached or your private pages are being cached, and the second is far more dangerous than the first.
We ran it on our own site and did not like the answer
On 18 August 2026 we ran that exact command against our own front page. It returned cf-cache-status: DYNAMIC with cache-control: no-cache. So although we have a cache rule configured at the content delivery network, our HTML is not being cached at the edge and every visit travels all the way to our own server.
The account page behaved correctly and was not cached, which is what it should do. But the public half is not cached either, and that is a fault rather than a decision. We are working on it, and when it is fixed we will publish the before and after.
We write this down because an agency that sells speed and only ever publishes its wins is not worth trusting. The command above returns a bad answer on our own site and you can run it right now.
The number that gets lost in the hosting decision
The same day, we measured the raw HTML weight of thirty-eight Persian sites. The median was 349 KB and the heaviest 3.1 MB, before a single image or script.
No hosting plan compensates for that. If your product page ships half a megabyte of HTML, upgrading the plan just sends the same payload faster. The order is: lighten first, then host. The long version is on the speed page, and the relationship between hosting and Google's metrics is in the piece on hosting, speed and SEO.
When you do not need WooCommerce hosting
If your shop takes a handful of orders a day and never has dozens of simultaneous visitors, ordinary shared hosting is enough and paying more buys you nothing. The practical boundary is where concurrency begins: a campaign, a sale, or anything that sends a hundred people to checkout at the same moment.
And if you do not have a shop yet, hosting is the earliest wrong decision to make. Build the shop first, and what it needs becomes obvious afterwards. Specifications sit on the WooCommerce hosting page and the broader options in the hosting section.
Questions we get
Is WooCommerce hosting different from WordPress hosting?
Not in software terms. Both run the same WordPress. The difference is in the resources set aside for pages that cannot be cached, and in whether an object cache is switched on.
Is caching the cart page actually a problem?
Yes, and a serious one. If personalised output gets cached, one shopper's basket can be served to another. Cart, checkout and account paths have to be excluded explicitly.
How many orders a day means it is time to upgrade?
We do not have a fixed number and anyone who gives you one is guessing. The real signal is checkout slowing down at your busy hour, not the daily order count.
Is cloud hosting better for a shop?
It depends entirely on how many concurrent workers and what kind of disk that plan gives you. The plan name does not tell you. You have to ask.
Comments & Questions
Have a question about this article? Ask, we'll answer.
No comments yet; be the first.