How to Configure the LiteSpeed Cache Plugin for WordPress

The LiteSpeed Cache plugin (LSCWP) controls LiteSpeed Web Server's built-in page cache for WordPress. To configure it: confirm your host runs LiteSpeed or OpenLiteSpeed, install the plugin, enable caching, check that carts, checkouts and logged-in pages are excluded, then enable optimisation options one at a time while testing. Finally, verify that pages are served from cache with the x-litespeed-cache: hit response header.

The page-cache feature only works on LiteSpeed servers. On other servers, use your host's caching or another caching plugin. Plugin menus change between versions, so names below may differ slightly.

Step 1: Confirm LiteSpeed support

• Check your hosting plan description or ask your host.
• After installing the plugin, its dashboard reports whether LSCache is available on the server.
• In the browser developer tools, response headers from LiteSpeed servers often include server: LiteSpeed.

Background: LiteSpeed Web Server explained.

Step 2: Install and enable

1. In WordPress, go to Plugins → Add New, search for LiteSpeed Cache, install and activate it.
2. Deactivate other page-caching plugins; two page caches conflict.
3. Go to LiteSpeed Cache → Cache and make sure Enable Cache is on.

Step 3: Review the cache settings

• Cache Logged-in Users: usually off for sites where logged-in users see personal content. Turn on only if you understand private caching.
• Cache Commenters: off unless you have many commenters and test carefully.
• Cache Mobile: turn on only if your theme serves different HTML to mobile devices; most responsive themes do not need it.
• TTL (cache lifetime): defaults are reasonable; LSCache purges pages automatically when content changes.

Step 4: Check exclusions (important for shops)

On WooCommerce, the plugin automatically avoids caching cart, checkout and account pages and handles cart cookies. Confirm under Cache → Excludes and by testing:

• add an item to the cart in one browser and check another private window does not show it;
• log in as a customer and confirm account pages show the right person's data.

Add any other personal or dynamic pages (membership areas, custom forms with per-user content) to the URI exclusions.

Step 5: Purge settings

Under Cache → Purge, keep automatic purging of related pages when a post is updated. Use Toolbox → Purge All after theme changes, plugin updates or menu changes.

Step 6: Enable optimisation options one at a time

The plugin includes many front-end options. Turn them on individually and test the site after each:

1. Image optimisation: request optimised images and WebP versions (uses QUIC.cloud services; check the plugin's terms and quotas).
2. Lazy load images: on, but exclude the main hero image at the top of the page so it loads immediately.
3. CSS and JS minify: usually safe.
4. CSS and JS combine: can break layouts; test carefully.
5. Load JS deferred or delayed: can improve responsiveness but may break sliders, menus or forms; exclude scripts that break.
6. Generate critical CSS / UCSS: powerful but needs testing.

If something breaks, turn the last option off and use Purge All.

Step 7: Object cache (optional)

If your host provides Redis or Memcached, the plugin's Object cache section can connect to it, which helps logged-in users and WooCommerce. Test the connection status before enabling. See Redis object caching explained.

Step 8: Verify the cache works

1. Open a private browser window (not logged in).
2. Load a page twice.
3. In developer tools → Network, select the page request and check the response headers: x-litespeed-cache: hit means the page came from cache; miss means it was generated (normal on the first load).
4. Compare Time to First Byte between the first and second loads.

A safe starting configuration

For a typical business site or small WooCommerce store on a LiteSpeed server, this is a conservative baseline to start from (then tune):

Area	Setting	Starting value
Cache	Enable Cache	On
Cache	Cache Logged-in Users	Off
Cache	Cache REST API	On (default)
Cache	Cache Mobile	Off (unless the theme serves different mobile HTML)
Purge	Purge all on upgrade	On
Image	Lazy load images	On, with the hero image excluded
Page Optimization	CSS Minify	On
Page Optimization	JS Minify	On
Page Optimization	CSS/JS Combine	Off at first; test later
Page Optimization	Load JS Deferred	Off at first; test later
Browser	Browser Cache	On

Change one item at a time from this baseline and measure. Many problems people blame on LiteSpeed Cache come from enabling every optimisation option at once.

Crawler and cache warm-up

The plugin can include a crawler that visits pages to pre-build the cache after it is purged, so the first real visitor gets a cached page. It uses server resources, so check whether your host allows it and keep its speed settings modest on shared hosting; see hosting resource limits explained.

Troubleshooting

Problem	Fix
Header always shows miss	Logged-in session, query strings, or a plugin setting no-cache cookies; test in a private window
No LiteSpeed headers at all	Server is not LiteSpeed, or a proxy/CDN strips headers
Layout broken after optimisation	Disable the last CSS/JS option, purge, re-test
Cart shows wrong items	Check WooCommerce exclusions and that no other cache plugin is active

Frequently Asked Questions

Can I use LiteSpeed Cache with Cloudflare?

Yes. Cloudflare caches static files at the edge; LSCache caches pages on the server. Avoid enabling HTML caching in both without careful rules.

Does LiteSpeed Cache replace image optimisation plugins?

It can, through its image optimisation feature. Using two image optimisers at once wastes resources.

Related reading

See how to speed up a WordPress website and website caching explained. Compare ServerNeed WordPress hosting.

For the wider choice of WordPress hosting, see WordPress hosting: what it is and how to choose.

Sources

• LiteSpeed Cache for WordPress documentation
• WordPress.org: LiteSpeed Cache plugin