LiteSpeed Cache Settings for WordPress: A Step-by-Step Speed Guide

On a WordPress site running on a LiteSpeed server, the biggest speed gain comes from one plugin: LiteSpeed Cache (LSCache). The plugin is free, but its defaults need tuning for your site. This guide is written for the LiteSpeed + Redis stack on Fiberserver WordPress hosting; if you want the background first, read what LiteSpeed is.

Before you start

• Remove any other caching plugin (WP Super Cache, W3 Total Cache, WP Rocket); two caches break each other.
• Install and activate LiteSpeed Cache from Plugins > Add New. A LiteSpeed Cache entry appears in the left menu.
• Measure first: record your PageSpeed Insights or GTmetrix result before changing anything.

1. The Cache tab

• Enable Cache: ON. Leave Cache Logged-in Users OFF unless you run a membership site.
• Cache Mobile: turn on only if you serve a separate mobile theme or content. Keep it off for responsive themes; if you enable it you must fill in the Mobile User Agents list.
• TTL: the default public TTL of 604800 seconds (one week) suits most sites. For a frequently updated homepage set Front Page TTL to 3600–7200.
• Purge: keep "Purge All On Upgrade" on; purging the homepage, category and tag pages when a post is published comes with the default rules.
• Excludes: with WooCommerce the cart, checkout and my-account pages are excluded automatically; add the URI of any custom form or member page here. utm_* query strings are ignored by default, which is correct.
• ESI: for small personalised blocks such as the cart icon or "Hello, Ali", enable ESI and keep only that block private; otherwise leave it off.

2. Object cache: Redis

The page cache works for visitors; the object cache serves database queries from memory for the admin area, WooCommerce and logged-in users. Redis is ready on Fiberserver WordPress plans:

1. In Cache > Object set Object Cache: ON, Method: Redis.
2. Take the host and port from the LiteSpeed Web Cache Manager in cPanel (usually 127.0.0.1 and 6379, or a unix socket). After saving, the status line should read "Connection Test: Passed".
3. If several sites share one account, give each a different Redis Database ID, otherwise their caches mix.

3. Browser cache

Cache > Browser: Browser Cache: ON, TTL 31557600 (one year). Static files stay in the visitor's browser; when a file changes LiteSpeed refreshes it with a version parameter.

4. Page Optimization

Every option here can break the site; enable them one at a time and check the site in a private window after each step.

• CSS Minify: ON. Start with CSS Combine OFF; with HTTP/2 and HTTP/3 the gain from combining is small and the breakage risk is high.
• JS Minify: ON. JS Defer: Deferred. If a slider or form breaks, add that file to "JS Deferred / Delayed Excludes".
• Load CSS Asynchronously: critical CSS generation needs a QUIC.cloud account; if you enable it, also enable Generate Critical CSS to avoid a flash of unstyled content. Leave it off if unsure.
• Media: Lazy Load Images ON, but add the logo and hero image above the fold to "Lazy Load Image Excludes", otherwise LCP gets worse. Lazy Load Iframes ON.
• Localization: Localize Resources can serve Google Fonts and Gravatar locally; unnecessary if your theme already hosts its fonts.

5. Image optimisation and WebP

In the Image Optimization tab click Request Domain Key for a free QUIC.cloud key. Then set Image WebP Replacement: ON and Auto Request Cron: ON. Existing images are compressed in the background and served as WebP when the browser supports it. Large libraries take a few hours for the first pass; if the free monthly quota runs out, it continues next month.

6. Verify that it works

1. Open the site twice in a private window. In the browser's developer tools (Network tab) look at the response headers of the first document: you should see x-litespeed-cache: hit. miss is normal on the first request; a permanent miss means the page is excluded.
2. As a logged-in user the same page should carry no x-litespeed-cache header, which means personalised content is not cached.
3. Compare the PageSpeed Insights result with your earlier measurement. On a well-tuned LiteSpeed site the server response time (TTFB) drops below 200 ms.

Common mistakes

• Caching the cache again with Cloudflare "Cache Everything": purge rules collide and stale content shows. Cache only static files in Cloudflare.
• Caching the WooCommerce mini-cart without ESI: another customer's cart appears.
• Forgetting to purge after a change: use "Purge All" from the LiteSpeed menu in the admin bar.

If the settings break your site, LiteSpeed Cache > Toolbox > Debug has "Reset All Settings". If you get stuck, open a support ticket with a screenshot; LiteSpeed configuration is covered by our hosting support.