LiteSpeed Plugin Settings: Fast WordPress with Redis

LiteSpeed Plugin Settings: The Best Configuration for Speed & SEO

By Thomas McKee | August 10, 2025

Meta Title: LiteSpeed Plugin Settings: Fast WordPress with Redis

Meta Description: Definitive LiteSpeed Cache settings for WordPress. Use Redis at /var/run/redis/redis.sock, boost Core Web Vitals & SEO with a copy-paste guide.

TL;DR:

Enable server-level LSCache, then configure LiteSpeed Cache for page cache + Redis object cache via /var/run/redis/redis.sock.
Turn on Browser Cache, keep Page Optimization conservative first (then enable CSS/JS minify, Defer/Delay in phases).
Verify success with headers (x-litespeed-cache / x-redis-cache) and Lighthouse.
Need a tuned stack? See our Professional WordPress Hosting.

Keyword Strategy (Local SEO + E-E-A-T)

Primary: litespeed plugin settings, litespeed cache settings, best litespeed settings, litespeed redis socket

Secondary: wordpress speed optimization, http/3 quic wordpress, brotli compression, redis object cache

Local (Springfield, MO): wordpress performance springfield mo, litespeed cache expert springfield, website speed optimization springfield

We build topical authority with step-by-step configuration for every relevant page in the plugin, include copy/paste commands, and cite official docs to strengthen E-E-A-T.

Prerequisites & Quick Verifications

Server + Plugin

LiteSpeed Web Server (LSWS) active on your host.
WordPress + LiteSpeed Cache plugin installed.
Redis installed, enabled, and listening on a UNIX socket.

Copy/Paste Checks

# Redis via UNIX socket
redis-cli -s /var/run/redis/redis.sock PING

# Two-hit test: check cache headers (run twice)
curl -I https://example.com | egrep -i 'x-(litespeed|redis)-cache|content-encoding'
curl -I https://example.com | egrep -i 'x-(litespeed|redis)-cache|content-encoding'

On a second request, expect x-litespeed-cache: hit and (once object cache is active) x-redis-cache: hit.

General (Plugin Dashboard)

Cache (Core Page Caching)

Cache → Cache

Enable Cache: ON
Cache Mobile: ON
Cache Logged-in Users: OFF (ON only for private communities)
Cache Commenters: OFF
Cache REST API: ON
Cache Login Page: ON

Cache → TTL

Default Public Cache TTL: 604800 (7d)
Front Page TTL: 604800
Feeds TTL: 3600
REST TTL: 3600

Cache → Purge

Purge All On Upgrade: ON
Auto Purge Rules: All relevant (home, front page, post type archives, taxonomy pages)
Serve Stale: ON (serve cached page while regenerating)

Cache → ESI (Edge Side Includes)

Enable ESI: ON
Admin Bar: Private
Comment Form: Private
WooCommerce Cart/Fragments: ESI ON

Cache → Browser

Browser Cache: ON
TTL: 31557600 (1 year) for CSS/JS/fonts/images

Cache → Excludes

Do Not Cache URIs: /wp-admin/*, /cart/*, /checkout/*, /my-account/*
Do Not Cache Cookies: wordpress_logged_in_, woocommerce_items_in_cart, wp_woocommerce_session_

Pro Tip: Offer a tuned base at the hosting layer. Our Professional WordPress Hosting ships with LSCache best practices for faster TTFB.

Object Cache (Redis)

Use the local UNIX socket for lowest latency:

Cache → Object

Object Cache: ON
Method: Redis
Host: /var/run/redis/redis.sock
Port: (leave blank)
Persistent Connection: ON
Database ID: choose a unique number per site (0–15)

Quick Tests

# Verify Redis socket is up
redis-cli -s /var/run/redis/redis.sock PING

# Optional: inspect keys (namespaces vary by site)
redis-cli -s /var/run/redis/redis.sock KEYS '*litespeed*' | head -n 20

Heads-up: If the toggle won’t stay ON, remove a conflicting drop-in at wp-content/object-cache.php, ensure the site user is in the redis group, and include /var/run/redis/ in open_basedir if enforced.

Page Optimization (CSS / JS / HTML / Media)

CSS

CSS Minify: ON (test)
CSS Combine: OFF (HTTP/2/3 reduces need)
Generate UCSS: OFF initially (enable later with care)
Inline UCSS: OFF initially

JS

JS Minify: ON (test)
JS Combine: OFF
Load JS Deferred: ON (exclude critical scripts if needed)
Delay JS: OFF initially → ON later; exclude nav/slider scripts

HTML

HTML Minify: ON
DNS Prefetch: Add CDN/3rd-party origins used site-wide

Media

Lazy Load Images: ON
Lazy Load Iframes: ON
Add Missing Sizes: ON
Instant Click: Optional ON

Pro Tip: Toggle one setting at a time and re-run Lighthouse. If CLS or INP regresses, roll back and add exclusions.

Image Optimization (WebP, AVIF, LQIP)

Optimization: Lossless or Conservative Lossy
Create WebP: ON (most browsers)
Create AVIF: Optional ON (smaller but slower to generate)
Preserve Originals: ON
Auto Request Cron: ON
Remove Original Backups: OFF

CDN (QUIC.cloud / Cloudflare)

QUIC.cloud: Deep integration with LSCache (edge cache, image services).
Cloudflare: Excellent global CDN; avoid double URL rewrites.
Compression: With LiteSpeed + Brotli, you’re already serving compressed assets from origin.

Hosting matters: Our Professional Plan is tuned for HTTP/3, Brotli, and LSCache.

Database Optimizer

Post Revisions: Clean monthly
Auto Drafts / Trashed Posts: Clean weekly
Transients: Clean weekly (active ones remain hot in object cache)

# WP-CLI quick DB clean (safe subset)
wp transient delete --all
wp comment delete $(wp comment list --status=trash --format=ids) --force 2>/dev/null || true

Crawler

Leave OFF unless you’ve profiled server headroom. Crawlers warm cache but consume CPU/RAM. If needed, limit concurrency and schedule off-peak.

Toolbox & Debug (WP-CLI, headers)

Handy Commands

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

# Inspect LSCache settings (serialized)
wp option get litespeed-conf | sed 's/;/;\n/g' | less

# Verify HTTP/3 and compression
curl -I --http3 https://example.com
curl -I --compressed https://example.com | egrep -i 'content-encoding|cache-control'

In Springfield, MO and want expert help? See our SEO services or Get in Touch.

Security & Stability Tips

Test Page Optimization on staging first; JS timing is the most common issue.
For Redis socket: ensure each cPanel user that needs it is a member of the redis group and open_basedir includes /var/run/redis.
Keep PHP/OPcache tuned (opcache.memory_consumption=256–512, revalidate_freq=0).

Background on Redis: Redis (Wikipedia).

Pro Tips / Tips & Tricks

Warm critical paths: Home, top categories, top posts, cart/checkout; then run Lighthouse.
Delay JS incrementally: Turn ON, test, then exclude any script that controls navigation or hero sliders.
Guest Mode / Guest Optimization: Consider for anonymous traffic; validate personalization still works.
Measure INP, not just LCP: Interactivity matters—optimize long tasks and third-party scripts.
Edge caching: If your audience is worldwide, consider QUIC.cloud for edge cache + images.

Key Takeaways

Start with caching + Redis socket + browser cache; layer Page Optimization carefully.
Favor stability over aggressive combine/minify—HTTP/2/3 reduces the need to combine.
Use WebP/AVIF and a CDN for global speed; verify asset rewrites and headers after changes.