Caching & speed
Most visits to a Zinn Digital® site never touch PHP or MySQL. A LiteSpeed full-page cache, a per-site Redis object cache and the CDN edge work together, coordinated by smart auto-purge, so pages stay fast and origins stay quiet — across 100,000+ hosted PBN sites in every niche.
Speed comes from serving the right thing from the fastest place. We stack three caches so a request is answered as early as possible — at the edge, at the web server, or from memory — and never has to rebuild a page it already built.
On LiteSpeed hosts, cacheable front-end responses are stamped with LiteSpeed cache-control and tag headers, so the web server serves complete pages without invoking PHP or querying MySQL. That is the biggest single win for time-to-first-byte on WordPress.
A one-click toggle installs a self-contained Redis object-cache drop-in, offloading repeated database reads. If Redis is ever unreachable the drop-in falls back to a per-request in-memory cache, so the site keeps working.
Static assets and cacheable pages are served from the CDN close to visitors. Purges are mirrored to the edge so it stays in step with the origin cache — one control, not three disconnected settings.
A cache is only useful if it clears the right pages at the right moment. Ours watches for real changes and purges surgically using LiteSpeed cache tags — not a blunt flush-everything on every edit.
Aggressive caching is only safe when the things that must stay live never get cached. Zinn Cache ships with sensible WordPress and WooCommerce / Easy Digital Downloads defaults: cart, checkout, my-account, REST and AJAX, preview and search are excluded, and any logged-in or session-cookie request is served fresh.
That means a shopper never sees someone else's cart and a logged-in editor never sees a stale draft. You can add extra path, query-key and cookie-prefix rules per site when a plugin needs them, without touching the safe defaults.
Caching is a per-blueprint capability, so static, PHP and Node sites each get the caching that suits them, and the plugin degrades gracefully wherever a full-page cache layer is absent.
No. The Zinn Cache plugin ships in the deploy footprint and the full-page cache, object cache, auto-purge and safe exclusions are wired up on Zinn-hosted sites automatically. You can fine-tune everything under Settings → Zinn Cache, or from the dashboard, if you want to.
No. Cart, checkout, my-account, and any logged-in or session-cookie request are never cached by default, so dynamic and per-customer pages always stay live. The full-page cache only serves pages that are the same for every visitor.
The object cache is optional and fails safe. If the phpredis extension is missing the toggle is disabled with a notice; if Redis becomes unreachable at runtime, the drop-in serves from a per-request in-memory cache so the site never breaks.
Full-page caching uses a LiteSpeed web server, or the third-party LiteSpeed Cache plugin if it is already active. On other servers no cache headers are emitted, but the object cache, exclusions and remote purge all still work.
One coordinated purge. When content changes, targeted tag-based purges clear the affected pages at the web server and are mirrored to the CDN and edge over a signed webhook, so every layer clears the same pages at the same time.
Start a card-free 7-day trial and let the multi-layer cache do the work. Free migrations, a 30-day money-back guarantee, a 99.99% uptime assurance and no vendor lock-in.
Start free