Configure LiteSpeed Cache for WordPress

Omega Digital web hosting uses LiteSpeed Web Server. The LiteSpeed Cache plugin connects WordPress to its cache. This guide covers setup and verification.

Step 1: Install the plugin

# Via WP-CLI
wp plugin install litespeed-cache --activate

# Or: Plugins → Add New → search 'LiteSpeed Cache' → Install → Activate

Step 2: Enable the page cache

Under Cache → Cache, turn on Enable Cache. Verify cache behavior before changing optimization settings.

Choose a cache lifetime that fits how often your public pages change, and verify that updates clear the relevant cached pages.

Step 3: Cache settings worth changing

Step 4: Object cache with Redis or Memcached

Cache → Object tab. WordPress core hits MySQL constantly for options, user meta, and term queries. Object caching keeps those in memory. On Omega Digital, use Redis:

1. Method: Redis
2. Host: 127.0.0.1
3. Port: 6379
4. Default Object Lifetime: 360
5. Persistent Connection: ON
6. Save the settings and check the connection test result.

# Verify from command line
wp litespeed-option get redis_host
# Expected: 127.0.0.1

wp litespeed-purge objects
wp cache get doing_it_wrong_trigger
# Should return a value if object cache is working

Step 5: Image optimization

Image → Image Optimization Settings. Enable the LiteSpeed Cloud optimization (free quota). Your images get compressed and served as WebP to supporting browsers.

• Auto Request Cron: ON
• Auto Pull Cron: ON
• Optimize Original Images: ON
• Remove Original Backups: only after verifying results for a week
• Preserve EXIF/XMP data: ON (for photography sites), OFF otherwise (smaller files)
• WebP Replacement: ON

Step 6: Page optimization

Page Optimization controls CSS and JavaScript minification, file combining and deferred loading. Change one setting at a time, then test navigation, forms and checkout.

• CSS Minify: test after enabling
• CSS Combine: test carefully (sometimes breaks themes using @import)
• JS Minify: test after enabling
• JS Combine: test carefully (often breaks sliders and custom jQuery)
• JS Defer: ON (move to body bottom). Preview any page with embedded forms.
• Lazy Load Images: test image loading after enabling
• Lazy Load Iframes: ON
• Remove Query Strings: OFF (breaks plugin versioning)

Step 7: CDN (optional)

The CDN section provides QUIC.cloud integration. Review your existing CDN configuration before enabling another service.

Verify it's working

# Fetch a page and check headers
curl -sI https://yourdomain.com/ | grep -iE 'x-litespeed|cache-control|x-cache'

# You should see:
# x-litespeed-cache: hit     <-- cached!
# (Or on first request: x-litespeed-cache: miss, then hit on second)

# If you see:
# x-litespeed-cache: no-cache,cookie
# then LSCWP is seeing a logged-in cookie (or a test-cookie). Open in a private tab.

When to purge

LSCWP auto-purges when you publish or update posts. You need to purge manually only when:

• You update a theme file directly
• You change LSCWP settings
• You see stale content in testing

# Purge everything via WP-CLI
wp litespeed-purge all

# Purge just the homepage
wp litespeed-purge url https://yourdomain.com/

Common issues

• Changing several optimization settings at once makes failures harder to trace. Test after each change.
• Expecting cache hits when logged in. You disabled logged-in caching (correctly), so test in a private window.
• CSS combining errors. Disable CSS Combine and test again if styles or animations stop working.
• Forgetting to exclude dynamic pages. Cart, checkout, account pages must be excluded under Cache → Excludes.

Contact support

Email [email protected] with the URL and a screenshot of the LSCWP dashboard.