LiteSpeed Cache Advanced Configuration: ESI, CDN, Object Cache & More

If you followed my beginner LiteSpeed Cache setup guide, your site is already faster — caching’s on, images lazy-load, code’s minified. That’s most of the benefit for most people, and there’s no shame in stopping there.

But if you’re reading this, you want the rest. This guide covers the settings I told beginners to skip: Object Cache, QUIC.cloud CDN integration, database optimization, the built-in crawler, and ESI — the features that make LiteSpeed Cache genuinely stand apart from every other caching plugin, once you understand how to use them.

This is more technical territory, so read the “before you start” section first — a couple of these settings can break things if flipped carelessly.

Key Takeaways

• Back up your site before touching any setting in this guide — these are more powerful, and more capable of causing visible issues, than the beginner basics.
• Object Cache requires Redis or Memcached support from your host — check before you try to enable it.
• QUIC.cloud is LiteSpeed’s own CDN and optimization service, built by the same company, with a genuinely useful free tier.
• ESI is the single most powerful — and most complex — feature in this plugin. Save it for last.

Before You Start

A few ground rules before diving into any of this:

• Back up your site first. I mean it — see my full backup guide if you haven’t already. Every setting below is safe when configured correctly, but “correctly” is doing a lot of work in that sentence.
• Change one setting at a time, and check your site after each change. If something breaks, you’ll know exactly what caused it.
• Test on a staging site if you have one. Several backup plugins (Duplicator, BlogVault) include staging environments — worth using here if available.
• Confirm you’re actually on LiteSpeed hosting. Everything in this guide assumes the LiteSpeed Web Server or OpenLiteSpeed foundation covered in Part 1 — without it, several of these features won’t function at all.

1. Object Cache (Redis or Memcached)

Object Cache stores the results of repeated, expensive database queries in your server’s memory, so WordPress can reuse them instantly instead of re-querying your database every time. On a busy site, this can meaningfully reduce database load and speed up dynamic pages that regular page caching can’t fully cover — things like logged-in dashboards or WooCommerce carts.

The catch: this feature requires your server to support Redis or Memcached, two in-memory data stores that aren’t available on every hosting plan. Check with your host whether either is available before trying to enable this — if it isn’t, the setting simply won’t do anything useful, and it’s not worth chasing.

To set it up: go to LiteSpeed Cache > Cache > Object, enable Object Cache, and select Redis or Memcached based on what your host provides (they’ll tell you which, and often the connection details too). Once enabled, give it a day or two and check your site’s overall responsiveness, especially on dynamic, logged-in pages.

2. QUIC.cloud CDN Integration

QUIC.cloud is a CDN and optimization service built by LiteSpeed Technologies — the same company behind the plugin — which is why the integration is unusually seamless compared to connecting a generic third-party CDN. A CDN (content delivery network) stores copies of your site on servers around the world, so visitors load it from a location near them instead of one distant server.

QUIC.cloud goes further than a typical CDN: it also offers free-tier image optimization, low-quality image placeholders (a blurry preview that loads instantly while the real image finishes), and even DNS-level performance features. Under LiteSpeed Cache > General, you’ll find a QUIC.cloud connection option — it walks you through linking your domain, and the free tier covers a meaningful amount of traffic for most beginner-to-mid-size sites before any payment is involved.

If you’d rather use a different CDN you already have (like Cloudflare), LiteSpeed Cache also supports generic CDN mapping under the CDN tab — QUIC.cloud just tends to be the smoothest option specifically because it’s built by the same team as the plugin.

3. Database Optimization

Over time, your WordPress database accumulates clutter — old post revisions, trashed items sitting unemptied, spam comments, and expired transients (temporary cached data). None of it helps your site; it just makes your database larger and slightly slower to query. This is routine maintenance, not caching, but it’s bundled into the plugin because a leaner database supports everything else you’ve configured.

Under LiteSpeed Cache > Database, you’ll find checkboxes for cleaning revisions, trashed posts/comments, spam, and transients, plus a table optimization option. This is one of the lower-risk sections in this guide — run it periodically (monthly is reasonable for an active site) rather than obsessively.

