Set up LiteSpeed Cache on WordPress and WooCommerce

LiteSpeed Cache connects WordPress to the LiteSpeed server cache. For a compatible public page, the server can reuse a response that has already been generated and avoid running WordPress on every visit. This is different from minifying files or turning on an object cache.

This guide helps you get it running and check it. For a broader review of images, queries and resources, continue with Speed up and optimise WordPress step by step.

Install and activate

1. Keep a recoverable backup and note the settings of your current cache.
2. Deactivate the other page caching plugin, if there is one, following its removal procedure.
3. In WordPress, open Plugins > Add New, search for LiteSpeed Cache and check that the author is LiteSpeed Technologies. Install and activate it from the official listing.
4. Open LiteSpeed Cache > Cache and check that Enable Cache is on. Names may vary with the translation.
5. Save and test before turning on additional optimisations.

You do not need to order a CDN to use our server's page cache. QUIC.cloud's online services, if you need them, have their own configuration and conditions.

Check a public page

Open a private window without logging in to WordPress. In the developer tools, go to Network, load a public page and review the headers of its HTML document. Repeat the visit: a stored response may show X-LiteSpeed-Cache: hit; the first may be miss.

Make sure you are looking at a request to the server, not just a copy from the browser's memory. A CDN can add another layer and other headers. It may be correct for the admin area or the cart not to return hit: they are not the reference for checking the public cache.

WooCommerce and personalised content

Check the cart, checkout, account, prices, currencies, languages and any user rules your shop uses. Test with two independent sessions to detect content shared by mistake.

Do not force caching of excluded pages or remove exclusion cookies to improve a score. If a module changes prices or content depending on the visitor, check its compatibility. The LiteSpeed beginner's guide explains the sections and how WooCommerce is handled.

CSS, JavaScript and image optimisation

The current options are grouped into sections such as Page Optimization and Image Optimization. The old Basic View, Advanced View and Manage menus that appeared in earlier versions are no longer a reference for navigation.

Turn on one option at a time and check the layout and features. Combining files does not always benefit HTTP/2 or HTTP/3; deferring JavaScript can affect menus, forms, consent or checkout. Avoid delaying the main image visible when the page opens.

Purge and clean up data

Use the purge options in the LiteSpeed menu or in Toolbox when a change does not show. Start with the affected page. If there is a CDN, check whether it also needs purging.

The Database section has clean-up operations that can delete revisions or other selected data. Read their scope and save a backup: purging the cache and deleting database records are not the same operation.

If it does not improve or something fails

Revert the last setting and repeat the test. If the problem started when you turned on the page cache, disable it temporarily from the plugin and purge the existing responses. Keep the URL, time and configuration for the diagnosis.

To add Redis as an object cache, follow its guide separately. Do not turn on two integrations that try to manage the same object cache file.