Platform · Caching

LiteSpeed + Redis.
The cache stack WordPress wants.

Page cache served from RAM in single-digit milliseconds. Object cache that keeps MySQL out of the request path. Pre-installed, pre-tuned, included on every plan, no plugin licensing required.

See Plans See the Full Stack

Bundled, configured, monitored

LiteSpeed Enterprise (web server + LSCache) and Redis 7 are pre-installed and tuned per site. Nothing to license, nothing to configure.

What you're actually getting

Two caches. Two different jobs.

Most hosts ship one or the other. We ship both, pre-wired so they cooperate instead of fighting each other.

Page cache

LiteSpeed Enterprise + LSCache

LiteSpeed serves a fully-rendered HTML copy of every cacheable page directly from RAM. Repeat visitors skip PHP and MySQL entirely, the response is essentially a memory read.

Pages served in 2–8 ms from RAM
ESI tags cache static parts, leave cart & account dynamic
Auto-purge on post, plugin and theme updates
Brotli + HTTP/3 enabled by default

Object cache

Redis 7 (per-site instance)

Redis keeps WordPress's internal object lookups, options, user meta, term queries, in memory. The result is fewer MySQL round-trips on every uncached request: logged-in pages, the admin, WooCommerce checkout.

Cuts MySQL queries by 60–90% on transactional sites
Per-site Redis instance, no cross-tenant collisions
Object Cache Pro drop-in pre-installed
Auto-flushed on plugin & theme updates

The request lifecycle

What a single page load looks like.

Two caches sitting in front of WordPress, each catching a different kind of work.

2–8 ms

Step 1

Request hits LiteSpeed

If the URL is cacheable and a fresh copy exists in RAM, LiteSpeed answers immediately. PHP and MySQL never run.

PHP runs

Step 2

Cache miss → PHP-FPM

On a miss (logged-in, checkout, admin, first visit) the request is handed to PHP. WordPress starts asking for objects.

Sub-ms reads

Step 3

WordPress asks Redis first

Object lookups (options, user meta, queries) are served from Redis in under a millisecond. MySQL only sees what isn't cached.

Self-warming

Step 4

Result is stored, then served

LiteSpeed stores the rendered HTML for the next visitor. Redis stores any new objects. The next request is instant.

Median TTFB · same WordPress + WooCommerce site

The cache stack does most of the heavy lifting.

Same site, same plugins, same database, only the cache layer changes. Lower is better.

internal benchmark · 30-run median

Cached (LiteSpeed RAM)

6 ms

Uncached + Redis (WP Tango)

124 ms

Uncached, no object cache

612 ms

Industry average shared host

940 ms

Where it matters most

Different sites, same stack.

LiteSpeed handles what can be cached. Redis handles everything that can't. Together they cover every kind of WordPress workload.

Content publishers

Front pages and articles serve from LiteSpeed RAM cache. Even a viral spike is essentially free. PHP barely runs.

5–10 ms

cached TTFB

WooCommerce stores

ESI keeps mini-cart, account, and checkout live while caching the rest of the page. Redis absorbs option and session lookups.

60–90%

fewer MySQL queries

Membership & LMS sites

Logged-in pages can't use page cache. Redis is what makes them feel fast, every option lookup is a memory read, not a disk seek.

3–5×

faster admin & dashboards

Vs. the usual suspects

Most hosts ship one cache. We ship both.

Capability	WP Tango	Kinsta	WP Engine	Generic shared
LiteSpeed Enterprise web server
Page cache served from RAM
Redis object cache (per-site)				Add-on
Object Cache Pro pre-installed
ESI partial-page caching
HTTP/3 + Brotli by default

Frequently asked questions

LiteSpeed and Redis, plainly explained.

The same questions our team gets on every demo call.

Included on every plan

Cache that's actually configured.

No extra licenses. No extra plugins. No 14-page setup guide. Just two best-in-class caches, pre-tuned for your WordPress.

See plans Talk to migrations

6 ms

Median cached TTFB

80%+

Fewer MySQL queries

Plugins to license

24/7

Monitored by humans

LiteSpeed + Redis.The cache stack WordPress wants.