4. The Cache Crawler

Here’s a problem you may not have realized exists: the very first visitor after your cache clears gets a slow, uncached page load, because nothing’s been saved yet for that URL. The Crawler, under LiteSpeed Cache > Crawler, solves this by having LiteSpeed itself visit your pages proactively and rebuild the cache before a real visitor ever hits that slow first load.

Enable it, and it’ll generate a list of your site’s URLs (often pulled from your sitemap) and crawl them on a schedule you set. For most beginner-to-intermediate sites, running it once after any major content update, or on a modest daily schedule, is plenty — there’s no need to crawl constantly.

5. ESI (Edge Side Includes) — The Advanced Feature

This is the one I told beginners to skip entirely, and for good reason: it’s the most powerful and most complex setting in the plugin.

The problem ESI solves: normally, if any part of a page is dynamic — a shopping cart icon showing item count, a “Hi, [Name]” login greeting — the entire page often can’t be fully cached, because that one small piece changes per visitor. That’s a real limitation on WooCommerce or membership sites, where otherwise-static pages get stuck being served uncached just because of one small widget.

What ESI actually does: it lets you mark specific small elements (like that cart icon) as their own separately-cached “hole” in an otherwise fully-cached page. The rest of the page — the 95% that’s identical for every visitor — gets served instantly from cache, while just that one small dynamic piece is generated fresh. It’s genuinely clever, and it’s why LiteSpeed Cache can achieve full-page caching on dynamic sites where other plugins can’t.

To use it, go to LiteSpeed Cache > Cache > ESI, enable ESI, and — if you’re running WooCommerce — LiteSpeed Cache includes some pre-built ESI blocks for common elements like the cart. For anything custom, this starts to move into developer territory (theme/plugin-specific ESI tags), so if you’re not comfortable there, enabling the built-in WooCommerce ESI blocks and stopping is a completely reasonable place to draw the line.

A Realistic Order to Tackle These

If all five feel like a lot at once, here’s the order I’d actually work through them in:

1. Database Optimization — lowest risk, do this first and periodically after.
2. Crawler — low risk, meaningful benefit, simple to set up.
3. QUIC.cloud CDN — moderate effort, strong payoff, especially the free tier.
4. Object Cache — only if your host confirms Redis/Memcached support.
5. ESI — save for last, and only if you’re running something like WooCommerce where it solves a real problem you actually have.

Conclusion

These five settings are the real reason LiteSpeed Cache has a reputation beyond “just another caching plugin” — they’re also exactly why I split this into two guides rather than throwing everything at you at once. Work through them at your own pace, test after every change, and keep that backup close by.

You don’t need all five to benefit. Even just Database Optimization and the Crawler, on top of your Part 1 setup, puts you ahead of most WordPress sites. Pick one from this guide, set it up carefully today, and add the rest as you get comfortable.

Frequently Asked Questions

Do I need Redis or Memcached for LiteSpeed Cache to work?

No, only for the Object Cache feature specifically. Regular page caching, minification, and the other basics from Part 1 work without either.

Is QUIC.cloud free?

It has a free tier that covers a meaningful amount of traffic and image optimization for most beginner-to-mid-size sites, with paid tiers for higher usage.

What is ESI and do I really need it?

ESI lets specific dynamic page elements (like a WooCommerce cart icon) be cached separately from the rest of an otherwise fully-cacheable page. It’s mainly valuable for WooCommerce or membership sites — mostly static sites can safely skip it.

How often should I run Database Optimization?

Monthly is reasonable for an active site. It’s low-risk routine maintenance, not something that needs constant attention.

Will enabling these advanced settings break my site?

They can, if misconfigured — which is why backing up first and changing one setting at a time matters. Object Cache and ESI carry the most risk; Database Optimization and the Crawler are lower-risk.

Can I use a different CDN instead of QUIC.cloud?

Yes. LiteSpeed Cache supports generic CDN mapping for services like Cloudflare under the CDN tab, though QUIC.cloud’s integration tends to be the smoothest since it’s built by the same company as the plugin.