LiteSpeed Cache earns its reputation because it is not just a plugin: on a LiteSpeed or OpenLiteSpeed server it hooks directly into the web server’s own cache engine, bypassing PHP entirely for cached pages. That is meaningfully faster than caches that still serve requests through PHP. The catch is that the plugin ships with dozens of toggles, and a few of them will break your layout, your checkout flow, or your editorial workflow if you flip them without thinking. This guide covers the settings that matter most, in the order you should touch them.
Before You Start
Confirm your environment first. LiteSpeed Cache’s full-page cache only works at full speed when your server is actually running LiteSpeed or OpenLiteSpeed. On Apache or nginx, the plugin falls back to its own PHP-level cache, which is still useful but is a different beast. Check your server software before assuming you have the fast path.
Also make sure you are on PHP 8.1 or higher. PHP 8.3 with OPcache enabled is the current solid default: OPcache compiles your PHP files to bytecode so the server does not re-parse them on every request, which matters even when pages are cached, because admin screens, REST API calls, and cache misses all still run through PHP.
Install the plugin from the WordPress repository, then do not touch anything else yet. Open the plugin’s dashboard and glance at the cache status indicator before you change a single option, so you have a baseline.
General Settings: The Defaults Worth Changing
Navigate to LiteSpeed Cache > Cache > General.
- Enable Cache: Turn this on. It is off by default on some installations. Nothing else matters until this is active.
- Cache Logged-in Users: Leave this off for most sites. Caching authenticated sessions can serve one user’s data to another. The only exception is a membership site where logged-in content is genuinely uniform across a user role, and even then, test exhaustively.
- Cache Commenters: Leave off. Commenters who just posted expect to see their comment immediately. Serving them a cached page that omits it is confusing.
- Cache REST API: This depends on your site. If REST API responses are public and not user-specific, caching them is fine. If your theme or plugins make authenticated REST calls, leave it off or set a short TTL.
- Default Public Cache TTL: The default is often 604800 seconds (one week). That is fine for stable content, but drop it to something like 86400 (one day) if you publish frequently and want cache misses to be predictable rather than surprising.
Page Optimization: Where Sites Break
The optimization tab is where most trouble starts. These settings minify and combine CSS and JavaScript, inline critical CSS, and defer scripts. Each one is a tradeoff between load speed and compatibility.
CSS Settings
- Minify CSS: Generally safe. Enable it, clear cache, and visually check your site. If something looks wrong, disable it and check which stylesheet is the culprit.
- Combine CSS: More risky. Combining files changes load order, which can break styles that depended on cascade specificity from separate files. Enable with care, test on staging first.
- Generate Critical CSS: Useful for improving Largest Contentful Paint. LiteSpeed Cache can generate critical CSS automatically, but the output is not always accurate for complex layouts. Check your LCP score in PageSpeed Insights (target is 2.5 seconds or under) before and after.
JavaScript Settings
- Minify JS: Usually safe. Enable and test.
- Combine JS: Proceed with real caution. JavaScript that depends on execution order will break when combined. WooCommerce checkout, booking plugins, and sliders are common casualties. If you combine JS, test every interactive element on your site.
- Load JS Deferred: A legitimate LCP booster. Deferring non-critical scripts means the browser renders the page first. The risk is scripts that must run before the DOM is ready. Test your forms, popups, and checkout steps.
- Inline jQuery: Leave this off unless you have a specific reason. jQuery is widely cached by browsers from CDNs; inlining it adds to your HTML payload.
The Exclude Lists Are Your Friend
Every optimization option has an exclusion field. When a specific page or script breaks after enabling minification or deferral, add its URI or script handle to the relevant exclusion list rather than disabling the feature globally. This keeps the optimization benefit for the rest of the site.
Object Cache: Adding Redis
Full-page cache handles complete HTML responses. Object cache is different: it stores the results of database queries and computed values so WordPress does not re-run expensive PHP operations on every request that is not a full cache hit. Admin pages, logged-in views, and dynamic pages all benefit.
LiteSpeed Cache supports Redis and Memcached as persistent object cache backends via a drop-in file. To connect Redis, go to LiteSpeed Cache > General > Object Cache, enable object cache, choose Redis as the method, and enter your Redis host, port, and password. The plugin will install the drop-in automatically.
Verify it is working with WP-CLI:
wp cache get alloptions --debug 2>&1 | grep cacheIf the output references Redis, it is connected. If object caching matters to you and you are not sure your host provides Redis, ask before assuming.
Image Optimization
LiteSpeed Cache includes its own image optimization service called QUIC.cloud. It compresses images and can convert them to WebP. The free tier has limits on how many images you can optimize per quota period. Understand those limits before bulk-optimizing a large media library.
More important than compression: enable Lazy Load Images. This defers off-screen images so the browser prioritizes what is above the fold. One important exception: your LCP image, usually a hero image or featured image near the top of the page, should not be lazy loaded. If it is, your LCP score will suffer. LiteSpeed Cache tries to exclude the first image automatically, but verify it with Lighthouse.
Crawler: Keeping Cache Warm
A cold cache means the first visitor after a cache expiry gets a slow uncached response while the server builds the page. LiteSpeed Cache’s built-in crawler visits your URLs on a schedule and pre-warms the cache so real users rarely hit misses.
Enable the crawler under LiteSpeed Cache > Crawler. Set the crawl interval to match your cache TTL. If your TTL is one day, crawl at least once a day. Limit the crawl speed (pages per minute) to avoid the crawler hammering your server during peak traffic hours.
WooCommerce and Dynamic Pages
LiteSpeed Cache ships with WooCommerce-aware defaults that automatically exclude the cart, checkout, and account pages from full-page cache. Do not override these exclusions. Caching the cart page is a classic mistake that results in users seeing each other’s cart contents.
If you have other dynamic pages, such as a membership dashboard or a search results page with live filters, add their URIs to Cache > Excludes > Do Not Cache URIs.
Checking Core Web Vitals After Setup
Once your settings are configured, measure. Use PageSpeed Insights for both lab data and real field data from the Chrome User Experience Report. Aim for LCP at or under 2.5 seconds, Interaction to Next Paint at or under 200 milliseconds, and Cumulative Layout Shift at or under 0.1.
Lighthouse in Chrome DevTools gives you lab data quickly during development, but field data from PageSpeed Insights reflects real users on real connections. Both matter, and they will often disagree. Use field data to confirm whether your lab improvements translated to actual user experience gains.
If CLS is above 0.1 after enabling optimizations, look at whether your lazy-loaded images have explicit width and height attributes. Missing dimensions are the most common cause of layout shift on image-heavy sites.
One Setting to Add in wp-config.php
This is not a LiteSpeed Cache setting, but it complements it. Add this line to your wp-config.php:
define( 'DISALLOW_FILE_EDIT', true );This disables the theme and plugin file editor in the WordPress admin. It is a basic hardening step, and it is worth doing while you have the file open anyway.
Takeaway
LiteSpeed Cache is genuinely excellent software, but it rewards a methodical approach. Enable full-page cache first, verify it works, then layer in object cache, image optimization, and JS and CSS optimization one section at a time. Test after each change. Use the exclusion lists liberally rather than disabling whole features when something breaks. And check your Core Web Vitals scores with real field data, not just lab scores, before calling the configuration done.