Most caching plugins sit inside WordPress and rebuild your pages through PHP. LiteSpeed Cache works differently — when your server runs LiteSpeed, it caches at the web server level, so a cached page can be served without PHP or the database ever getting involved. Get the LiteSpeed Cache settings right and your site answers in tens of milliseconds. Get them wrong and you get a broken layout on mobile. This guide walks you through the configuration I recommend, step by step.
Why LiteSpeed Cache Plays a Different Game
Here’s the core idea you need to understand before touching any setting.
A plugin like WP Rocket builds a static HTML file and serves it via PHP. LiteSpeed Cache hands the cache to the LiteSpeed web server itself. On a cache hit, the response goes straight from server memory to the visitor’s browser — PHP never boots, no database queries run. In practice that difference shows up as noticeably lower time to first byte on a LiteSpeed host.
One important caveat: the plugin only shines on LiteSpeed or OpenLiteSpeed servers. On Apache or Nginx, the server-level caching features lose most of their punch, though the image and CSS/JS optimization tools still work. Which brings us to the first step.
First: Confirm Your Server Actually Runs LiteSpeed
After installing the plugin from Plugins → Add New and activating it, look at the LiteSpeed Cache dashboard widget. If you see the message that your site is running on LiteSpeed, you’re good. You can also confirm by checking your site’s response headers in your browser’s developer tools — LiteSpeed servers announce themselves there.
Not sure? Ask your host. Popular shared hosts that run LiteSpeed include Hostinger, ChemiCloud, ScalaHosting, GreenGeeks, and WPX. If your host runs something else, skip straight to the LiteSpeed Cache vs WP Rocket section at the bottom.
Step 1: Start With the Advanced Preset
LiteSpeed Cache ships with presets under LiteSpeed Cache → Presets: Essentials, Basic, Advanced (Recommended), Aggressive, and Extreme. Don’t start with a blank slate — apply Advanced (Recommended). It enables a sensible baseline: Guest Mode, JS/CSS/HTML minification, JS defer, font display optimization, and more.
Tip: before applying anything, use the Import/Export tab on the Presets page to export your current settings. That backup is your undo button if an experiment goes wrong.
Aggressive and Extreme presets add CSS/JS combining and async CSS with Critical CSS. They’re powerful but genuinely likely to break layouts on complex themes — treat them as “test in staging first” options, not defaults.
Step 2: Tune the Core Cache Settings
Go to LiteSpeed Cache → Cache. These are the settings that matter most:
- Enable Cache: ON. This is the whole point of the plugin.
- Cache Logged-in Users: OFF. Logged-in visitors (admins, customers, members) see personalized content. Caching their views creates weird bugs. Leave this off unless you fully understand cache vary rules.
- Cache Commenters: OFF. A visitor who just submitted a comment awaiting moderation should see their “awaiting moderation” message, not a stale cached page.
- Cache REST API: ON. REST responses benefit from caching, especially if you use the block editor heavily.
- Cache Mobile: OFF — if your theme is responsive. A responsive theme serves the same HTML to every device, so a separate mobile cache just wastes disk. Only turn this on if your theme serves different HTML to phones.
- Default Public Cache TTL: 604800 (7 days). A long TTL sounds scary, but the plugin purges intelligently when content changes, so a long TTL just maximizes your cache hit rate. For related reading on why the first byte matters, see my guide on reducing server response time.
Under Purge, turn Purge All on Upgrade ON so WordPress, theme, and plugin updates flush stale cached pages, and make sure the auto-purge rules for publish/update are enabled — this is what refreshes your homepage, category archives, and related pages the moment you publish a post.
Step 3: Connect QUIC.cloud
Under LiteSpeed Cache → General → Online Services, connect your site to QUIC.cloud by requesting a domain key. This unlocks three things you can’t get any other way:
- Image optimization (img_optm) — cloud-based compression and WebP conversion.
- Critical CSS generation (ccss) — the above-the-fold CSS that makes async CSS loading safe.
- Unique CSS (ucss) — removing unused CSS per page.
QUIC.cloud also powers Guest Optimization, which serves an optimized, cache-warmed version of your pages to first-time visitors — one of the biggest wins this plugin offers. One honest note: the free tier has quotas, and Critical CSS generation is one of the limited resources, so don’t regenerate it repeatedly. Run it once per design change and move on.
Step 4: Optimize CSS and JS Without Breaking Your Theme
This is where people break their sites, so slow down. Under LiteSpeed Cache → Page Optimization:
- CSS/JS/HTML Minify: ON. Safe on almost every site.
- JS Defer: ON. Moves JavaScript execution after the page renders, which helps Interaction to Next Paint.
- Load CSS Asynchronously: ON — but only after you’ve generated Critical CSS via QUIC.cloud (Step 3). Without Critical CSS, async loading causes a flash of unstyled content.
- Combine CSS/JS: Test carefully. Combining works fine on simple sites but can break themes and page builders that generate dynamic CSS — Elementor sites are the classic example. If your layout breaks after enabling this, this setting is your first suspect.
- Lazy Load Images/Iframes: ON. I covered the full details in my lazy loading guide — same principles apply here.
The rule for this entire tab: change one setting, save, purge all cache, and check your site in an incognito window. Never stack five changes and then try to figure out which one broke the hero section.
Step 5: Set Up Image Optimization
Under LiteSpeed Cache → Image Optimization, enable automatic image optimization. The plugin sends new uploads to QUIC.cloud for compression and WebP conversion automatically.
Two practical notes: enable WebP Replacement so browsers that support WebP get the smaller files, and make sure lazy loading (Step 4) is on so below-the-fold images don’t compete with your hero image for bandwidth. Your Largest Contentful Paint score will thank you.
Step 6: Database Cleanup and the Cache Crawler
Two “set and forget” features worth enabling:
- Database Optimizer (under LiteSpeed Cache → Database): schedule a weekly cleanup of post revisions, expired transients, spam comments, and other bloat. I wrote a full walkthrough of WordPress database cleanup if you want to understand what each option removes.
- Crawler (under LiteSpeed Cache → Crawler): pre-warms your cache so visitors never trigger a slow, uncached first load. Run it after publishing or updating content, especially on low-traffic sites where pages would otherwise expire from cache between visits.
If you run anything dynamic that can’t be page-cached — a WooCommerce cart, a membership dashboard, wp-admin — consider the Object Cache with Redis. It moves WordPress’s repeated database lookups into memory, which makes even uncacheable pages noticeably faster. Your host needs to provide Redis or Memcached for this.
LiteSpeed Cache vs WP Rocket: Which Should You Pick?
The honest answer depends on your server, not the feature list.
Choose LiteSpeed Cache if your host runs LiteSpeed. It’s free, and its server-level caching genuinely outperforms PHP-layer plugins on that stack. If you’re already on Hostinger or a similar host, there’s no reason to pay for what your server does better for free.
Choose WP Rocket if your host runs Apache or Nginx, you manage client sites across many different hosts, or you want the setup to just work in fifteen minutes. It applies most performance best practices on activation, has excellent compatibility with page builders, and at $59/year for a single site, the support alone is worth it for many site owners.
There’s also FlyingPress, a newer challenger that scores well on Core Web Vitals. But for most people, the decision tree above is enough: LiteSpeed host → LiteSpeed Cache, anything else → WP Rocket.
When Something Breaks: The 3-Minute Recovery
Sooner or later, an optimization setting will break something. Here’s the drill:
- Purge all cache first. Stale cache is the number one cause of phantom problems. Debug nothing until you’ve purged.
- Undo the last change. If your layout broke right after enabling JS combine or async CSS, disable that one setting and purge again.
- Exclude the offender. Most Page Optimization tabs have exclusion boxes. Find the CSS or JS file causing trouble (your browser console will point at it) and exclude it from the aggressive setting.
Keep your exported settings backup from Step 1. Worst case, reimport it and you’re back to a known-good state in seconds.
The Quick Checklist
- ✅ Applied the Advanced (Recommended) preset, exported a settings backup
- ✅ Core cache tuned: logged-in users off, mobile off (responsive theme), REST API on, 7-day TTL
- ✅ QUIC.cloud connected: domain key, image optimization, Critical CSS generated
- ✅ Page optimization tested one setting at a time in an incognito window
- ✅ WebP conversion on, lazy load on
- ✅ Weekly database cleanup scheduled, crawler pre-warming the cache
Set up this way, LiteSpeed Cache handles page caching, image optimization, CSS/JS processing, and database cleanup from a single free plugin — which is exactly why it’s the default I reach for on LiteSpeed hosting.
Want this configured on your own site without the trial and error? I optimize WordPress sites for speed and Core Web Vitals every day — get in touch and I’ll take it from here.