Zinn® Cache
by Zinn Digital® 0 (0 reviews)

Zinn® Cache

Page cache, Redis object cache and purging for nginx, Varnish, Apache, LiteSpeed and Cloudflare — updates refresh pages gradually, never all at once.

Zinn® Cache ranks #21,336 among WordPress.org plugins with 50+ active installations, is #488 of 1,658 in the Performance category, and was last updated Oct 26, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1.4
v1.11.1 Current Version v1.11.1
Updated 1 week ago Last Update on 26 Oct, 2026
Refreshed 1 week ago Last Refreshed on
#488 of 1,658 in Performance Top 50% by installs Downloads +120.5% this week Actively maintained
View on WordPress.org
Rank
#21,336
— No change
Active Installs
50+
+117.4%
KW Avg Position
83.3
1 worse
Downloads
1.9K
+97 today
Support Resolved
0%
— No change
Rating
0%
Review 0 out of 5
0 (0 reviews)

Next Milestone 60

Total Progress 30%
50+ 60+
2,387
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

  • Exact install estimates within tiers
  • Track install growth over time
  • Milestone progress predictions
Upgrade to Pro
Need 7 more installs to reach 60+

Rank Changes

20,269 20,803 21,336 21,869 22,403 31-10-2026 01-11-2026 02-11-2026 03-11-2026 04-11-2026 05-11-2026 06-11-2026 07-11-2026
20,524 20,747 20,970 21,193 21,416 23-10-2026 24-10-2026 25-10-2026 26-10-2026 27-10-2026 28-10-2026 29-10-2026 30-10-2026 31-10-2026 01-11-2026 02-11-2026 03-11-2026 04-11-2026 05-11-2026 06-11-2026 07-11-2026
Current #21,336
Change
Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Active Installs 0,000,000+
Growth +0.0%
Peak 0,000,000

Downloads Growth

0 50 100 150 200 31-10-2026 01-11-2026 02-11-2026 03-11-2026 04-11-2026 05-11-2026 06-11-2026 07-11-2026
0 50 100 150 200 23-10-2026 24-10-2026 25-10-2026 26-10-2026 27-10-2026 28-10-2026 29-10-2026 30-10-2026 31-10-2026 01-11-2026 02-11-2026 03-11-2026 04-11-2026 05-11-2026 06-11-2026 07-11-2026
Downloads
Growth
Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

0.0
0 reviews
Overall 0%
5
0 (0%)
4
0 (0%)
3
0 (0%)
2
0 (0%)
1
0 (0%)

Frequently Asked Questions

Common questions about Zinn® Cache

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: 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.
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.
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.
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.
No. If the LiteSpeed Cache plugin is active, Zinn® Cache defers page caching to it and routes purges through its public actions.
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.
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.

Sign In / Register

You need to sign in or register to use this feature.