How to Configure LiteSpeed Cache in WordPress
Updated today
Enable LiteSpeed Cache page caching and check that a public page is served from the cache. This is a good first step toward improving WordPress response times. CSS, JavaScript, and CDN settings are optional.
Before you start
You need WordPress administrator access. To use page caching, you need a LiteSpeed server with LSCache enabled or the QUIC.cloud CDN. If your site is hosted with us and the plugin says server caching is unavailable, you can ask us to check your plan configuration.
If you already use another page caching plugin, disable its page caching feature before enabling LiteSpeed Cache. Use only one plugin to manage page caching.
Enable page caching
In the WordPress dashboard, look for LiteSpeed Cache in the Plugins section. Install and activate it if it isn't active yet. The plugin author is LiteSpeed Technologies.
Go to LiteSpeed Cache → Cache and open the first tab, also called Cache.
Enable the main cache option and save your changes. For the first test, leave your other settings as they are.
If your site is a WooCommerce store, LiteSpeed excludes the cart, checkout, and My Account pages by default. After enabling the cache, test all three steps as a customer. If you use custom checkout pages or rules that cache HTML on a CDN, check their exclusions too.
Check that it works
Test your homepage or a public post in an incognito window without signing in. This lets you see what a new visitor receives.
Right-click and select Inspect to open your browser's developer tools. Go to Network (Network) and reload the page.
Select the HTML document request for that page. In the response headers, look for
x-litespeed-cache.If you see
miss, reload the same URL and check again.hitconfirms that LiteSpeed served a cached copy. If you use QUIC.cloud, you can also checkx-qc-cache.
If miss still appears or the header is missing, try another public page without URL parameters. An x-litespeed-cache-control value of no-cache means LiteSpeed has excluded that page from the cache. If you still don't get a hit on another public page and your site is hosted with us, send us the URL you tested and a screenshot of the headers.
Test advanced settings one at a time
Once you've confirmed that the cache works, choose a setting based on the problem you want to solve. If you have a staging site, test CSS and JavaScript changes there first.
CSS and JavaScript. If you want to test minification or delay scripts, change one option at a time. Then check the mobile menu, forms, and, if you have a store, the cart and checkout page.
Object cache. Redis can help reuse data that WordPress queries repeatedly. Enable this feature only if your plan includes Redis, you have the connection details, and the plugin's connection test succeeds. If another plugin already manages the object cache, use only one integration.
Cloudflare. You can continue using it with LiteSpeed. Linking its API to the plugin is optional and lets you manage Cloudflare purges from WordPress.
To compare the results, measure the same page before and after under similar conditions. How to Measure Performance with Lighthouse.
What to do if a change breaks the design or a feature
If the problem started after enabling a CSS or JavaScript setting, revert that setting first.
Go back to LiteSpeed Cache → Page Optimization, disable the last setting you changed, and save.
In LiteSpeed Cache → Toolbox, open the purge tab and purge the LiteSpeed cache and the CSS/JS cache. If a CDN has a copy of the affected page, purge it there too.
Test the page again in an incognito window.
If the cache is returning hit and the site is still slow, FastWeb can review the theme, plugins, and database to find what's causing the delay. FastWeb WordPress Optimization Service.
If you've already set up page caching and need to control which scripts or styles load, see the Perfmatters review on FastWeb. Before combining tools, avoid enabling the same CSS or JavaScript optimization in both.