Omega Digital's shared and reseller servers run LiteSpeed Web Server. LiteSpeed Cache (LSCWP) is the WordPress plugin that talks to it and can take a typical page load from 1.5s down to under 200ms. This article covers the configuration that delivers most of that benefit.
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
Cache → Cache → Enable Cache: ON. This is the single biggest win. Every uncached visitor now gets HTML served from disk without PHP or MySQL running.
Default TTL of 604800 seconds (7 days) is fine. Don't go lower than a day for public pages.
Step 3: Cache settings worth changing
| Setting | Value | Why |
|---|---|---|
| Cache Logged-in Users | OFF | Each user is different; cache storage explodes |
| Cache Commenters | OFF | Commenters see their pending comments |
| Cache REST API | ON | Gutenberg and headless sites benefit |
| Cache Login Page | ON | Static login HTML, lower brute-force cost |
| Cache favicon.ico | ON | Free win |
| Cache PHP Resources | ON | Caches plugin assets like wp-includes/wlwmanifest.xml |
| Cache Mobile | ON only if you have a separate mobile theme | Otherwise unnecessary split |
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:
- 01. Method: Redis
- 02. Host: 127.0.0.1
- 03. Port: 6379
- 04. Default Object Lifetime: 360
- 05. Persistent Connection: ON
- 06. Save Changes. Status should flip to Connection Test Passed within seconds.
# 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 (the part that breaks things)
Page Optimization is where LSCWP minifies CSS/JS, combines files, and defers loading. It also where most sites break. Turn each setting on one at a time and visually verify the site still works.
- · CSS Minify: ON (safe)
- · CSS Combine: test carefully (sometimes breaks themes using @import)
- · JS Minify: ON (safe)
- · 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: ON (huge bandwidth win)
- · Lazy Load Iframes: ON
- · Remove Query Strings: OFF (breaks plugin versioning)
Step 7: CDN (optional)
CDN → QUIC.cloud. LSCWP integrates with QUIC.cloud CDN for a generous free tier. If you're already using Cloudflare, leave this off. Don't double-CDN.
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 gotchas
- · Enabling all page-optimization settings at once. Something always breaks. Toggle one at a time with visual QA between each.
- · Expecting cache hits when logged in. You disabled logged-in caching (correctly), so test in a private window.
- · Combine CSS breaking animations. Combine is aggressive; fall back to Minify-only if things look off.
- · Forgetting to exclude dynamic pages. Cart, checkout, account pages must be excluded under Cache → Excludes.
Still stuck?
Email [email protected] with the URL and a screenshot of the LSCWP dashboard.