Store build · Beginner · 45 minutes, checkout timed
How to install WooCommerce — The Install Takes Ten Minutes. The Cache Exclusions Decide Everything
Your store is quick on the product pages and slow exactly where it matters, because the checkout is the one page nothing is allowed to cache.
The short answer
Get the caching rules right before you add a single product, because WooCommerce turns a mostly-static site into a mostly-dynamic one. Cart, checkout and account pages must be excluded from page cache or shoppers start seeing each other's baskets; everything else should be cached hard. LiteSpeed Cache applies those exclusions itself, and your job is to verify it did rather than assume it.
The three things that then decide how the store feels are an object cache holding repeated queries in memory, a current PHP release doing the work, and cart fragments — an AJAX request that many themes fire on every page view, including pages with no cart on them. This runbook covers each, and finishes by timing a real order end to end.
By the HostingFast team · Reviewed 24 August 2026
Beginner
Skill floor
45 minutes
Hands-on time
5
Numbered stages
24/7
Support cover
Forty-five minutes, from a clean WordPress to a test order that has been through a payment gateway and out the other side. Assumed: you can read a response header and a network waterfall, because that is how the cache work gets verified.
Two numbers to keep. Time to first byte on a product page, which should be a cache hit, and time to first byte on the checkout, which never will be. The gap between them is the honest measure of your store's performance.
Set the platform baseline before installing
WooCommerce inherits whatever it lands on. A current PHP 8.x release, switchable per site from the control panel, is the single largest free improvement available; an object cache is the second. NVMe storage under the database matters here more than on a brochure site because a store's traffic is disproportionately uncached.
Do this first rather than after the store is live. Diagnosing a slow checkout while orders are arriving is a much worse afternoon than spending ten minutes on the platform beforehand, and none of these settings are ones you want to change during trading hours.
Cache exclusions, and how to verify them
Cart, checkout and my-account must never be served from page cache. LiteSpeed Cache excludes them by default, but themes and page builders create custom endpoints the defaults do not know about — a one-page checkout at a bespoke URL is the classic case. Read the cache header on each of those URLs while logged in and while logged out.
The failure mode is memorable enough to be worth the check: a cached cart page served to a second visitor shows them somebody else's basket, and occasionally their address. Verify the header, then verify it again after any change to the theme or the cache configuration.
Cart fragments and the request on every page
Many themes load WooCommerce's cart-fragments script site-wide, which fires an uncacheable admin-ajax request on every page view — including the blog and the contact page. Open the Network panel on a page with no cart in sight and look for it. On a busy site that single request is a substantial share of total PHP work.
Restrict the script to pages that actually need it, or use a theme that already does. Then check what else is loading globally: payment gateway scripts, review widgets and shipping calculators frequently enqueue everywhere by default rather than only where they are used.
Push an order through, with a stopwatch
Install the gateway extension in test mode, add one genuine product with its price, stock figure and images, and buy it from a logged-out browser. Watch the order appear, the stock fall and the confirmation email leave. That loop proves more than reading the settings screen back to yourself ever will.
Time the checkout while you do it. Note the first-byte figure on the checkout page and on the order-received page — both uncacheable, both PHP and database work, both the part of the store that shapes conversion. Free SSL is already issued and renewing, so the padlock is in place before the first real card arrives.
What a store gets from this platform
Store-ready hosting means the uncacheable half is fast too: NVMe under the database, LiteSpeed compiled into the web server for everything that can be cached, per-site PHP switching, and staging clones for testing a gateway update before it meets a real card.
Daily backups on every plan, with restores you run yourself from the panel rather than raising a ticket.
- NVMe under the database, where an uncached checkout lives
- LiteSpeed compiled in, with Woo exclusions applied by default
- Per-site PHP switching from the control panel
- Staging clones for testing a gateway update safely
Why HostingFast
Standard on every plan
Platform first, store second
PHP version, object cache and storage are settled before the install, because fixing them later happens while orders are arriving.
Exclusions verified, not assumed
You read the cache header on cart, checkout and account yourself — logged in and logged out — including custom endpoints.
The site-wide AJAX request found
Cart fragments firing on every page is one of the largest hidden costs in a Woo install, and it takes one look at the Network panel.
Two numbers, honestly separated
Cached product page and uncacheable checkout are measured apart, because averaging them hides the part that converts.
A real order, end to end
Test-mode purchase, stock movement and confirmation email witnessed, which is the only proof the pipeline works.
Rehearsal space included
Staging clones and daily backups mean a gateway or plugin update gets tried on a copy before it meets a live card.
Quick Start
From order to online
- 1
Fix PHP, caching and storage first
Current PHP 8.x switched per site from the panel, object caching available, NVMe underneath. Ten minutes now against a bad afternoon later.
- 2
Install and run the setup wizard
WooCommerce from the plugin directory or Softaculous, then the wizard: address, currency, tax handling, shipping. Six screens replace a day of manual configuration.
- 3
Verify the cache exclusions
Load cart, checkout and my-account and read the cache header on each, logged in and out. Custom checkout endpoints from a theme are where the defaults miss.
- 4
Kill the site-wide cart request
Open the Network panel on a page with no cart. If cart fragments are firing, restrict the script to the pages that need it and re-check.
- 5
Buy your own product and time it
Gateway in test mode, one real product, one logged-out purchase. Watch the stock fall and the email leave, and note the checkout's first-byte figure.
Built In
Loaded onto every plan
- NVMe SSD storage on every tier, including the entry plan
- LiteSpeed caching compiled into the server, not bolted on by plugin
- Per-site PHP version switching from the control panel
- Staging environments for rehearsing a change before it ships
- Daily backups on every plan, with restores you run yourself from the panel
- Free SSL on every plan, reissued automatically before it can expire
- cPanel — the control panel most of the industry already runs
- WordPress and 400+ other applications installed in one click
- In-place account upgrades, with no migration when you change plan
- Human support on duty every hour of every day
Frequently Asked
What people ask us most often
Which WooCommerce pages must be excluded from page cache?
Cart, checkout and my-account at minimum, plus any custom endpoint your theme or a one-page-checkout plugin introduces. LiteSpeed Cache handles the standard ones itself; the custom ones are where sites get caught. Read the cache header on each URL logged in and logged out — a cached cart served to a second shopper shows them somebody else's basket.
Does an object cache actually help a WooCommerce store?
More than on almost any other kind of site, because a store's traffic is heavily uncacheable at the page level and therefore heavily dependent on repeated database lookups. Redis keeps those results in memory so the second identical query in a request never reaches MySQL. Check the plugin reports a live connection rather than merely being installed.
How do I tell whether cart fragments are loading on every page?
Open the Network panel on a page with no cart on it — a blog post, the contact page — and look for the admin-ajax request. If it is there, the script is enqueued site-wide and every visitor is paying for an uncacheable PHP request they have no use for. Restricting it to store pages is usually a theme setting or a few lines in the child theme.
What slows a WooCommerce checkout more, PHP or the database?
Usually the database, because the checkout is uncacheable and runs a lot of queries against orders, sessions and product metadata. That is why NVMe storage and an object cache matter here more than on a brochure site. Measure it rather than assume: profile the checkout with Query Monitor and the top of the duration list will settle it in seconds.
Keep reading
How to Set Up Domain Forwarding
Send every visitor from one name to another in a single hop, with the certificate valid on both — beginner, roughly 5 minutes.
How to Fix Common SSL Errors
Turn each browser warning into the specific repair it is asking for, chain problems included — intermediate, roughly 20 minutes.
Best WooCommerce vs Shopify
The same decision as a buying guide: which specifications actually matter for a store, and the plan we would sign.
WooCommerce Hosting
Store-ready hosting with Redis caching and headroom reserved for checkout traffic.
Domain Names
Search, register and transfer names — year one free when you order annual hosting.
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.
Put the checkout on NVMe.
Redis caching, LiteSpeed compiled into the server, per-site PHP control, staging clones and daily backups you restore yourself.
View WooCommerce Hosting plans