Knowledge base
The Zinn® Cache plugin
What it does on a site we host, how to purge, and when the Redis object cache is worth switching on.
Zinn® Cache is the plugin for sites hosted with us. It does not do the caching itself — your server already does that — it tells the server what to cache and when to throw it away. If your site is hosted somewhere else, the plugin you want is Zinn® Cache Engine instead; installing both on one site is never right.
Check this first
Settings → Zinn® Cache shows a status panel at the top. If it says the LiteSpeed server is not detected, nothing below will have any effect and that is the thing to fix — open a ticket and we will look at the server, not at your site.
Purging, and why you rarely need to
Publishing a post, editing a page, changing a menu or switching theme already purges what changed. The plugin purges by tag, so editing one post clears that post, the pages it appears on and your feeds — not your whole site. That is why your site stays fast after an edit instead of going slow for ten minutes.
Purge everything now is on the same screen for the times you have changed something we cannot see, such as editing a template file over SFTP.
The Redis object cache
The toggle installs a drop-in that keeps WordPress's own internal lookups in memory between requests. It helps most on:
- WooCommerce and any shop with a large catalogue
- sites with many plugins
- membership or forum sites, where almost every page is logged-in
It helps least on a small brochure site that is already fully page-cached. Switch it on, watch the site for a day, and switch it off again if you see nothing — it is reversible and it never overwrites a drop-in another plugin installed.
Exclusions
Cart, checkout, my-account and any logged-in session are never cached, and you do not have to configure that. Add your own rules only when you have a page that must always be fresh — each rule you add is a page that stops being fast, so add them one at a time.
If a change is not showing
In this order: purge that page from the plugin screen; hard-reload in your browser (Ctrl-Shift-R); check whether a CDN in front of us is holding it. Three different caches can hold a page and only the first one is ours.
Still stuck?
Support is included on every plan and answers in your own language.
Contact support → All articles →