Zinn® Cache makes a WordPress site faster wherever it is hosted. On a LiteSpeed server it drives the server’s own page cache. When nginx, Varnish or Apache already caches pages in front of WordPress, it does not add a second page cache behind them: it tells them which pages changed. On any other ser
PricingFree downloadThe WordPress.org download is free. Pro versions, add-ons or external services may cost extra.
CompatibilityRequires WordPress 6.6 and PHP 8.2.
SourceWordPress plugins · Nov 16, 2026
01 / Source details
Aboutthistool.
Zinn® Cache makes a WordPress site faster wherever it is hosted. On a LiteSpeed server it drives the server’s own page cache. When nginx, Varnish or Apache already caches pages in front of WordPress, it does not add a second page cache behind them: it tells them which pages changed. On any other server it stores each page as a file and serves it before WordPress loads. It also installs a Redis object cache that proves it is working, and purges only the pages a change affects.
It is installed for you on sites hosted with Zinn Digital®, and it works the same way on any other host. There is one Zinn® cache plugin; Zinn® Cache Pro is an optional add-on that installs on top of it (see Pro features below).
What it does
Page cache on any server. On a LiteSpeed server it stamps X-LiteSpeed-Cache-Control and X-LiteSpeed-Tag headers so the web server serves full pages without hitting PHP or MySQL. On any other server it stores each complete page as a file under wp-content/cache/zinn-cache/ and serves it from advanced-cache.php before WordPress loads (it adds define( 'WP_CACHE', true ); to wp-config.php for that, and removes it again when the page cache is turned off). Only visitors who are not signed in are served stored pages, and only addresses with no query string (tracking parameters such as utm_source are ignored). If the third-party LiteSpeed Cache plugin is present, page caching is deferred to it instead.
Smart auto-purge. When content changes — a post or page is saved, trashed or deleted, a comment is added or moderated, a taxonomy term is edited — only the affected pages (and the listings they appear on: its home page, archive, categories, tags and author page) are purged, on every cache layer: LiteSpeed by cache tag, the disk cache, nginx, Varnish, Apache and Cloudflare by address. A change that touches every page (the theme, a plugin, an update, a menu, the site title) starts the paced refresh described below. The plugin can also mirror each purge to a control panel over a signed webhook, but only when ZINN_CACHE_PANEL_URL is defined — and the Zinn Digital® platform does not set it today, so on a Zinn-hosted site purges happen on the server and are not mirrored anywhere.
Redis object cache. A one-click toggle installs a self-contained Redis object-cache drop-in (requires the phpredis extension), offloading repeated database reads. It signs in with a plain password or a Redis 6+ ACL username and password, honours the usual WP_REDIS_* constants (including WP_REDIS_PASSWORD given as array( 'user', 'password' ) , WP_REDIS_PATH and WP_REDIS_MAXTTL ), and proves itself with a write-and-read round trip: if Redis refuses the login or the data, the settings screen says why. It never overwrites another caching plugin’s drop-in, refreshes its own after an update, and falls back to an in-memory cache if Redis is unreachable. Choose the igbinary serializer (smaller and faster, when installed) or PHP’s own; each value is read in the format it was written in, so switching is safe.
Host-managed object cache. A host that installs this drop-in for its customers (as Zinn Digital® hosting does) defines ZINN_CACHE_MANAGED_OBJECT_CACHE ; the plugin then never removes that drop-in and shows the cache as managed. A host whose Redis users may not run SCAN can define ZINN_CACHE_FLUSH_SOCKET , the path of a local helper that deletes only the calling site’s keys, so “Flush cache” keeps working.
Server caches in front of WordPress: nginx, Varnish, Apache. Zinn® Cache detects an nginx proxy_cache / fastcgi_cache , Varnish, Apache mod_cache or LiteSpeed in front of the site from the response headers, and then keeps its own disk cache out of the way. Tell it how to reach the cache and it purges changed pages there: nginx by a purge request (the ngx_cache_purge module), by deleting the cache files when WordPress can read the cache folder, or by writing the changed addresses to a folder your host’s purger reads; Varnish by PURGE or BAN ; Apache’s disk cache by deleting the entry files. Signed-in visitors, excluded addresses and form posts are sent Cache-Control: private, no-store , so a server cache never keeps one person’s page for the next.
Cloudflare purge. With a zone ID and an API token limited to Cache Purge, changed pages are purged from Cloudflare’s edge by address, in batches, from WP-Cron so editors never wait on it. Emptying the whole zone is off unless you allow it.
Paced refresh instead of “purge everything”. An update, a plugin activation, a theme or menu change or a site-wide setting no longer empties the cache at once, sending every visitor to WordPress in the same minute. Zinn® Cache refreshes a batch a minute instead (100 pages by default), newest first, to the end, and pauses while the server is busy. “Empty all now” is still there when you want it.
Status screen and per-address purge. One screen shows what serves your pages (LiteSpeed, nginx, Varnish, Apache, Cloudflare or the disk cache), what the last check saw in front of the site, each cache’s size where WordPress can read it, the purge queue, the paced refresh and recent purges with each layer’s answer. Purge any address, sample the hit ratio, or start and stop a refresh.
Autosave and an activity log. Settings save a moment after each change (the Save changes button stays). The Status screen lists the last 100 changes: who changed which setting (by name, never its value), who emptied the whole cache and when a paced refresh started.
Lighter pages. Control the WordPress Heartbeat, show text at once while Google Fonts load ( display=swap ), connect early to the servers your pages use, and serve images, CSS, JavaScript and fonts from a pull CDN address.
Safe cache exclusions. Ships with sensible WordPress and WooCommerce/Easy Digital Downloads defaults — cart, checkout, my-account, REST/AJAX, preview, search, and any logged-in or session-cookie request are never cached. Extra path, query-key, and cookie-prefix rules can be added per site.
Remote purging
A REST endpoint, POST /wp-json/zinn-cache/v1/purge , purges everything, specific URLs, or specific tags. It accepts a logged-in administrator, or any caller holding the site’s ZINN_CACHE_PANEL_SECRET who signs the request body with it (HMAC-SHA256) — so a deploy script or your own tooling can clear the cache. Your Zinn® dashboard does not call it today; there is no dashboard purge button for this plugin yet.
Pro features
Everything above is free and stays free. Zinn® Cache Pro is an add-on that installs on top of this plugin and adds:
A cache analytics screen: hit ratio, memory, keys and the slowest cache commands.
A slow-query and uncached-call finder that names the plugin or theme responsible.
An in-memory APCu tier in front of Redis for the hottest keys, plus prefetching and compression (zstd, lzf or gzip).
Tag-based purging for posts, terms and WooCommerce products, so only what changed is cleared, with the page and object caches purged together.
Automatic cache warm-up after a purge and when a paced refresh finishes, WebP and AVIF images, missing image width and height added from the file, unused-CSS removal and delayed JavaScript.
Cloudflare’s own cache-hit ratio for the last 24 hours on the status screen.
Scheduled database clean-up with a preview, and per-page cache rules.
Cache health alerts in your Zinn Digital® dashboard when the hit ratio drops or memory fills.
Pro costs $49 a year for one site, $99 for five sites and $199 for unlimited sites, and every plan starts with a 14-day free trial, no card needed. Start it from the Pro tab of the Zinn® Cache screen.
Source code
The complete source is public at https://github.com/Zinn-Digital/zinn-cache
External services
Cloudflare (only if you switch on Cloudflare purge)
When Cloudflare purge is on and a zone ID and API token are saved (or ZINN_CACHE_CLOUDFLARE_ZONE and ZINN_CACHE_CLOUDFLARE_TOKEN are defined), the plugin sends the addresses of changed pages on this site to https://api.cloudflare.com/client/v4/zones/<zone>/purge_cache so Cloudflare stops serving the old copies. Nothing else about the site or its visitors is sent. Cloudflare: terms https://www.cloudflare.com/terms/, privacy policy https://www.cloudflare.com/privacypolicy/
Your own site (cache detection)
The Status tab’s Check now button, and a daily check, request a few of this site’s own pages as a visitor would, to read which caches answered. These requests go only to this site’s own address.
AI apps you connect (MCP sign-in)
Only when an AI app such as Claude or ChatGPT starts connecting to the site’s MCP server does the site fetch that app’s public OAuth client metadata from the address the app gives, for example https://claude.ai/oauth/mcp-oauth-client-metadata or https://chatgpt.com/oauth/client.json . No site content is sent.
This plugin can connect your site to Zinn Digital® (the hosting platform it is built for) so that cache purges can be mirrored to it and the Zinn® dashboard can show what changed on the site.
What is sent, and when
Cache purges (only if ZINN_CACHE_PANEL_URL and ZINN_CACHE_PANEL_SECRET are defined). When content changes, the plugin posts the affected URLs and cache tags — no post content, no visitor data — to the address in ZINN_CACHE_PANEL_URL . The request is signed with an HMAC-SHA256 of the body using your site’s own secret. Note: the Zinn Digital® platform does not define ZINN_CACHE_PANEL_URL on the sites it hosts today, so on those sites nothing is sent.
Outbound link index (only if ZINN_SITE_LINKS_URL and ZINN_CACHE_PANEL_SECRET are defined). When a post is saved or removed, and on a daily pass, the plugin sends that post’s title , its permalink , and the links found in its content so link placements can be tracked from your Zinn® dashboard. This is post-deriv
See it in action
Screenshots & previews.
The Page cache tab: the full-page cache switch, how long a page stays cached, and whether signed-in visitors are ever served a cached page. The panel above the tabs says plainly when the server cannot cache — here, a server that is not LiteSpeed.The Purging tab: clear only the affected pages when content changes, clear everything after an update, and the tools to purge by hand or export your settings.The Exclusions tab: addresses, query parameters and cookies that are never cached, on top of the WordPress and WooCommerce defaults that always apply.Every screen is translated — here the Page cache tab in Arabic, right to left.
02 / Source details
Gettingstarted.
01Upload the zinn-cache folder to /wp-content/plugins/ (this is done automatically as part of the Zinn® deploy footprint).
02Activate the plugin through the Plugins screen in WordPress.
03Go to Zinn Digital® → Cache to configure the full-page cache, object cache, auto-purge, and exclusions.
Optionally define these constants in wp-config.php (set automatically on Zinn-hosted sites):
04ZINN_CACHE_PANEL_URL and ZINN_CACHE_PANEL_SECRET — enable signed purge mirroring to the control plane.
Open Zinn Digital® → Cache → Status and press Check now . If nginx caches your pages, the screen says so and Zinn® Cache does not install its own page cache behind it. Then open the Server cache tab, choose nginx , and choose how to purge it: a purge request per page if your nginx has the ngx_cache_purge module (set “Send purges to” to http://127.0.0.1 when a CDN is in front); delete the cache files if WordPress can read the folder in your proxy_cache_path or fastcgi_cache_path line (copy the folder, the levels= value and your cache key); or write the addresses to a folder your host’s purger reads. Save, then purge one address from the Status tab and check that its next visit says MISS. If nginx does not cache your pages at all, choose None and Zinn® Cache’s own page cache does the job.
Varnish, Apache mod_cache or Cloudflare?
Varnish: choose Varnish , give its address and port, and allow PURGE (or BAN ) from this server in your VCL. Apache: put mod_cache in a reverse-proxy virtual host in front of WordPress — inside the same server as WordPress’s own rewrite rules, Apache stores every address as /index.php and can serve one page for all of them; the status screen warns when it sees that. Cloudflare: switch on Cloudflare purge and paste a zone ID and a token limited to Cache Purge.
Why does an update no longer empty the cache?
Because emptying it sends every visitor and every crawler to WordPress in the same minute, and on a large site that can take the server down. Updates, plugin activations, theme and menu changes start a paced refresh: every page is refreshed, a batch a minute, newest first, until the whole site is done, and the refresh pauses while the server is busy. Empty all now on the settings screen empties everything at once when you want that.
Why is there no “combine CSS/JS”, “minify” or “separate mobile cache” option?
On purpose. Combining files was a workaround for HTTP/1.1; on HTTP/2 and HTTP/3 it makes pages slower to start and breaks caching of shared files, which is why other cache plugins have been retiring it. Minifying saves a few percent once files are compressed (gzip or Brotli) and is the most common cause of a broken layout after installing a cache plugin. A separate mobile cache doubles every cached page and every server-cache key for themes that are responsive anyway; Zinn® Cache Pro’s warm-up can warm a mobile pass for the few sites that do serve phones a different page.
Does this require LiteSpeed?
Full-page caching requires a LiteSpeed web server (or the third-party LiteSpeed Cache plugin). On any other server nothing reads the cache headers, so pages are not cached — and the settings screen says so plainly rather than looking as if it works. Everything else (object cache, exclusions, and the signed purge endpoint) still works.
Does it conflict with the LiteSpeed Cache plugin?
No. If the LiteSpeed Cache plugin is active, Zinn® Cache defers page caching to it and routes purges through its public actions.
What happens if Redis is unavailable?
The object cache is optional. 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.
How do I clear the cache from the command line?
With WP-CLI: wp zinn-cache purge all empties every cached page, wp zinn-cache purge url https://example.com/pricing/ (or just /pricing/ ) empties those pages, and wp zinn-cache purge post 42 empties a post’s page and the lists it appears on. Each prints how many stored pages it removed. On a LiteSpeed server the purge is sent to the server with the next request, which the command makes itself.
FinderPress Media Auditor helps site administrators scan for broken images, missing Media Library files, unreachable media URLs, and other media issues across WordPress content. Use it to audit images, video, audio, PDFs, featured images, and attachment files without sending scan data to an external
The Accepted Payment Methods plugin is a straightforward, lightweight solution that enhances your website by displaying visually appealing icons of the payment methods you accept. This plugin is ideal for a variety of websites, including e-commerce platforms, service-oriented websites, and informati