Plugin how-tos · Guide
What Are the Best LiteSpeed Cache Settings for WooCommerce?
Short answer
For WooCommerce, set LiteSpeed Cache to exclude the cart, checkout and My Account pages, turn on ESI so the cart stays personal while product pages stay cached, and leave the default public TTL of 1 week in place. Confirm the exclusions in Cache > Excludes, enable ESI in Cache > ESI, and test with a private browser window before you take orders.
Key takeaways
- Cart, Checkout and My Account are excluded from LiteSpeed Cache by default, but you should still confirm the exclusion.
- ESI keeps the cart personal while product pages stay cached, and LiteSpeed highly recommends it for WooCommerce.
- The default public cache TTL is 604800 seconds, or 1 week, and WooCommerce uses the front page TTL for the Shop page.
- Object cache needs Redis or Memcached on the server; LiteSpeed Cache does not provide it itself.
- A product page should show X-LiteSpeed-Cache: hit on reload, while cart and checkout show no-cache.
- Never run a second cache plugin with LiteSpeed Cache; LiteSpeed lists WP Rocket and W3 Total Cache as conflicts.
What does LiteSpeed Cache do for a WooCommerce store?
LiteSpeed Cache stores finished copies of your product, category and home pages at the server, so repeat visits skip PHP and database queries.
A page cache lets the server bypass PHP and database queries, and LiteSpeed's plugin page states that its link with the server lets it track cache entries and purge them by tag. WooCommerce support is listed as a LiteSpeed exclusive feature. The plugin is free, and its general features work on any web server.
The page cache itself needs LiteSpeed hosting or the QUIC.cloud CDN. WordPress.org lists four options: LiteSpeed Web Server Enterprise with the LSCache module (v5.0.10 or later), OpenLiteSpeed (v1.4.17 or later), LiteSpeed WebADC (v2.0 or later), or QUIC.cloud CDN.
If your host runs Apache or NGINX without QUIC.cloud, only the optimization features work. You can set up LiteSpeed Cache with QUIC.cloud to get the page cache on any server.
What do you need before you change any settings?
You need a current backup, a staging copy or a quiet hour, WooCommerce already installed, and LiteSpeed Cache 7.9.3, released on November 3, 2026.
Check your hosting first, because the page cache only runs on a LiteSpeed server or through QUIC.cloud. Ask your host which server you run, or look for LiteSpeed in your hosting panel. If you are unsure, the plugin still gives you minification, image optimization and lazy loading on any server.
Update WooCommerce and LiteSpeed Cache before you start, and test on staging when you can. Our guide to updating WooCommerce safely walks through backups and staging first. Allow about 30 minutes for a small store, plus time to test the cart and checkout.
If the store still feels slow after caching, look at the wider speed checklist in our guide to speeding up WordPress.
How do you turn on page caching for WooCommerce?
Install LiteSpeed Cache, open LiteSpeed Cache > Cache, and set Enable Cache to ON.
- Go to Plugins > Add New, search for LiteSpeed Cache, then install and activate it.
- Go to LiteSpeed Cache > Cache and open the Cache tab.
- Set Enable Cache to ON and save.
- Open LiteSpeed Cache > Toolbox > Purge and press Purge All to clear any old cache.
Enable Cache is the final switch, and LiteSpeed's Cache docs say turning it OFF stops caching and purges all cached pages.
Leave Cache Logged-in Users at its default ON value, because the docs say logged-in pages are stored in private cache by IP address and session ID. If one customer sees another customer's data, turn it OFF and purge everything.
The Cache screen holds more than the on switch. Our guide to LiteSpeed Cache settings explained covers the full screen for non-store sites.
Which WooCommerce pages must never be cached?
Cart, Checkout and My Account must never be cached, because each one shows data that belongs to one shopper.
LiteSpeed's Cache docs say the My Account, Checkout and Cart pages are excluded by default, and WooCommerce's performance guide says dynamic content such as cart and checkout pages must stay uncached. Confirm the exclusion in LiteSpeed Cache > Cache > Excludes, under Do Not Cache URIs. Add /cart/, /checkout/ and /my-account/ if any of them are missing.
Also exclude the add-to-cart request and the session cookies. Add add-to-cart to Do Not Cache Query Strings, so a URL such as ?add-to-cart=123 is never served from cache. WooCommerce's caching guidance names three session cookies to keep out of the cache: woocommerce_cart_hash, woocommerce_items_in_cart and wp_woocommerce_session_.
Check your WooCommerce page setup too, because LiteSpeed's docs warn that misconfigured page associations in WooCommerce settings may cause pages to be classified incorrectly. Open WooCommerce > Settings > Advanced > Page setup and confirm Cart, Checkout and My Account each point at the right page.
How do you set up ESI for the cart and checkout?
ESI, or Edge Side Includes, lets the server cache a whole page while keeping small parts such as the cart total fresh for each shopper.
LiteSpeed's Cache docs highly recommend ESI for WooCommerce, because it allows flexible caching of mixed public and private data in a store. Go to LiteSpeed Cache > Cache > ESI and set Enable ESI to ON. The WooCommerce shopping cart is treated as a private ESI block, so the cart stays personal while product pages stay cached.
ESI has a cost. LiteSpeed's docs note it is simpler for the server to return full pages than to assemble them from several blocks. ESI is not available in OpenLiteSpeed, so stores on OpenLiteSpeed skip this step and rely on the exclusions above.
If you use the Recently Viewed Products widget, LiteSpeed's compatibility list says to set Enable ESI to ON in Cache > ESI. The plugin respects WooCommerce's own cacheability rules, so ESI works with the exclusions rather than against them.
What should the WooCommerce tab settings be?
Open LiteSpeed Cache > Cache > WooCommerce, which appears only when WooCommerce is active, and set Product Update Interval so stock changes purge the right pages.
LiteSpeed's Cache docs describe Product Update Interval as follows: purge the product when its quantity or stock status changes, and purge categories only when the stock status changes.
That keeps a product page fresh after a sale without purging the whole shop. Leave the other settings in this tab at their defaults unless a specific problem points at one of them.
What TTL values work best for a store?
Keep the defaults for most stores: 1 week for public pages and the shop page, and 30 minutes for private pages.
| Setting | Default value | What it controls |
|---|---|---|
| Default Public Cache TTL | 604800 seconds (1 week) | Product, category and post pages |
| Default Front Page TTL | 604800 seconds (1 week) | Front page, and the Shop page in WooCommerce |
| Default Private Cache TTL | 1800 seconds (30 minutes) | Pages cached privately for logged-in users |
| Default REST TTL | 604800 seconds (1 week) | REST API responses |
| Default HTTP Status Code Page TTL | 3600 seconds (1 hour) | 403, 404 and 500 pages |
LiteSpeed's Cache docs list these defaults and note that any value of 30 seconds or more sets a TTL, while smaller values mean the page is not cached.
WooCommerce uses the front page TTL for its Shop page, so a shorter front page TTL also shortens shop caching. Shorten the public TTL only if your prices or stock change every day.
Serve Stale is OFF by default and suits busy stores. LiteSpeed's docs explain that with Serve Stale ON, visitors get the most recently purged copy while the fresh copy is built, which avoids a rush of PHP requests. Quiet stores can leave it OFF.
Should you turn on object cache for WooCommerce?
Yes, if your host provides Redis or Memcached, because object cache stores repeated database results instead of running the same queries again.
LiteSpeed Cache does not provide object caching itself. LiteSpeed's Cache docs say it supports external object caches such as Memcached and LiteSpeed's LSMCD replacement, plus Redis. Object Cache is disabled by default, so set it to ON and pick Memcached or Redis as the Method, then add the host and port your host gave you.
Ask your host first, because the Redis or Memcached service must run on the server before this setting does anything. If the status area in the Object tab shows errors, LiteSpeed's docs point to its object cache debugging guide. A store without an object cache service should leave this OFF.
Which Page Optimization settings are safe for a store?
Minify CSS and HTML, lazy-load images and defer non-critical JavaScript are safe for most stores, but change one setting at a time and test the cart after each change.
The plugin page lists minification of CSS, JavaScript and HTML, combining CSS and JavaScript, automatic critical CSS, lazy loading of images and iframes, asynchronous CSS loading and delayed JavaScript loading.
WooCommerce's performance guide also recommends minifying HTML, CSS and JavaScript, inlining critical CSS and deferring non-critical JavaScript. Turn these on one at a time under LiteSpeed Cache > Page Optimization.
Never run two caching or optimization plugins at once. LiteSpeed's compatibility list marks WP Rocket, W3 Total Cache and WP Super Cache as potential conflicts, because they duplicate caching and optimization features. If checkout breaks after a JavaScript change, turn off JavaScript minification and delay first, purge the cache, and test again.
How do you check that caching works and the cart stays fresh?
Purge the cache, reload a product page twice, and confirm the second load shows a cache hit while the cart page shows no cache.
- Go to LiteSpeed Cache > Toolbox > Purge and press Purge All.
- In a logged-out browser window, open a product page and reload it once.
- Open developer tools, go to the Network tab, click the page request and look for X-LiteSpeed-Cache: hit.
- Open the cart and checkout pages the same way and confirm they show X-LiteSpeed-Cache-Control: no-cache.
- Add a product to the cart, then open the cart in a private window and confirm it is empty.
LiteSpeed's verification docs describe exactly this check: the first load shows X-LiteSpeed-Cache: miss, and the reload shows X-LiteSpeed-Cache: hit. For pages that must stay dynamic, the docs say X-LiteSpeed-Cache-Control: no-cache means the server served the page fresh on purpose. The LSCache Check Tool also gives a Yes or No answer for any URL.
Finish with a full order test on staging, or a real order you refund right away. WooCommerce's performance guide recommends regular testing with Google PageSpeed Insights, GTmetrix or WebPageTest. If the cart ever shows another shopper's items, purge everything and re-check the exclusions before you take another order.
If you also use a CDN, check its rules too. Our guide to Cloudflare cache rules for WordPress shows how to keep the CDN from caching the same dynamic pages.
What mistakes should you avoid?
The costliest mistake is caching a page that shows one shopper's data to everyone else.
- Caching the cart, checkout or My Account pages, which can show one shopper's order to the next.
- Running a second cache plugin, such as WP Rocket or W3 Total Cache, next to LiteSpeed Cache.
- Turning on every optimization setting at once, so you cannot tell which one broke the checkout.
- Forgetting to purge after a change. Purge All on Upgrade is OFF by default, and LiteSpeed's docs recommend turning it ON.
- Enabling Cache Mobile without a reason. It is OFF by default and mainly helps non-responsive themes, per LiteSpeed's Cache docs.
- Turning on Cache Login Page, which defaults to OFF as of LiteSpeed Cache 7.9.
- Skipping the private-window cart test before you call the job done.
Frequently asked questions
Do I need a LiteSpeed server to use LiteSpeed Cache with WooCommerce?
No, but you need one for the page cache. The plugin's general features, such as minification, image optimization and lazy loading, work on any server. The server-level page cache and ESI need LiteSpeed Web Server Enterprise, OpenLiteSpeed, LiteSpeed WebADC or the QUIC.cloud CDN. On Apache or NGINX without QUIC.cloud, you get the optimization features only.
Why does my cart show the wrong items after I turn on caching?
A cached cart, checkout or account page is the usual cause. Check LiteSpeed Cache > Cache > Excludes and confirm Cart, Checkout and My Account are listed under Do Not Cache URIs. Also confirm the session cookies are excluded, then purge all cache and test the cart in a private browser window. If the problem stays, turn off Cache Logged-in Users and purge again.
Can I cache the checkout page if I use ESI?
No. ESI keeps small parts of a page fresh, but the checkout page itself must still stay out of the public cache. LiteSpeed excludes Cart, Checkout and My Account by default. ESI helps the rest of the store: product and shop pages stay cached while the cart widget and other personal parts stay fresh for each shopper.
Should I turn on Cache Logged-in Users for a WooCommerce store?
You can leave it at the default ON value, because logged-in pages go into private cache keyed by IP address and session ID. That keeps one customer's pages separate from another's. If you ever see one customer viewing another customer's cart or account details, turn it OFF, purge all cache and re-test before taking orders.
How often should I purge the LiteSpeed Cache on a store?
Purge after every change to products, prices, stock or settings, and after plugin or theme updates. The automatic purge rules clear related pages when you publish or update content. Purge All on Upgrade is OFF by default, and LiteSpeed recommends turning it ON so updates clear stale pages for you.
Does LiteSpeed Cache work with the block-based cart and checkout?
Yes. The WooCommerce tab appears when WooCommerce is active, and the same exclusions apply to block-based cart and checkout pages. Keep Cart, Checkout and My Account out of the cache, keep ESI on for the cart fragments, and test the block checkout in a private window after every settings change.
Sources
- Cache | Screen-by-Screen | LSCache for WordPress LiteSpeed Documentation
- LiteSpeed Cache – WordPress plugin WordPress.org
- Third Party | LSCache for WordPress LiteSpeed Documentation
- How to optimize performance for WooCommerce stores WooCommerce Developer Docs
- Installation verify | LiteSpeed Documentation LiteSpeed Documentation
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
