LiteSpeed Cache Complete Setup for WordPress

iWebVault servers run LiteSpeed Web Server, which works with the LiteSpeed Cache (LSCache) WordPress plugin to deliver dramatic performance improvements — often 5x to 10x faster load times. The plugin is free, the server-side caching is included with your hosting, and setup takes about 15 minutes. This guide walks through what to enable, what to leave alone, and how to verify everything’s working.

Why LiteSpeed Cache is special

Most caching plugins (WP Super Cache, W3 Total Cache) run in PHP — they intercept WordPress’s output and save the result to disk, then serve cached versions on subsequent requests. LiteSpeed Cache integrates with the LiteSpeed web server directly: cached pages are served BEFORE PHP even starts. That’s faster than any PHP-based cache can be.

Practical implication: on iWebVault hosting, LSCache is the right caching choice. Don’t install other page-caching plugins alongside — they’ll conflict.

Installation

1. WordPress Admin → Plugins → Add New → search “LiteSpeed Cache”.
2. Install, activate.
3. New menu item “LiteSpeed Cache” appears in admin sidebar.

Out of the box, basic page caching is already active. You’ll see immediate improvement just from installation.

Settings to enable

Cache → Cache tab

• Enable Cache: ON.
• Cache Logged-in Users: OFF (cached pages would mix between users — bad).
• Cache Commenters: OFF (similar reason).
• Cache REST API: ON (helps API calls).
• Cache Login Page: ON.
• Cache favicon.ico: ON.
• Cache PHP Resources: ON.
• Cache Mobile: OFF unless you have a separate mobile theme.

Cache → TTL tab

TTL = Time To Live, how long pages stay cached before regenerating.

• Default Public Cache TTL: 604800 (one week — sites that change rarely).
• Default Private Cache TTL: 1800 (30 minutes).
• Default Front Page TTL: 604800.
• Default Feed TTL: 604800.
• Default REST TTL: 604800.

Lower TTLs (1 hour, 1 day) if your site updates frequently. The cache also automatically purges when posts/pages/products are edited — long TTLs aren’t a problem for content freshness if your editors save through WP admin.

Cache → Purge tab

• Purge All On Upgrade: ON.
• Auto Purge Rules For Publish/Update: default settings work for most sites.
• Serve Stale: ON (during cache regeneration, serve previous cache rather than uncached pages — better UX).

Cache → Browser tab

• Browser Cache: ON. Tells visitor browsers to cache static assets locally.
• Browser Cache TTL: 31557600 (one year for static files).

Page Optimization → CSS Settings

• CSS Minify: ON. Removes whitespace, smaller files.
• CSS Combine: Try ON, but test thoroughly — can break some themes. Toggle OFF if site looks wrong.
• Generate UCSS: Generates Used CSS only (advanced). Try if site loads slowly even with caching.
• Inline CSS Async Lib: ON.
• Font Display Optimization: Swap (better web vitals).

Page Optimization → JS Settings

• JS Minify: ON.
• JS Combine: Try ON; test thoroughly. Some plugins break with combined JS.
• JS Defer: “Delayed” — biggest speed gain but most likely to break things. Start with “After DOM Ready”, test, only go to “Delayed” if everything works.

Page Optimization → Media Settings

• Image Lazy Load: ON. Images load as user scrolls — fewer requests, faster initial load.
• Iframe Lazy Load: ON.
• Add Missing Sizes: ON. Helps Core Web Vitals (CLS metric).
• Inline Lazy Load Library: ON.

Page Optimization → Image Optimization

• Auto Request Cron: ON. Automatically sends new images to QUIC.cloud for optimization.
• Optimize Original Images: ON.
• Create WebP Versions: ON. Modern image format, much smaller.
• Image WebP Replacement: ON. Serve WebP to browsers that support it.

QUIC.cloud is a free service from LiteSpeed Technologies that processes images. You’ll need to register for a free QUIC.cloud account (plugin guides you through it).

QUIC.cloud — CDN and image services

LSCache integrates with QUIC.cloud’s free tier for:

• Image optimization (compression, WebP generation).
• CDN delivery (global edge servers).
• Critical CSS generation.
• Page Optimization Service (UCSS generation).

General → QUIC.cloud Services → enable the free domain. Generates an API key automatically. Free tier includes generous monthly quotas — enough for most small/medium sites.

Settings to leave alone (until you know what they do)

• Object Cache (Redis/Memcached). Powerful but requires server-side Redis/Memcached setup. Skip unless on VPS with Redis configured.
• ESI (Edge Side Includes). Advanced fragment caching. Useful for specific dynamic sections but easy to misconfigure.
• Crawler. Automatically warms cache by crawling your site. Useful but adds server load. Enable later once stable.
• VPI (Viewport Images). Lazy-load below-fold images smarter — complex setup, marginal benefit on small sites.

Verifying it’s working

Check X-LiteSpeed-Cache response header

Browser DevTools → Network tab → load your site → click a page request → response headers. Look for:

• X-LiteSpeed-Cache: hit — page served from cache (good!).
• X-LiteSpeed-Cache: miss — page wasn’t cached, regenerated.
• X-LiteSpeed-Cache-Control: no-cache — caching disabled for this request (admin, logged-in, etc.).

After visiting a page twice (once to populate cache, once to read it), second visit should show “hit”.

Speed tests

• PageSpeed Insights (Google). Tests Core Web Vitals.
• GTmetrix. Detailed performance breakdown.
• WebPageTest. Most comprehensive.

Run a baseline test BEFORE enabling caching, then after — the difference is usually dramatic. Time-to-first-byte should drop from hundreds of ms to tens of ms.

Troubleshooting LSCache

“My site looks broken after enabling cache.” Almost always JS Combine or CSS Combine. Turn those OFF — page caching alone still gives most of the benefit.

“Changes I make in admin don’t appear on the public site.” Cache not purging on updates. LiteSpeed Cache menu → top bar → Purge All. Verify “Auto Purge Rules” are configured.

“Logged-in users see other users’ cached content.” Should not happen if “Cache Logged-in Users” is OFF. Double-check the setting.

“WooCommerce cart/checkout shows wrong data.” LSCache has WooCommerce integration — install it and configure the WooCommerce-specific cache exclusions. Cart, checkout, account pages should never cache.

“Page Speed score didn’t improve.” Caching helps server-side time-to-first-byte enormously, but Core Web Vitals depend on more — image sizes, render-blocking JS, layout shift. Enable lazy loading, image optimization, and consider Page Optimization tab settings.

“How do I disable cache temporarily for development?” LSCache menu → Cache → Cache tab → toggle “Enable Cache” off. Or add ?nocache=1 to URLs while testing.

When to manually purge

• After bulk content updates (CSV imports, mass post updates).
• After theme changes via FTP (not through Customizer — that auto-purges).
• After installing a plugin that changes front-end output.
• If you suspect cache is showing stale content despite auto-purge.

Top admin bar → LiteSpeed Cache → Purge All. Or LSCache menu → Toolbox → Purge tab → various purge options.

What’s next

• WordPress installation: WP install guide.
• If you also use WooCommerce: WooCommerce hosting.
• Image-heavy site optimization: enable image optimization in LSCache, audit image sizes.

LSCache is the single biggest performance lever on iWebVault hosting. Enable page caching with default settings as a baseline, then progressively turn on optimizations (lazy loading, image optimization, minification) testing as you go. Don’t turn on JS Combine and Delay without thorough testing — that’s where most breakage happens.