Performance Glossary
WooCommerce: Optimising the Uncacheable Half
Your product pages score well and your checkout does not, because only one of the two was ever allowed to be served from cache.
The short answer
WooCommerce turns WordPress into a full storefront — catalogue, basket, checkout and order handling — on a platform you own outright, with no per-sale cut taken by the software vendor.
Its performance profile is entirely different from a blog's, because basket, checkout and account pages must not be cached. That single constraint is why a store leans on object caching, PHP worker headroom and database speed rather than on page caching alone.
By the HostingFast team · Reviewed 12 August 2026
0
Terms, measured not asserted
100+
Entries wired together
Real
Runnable commands
Free
Free to read, always
A very large share of the world's online stores run on it, and the reasoning is arithmetic: no monthly platform rent, no percentage of every sale, no capability withheld behind a higher tier.
It does make specific demands of hosting. The pages that convert are the pages a page cache cannot serve, so the infrastructure has to be quick at exactly the work a brochure site never asks it to do.
Which URLs must miss the cache
Cart, checkout, my-account and anything carrying a session cookie have to bypass page caching, or customers see each other's baskets. Product and category pages should be cached aggressively. Getting that boundary right is the first configuration job on any store, and the commonest thing to find wrong.
Verify it by requesting each of those URLs and reading the cache status header, then repeating the checkout path with a session active. A store where checkout is being cached is a much worse problem than a slow one.
Cart fragments and the ajax tax
WooCommerce keeps the mini-basket accurate with an admin-ajax request fired on page loads across the site, including cached ones. That request runs the full application, so it is an uncached hit riding along with every otherwise-free page view.
Measure it before deciding anything. Look at the timing of the cart fragments call in the Network panel and at how often it appears in your logs. On stores where the mini-basket is not visibly used, limiting that request to store pages removes a large slice of uncacheable load at no cost to the customer.
Redis, and the queries behind checkout
Object caching keeps query results in memory between requests, which is the layer that helps pages a page cache is forbidden from touching. On a store that is precisely where the money is, so Redis behind checkout is not an extra — it is the caching that matches the workload.
Underneath it, the usual database discipline applies. Order and order meta tables grow forever, and once the working set stops fitting in memory every checkout query starts reaching for disk. NVMe softens that; pruning what nothing reads removes it.
Load-testing the path that earns
Test the checkout flow, not the homepage. Add to basket, view basket, reach the payment step, at a concurrency that matches your busiest realistic hour, and watch response times and PHP worker usage together. That is the capacity number a promotion will find out for you otherwise.
Rehearse it on staging with a full copy of the catalogue and order history. A load test against a trimmed database tells you the store is fine, which is exactly the wrong thing to learn the week before a sale.
Commerce hosting, judged on the checkout
A store's speed is decided on the pages a cache is not allowed to serve, so these entries measure there rather than on the homepage.
Our WooCommerce plans pair Redis object caching with NVMe storage and headroom reserved for checkout, plus staging to rehearse a sale on.
- Cache boundary verified, not assumed
- Cart fragments measured before removal
- Object caching where page caching cannot go
- Load tests aimed at the checkout
Why HostingFast
Standard on every plan
The right pages excluded
Which URLs must bypass page caching, and the header check that proves the boundary is where you think.
The ajax cost quantified
What cart fragments do to otherwise-cached page views, and how to decide whether yours are earning their keep.
Caching matched to workload
Why object caching, not page caching, is the layer that helps the pages a store actually converts on.
Order tables treated as growth
What happens to checkout queries once the working set stops fitting in memory, and what to prune.
Capacity found before the sale
Load-testing the basket-to-payment path at realistic concurrency, on a full copy of the data.
Ownership as arithmetic
No platform rent and no per-sale percentage, set against the maintenance that comes with running it yourself.
Quick Start
From order to online
- 1
Confirm the cache exclusions
Request cart, checkout and account with a session active and read the cache status. Anything cached there is a correctness bug, not a speed one.
- 2
Time the cart fragments request
Find it in the Network panel and note its duration and frequency. That number decides whether limiting it to store pages is worth doing.
- 3
Load-test basket to payment
Run the converting path at your realistic peak concurrency on staging, with the full catalogue, and watch worker usage alongside response time.
Built In
Loaded onto every plan
- LiteSpeed compiled into the server, not a caching plugin bolted on afterwards
- NVMe on every tier — the entry plan runs the same drives as the top one
- Staging you can clone, break and throw away before anything reaches live
- PHP version selectable per site, switched from the control panel in seconds
- Daily backups with a self-service restore you run yourself from the panel
- Free SSL on every plan, reissued automatically well before it can expire
- DDoS filtering absorbed at the network edge, before it reaches your workers
- Softaculous installers for WordPress and 400+ further applications
- A human on support at any hour, including for the awkward questions
- 99.9% uptime as the target, monitored around the clock
Frequently Asked
What people ask us most often
Why is my checkout slow when the rest of the store is quick?
Because the rest of the store is cached and checkout is not, by design. Those pages run the full application and hit the database on every request. Object caching with Redis, enough PHP worker headroom and a database whose working set fits in memory are the three things that move that number.
What should I look for in hosting for a store specifically?
Object caching available and configured, page caching that correctly excludes basket and checkout, NVMe storage under the database, and a backup schedule matched to your order volume. That combination is what our WooCommerce plans are put together to provide.
Can I run a restore without opening a ticket?
Yes. Every plan takes a daily backup and the restore runs from your own panel — files, databases or both — at whatever hour you discover the problem. Keeping an additional copy somewhere off our network remains good practice, and nothing in the platform stops you doing it.
Does the price move at renewal?
No. You renew at the rate you ordered at, every term, because there is no introductory teaser price to fall off. Every invoice sits in your client area and auto-renewal is a toggle in the account rather than a phone call to somebody's retention desk.
Keep reading
Redis
In-memory object caching for the queries a page cache never gets to see.
WordPress
The PHP application under four in ten websites, and what decides its speed.
Best Magento vs WooCommerce
Two commerce stacks weighed on hosting cost, checkout latency and who maintains what.
Plesk Reseller Hosting
Plesk-based reseller accounts for teams that prefer the Plesk workflow.
VPS Hosting
KVM virtual servers with root access, DDoS filtering and one flat monthly price.
Changing hosts? Run through our checklist first.
A straightforward sequence for a switch your visitors never feel: which files move first, how to shift email across without losing a single message, the right moment to repoint DNS, and the two mistakes behind almost all the downtime we get asked to rescue.
Optimise where the orders actually happen.
Redis object caching, NVMe storage and headroom reserved for checkout, with staging to rehearse the sale on first.
View Plesk Reseller Hosting plans