Knowledge base
The Zinn® Cache Engine plugin
Full-page, object and database caching for a WordPress site hosted anywhere — what to turn on first and what to leave alone.
Zinn® Cache Engine is for a WordPress site hosted anywhere, including with another host. It brings its own caching rather than driving ours, so it is the right choice when your site is not on Zinn® hosting. If your site is hosted with us, install Zinn® Cache instead — the two do the same job by different means and running both is never right.
It is a fork of LiteSpeed Cache, released under the GPL, with the parts that reported to a third-party service removed.
Turn on, in this order
- Page cache. This is where nearly all the speed comes from. Switch it on, then load your
- Browser cache. Free, and helps repeat visitors.
- Object cache, if your host offers Redis or Memcached. Big win on shops and membership
- CSS/JS optimisation — last, and one option at a time. This is the only section that can
site in a private window and confirm it looks right.
sites, little effect on a small brochure site.
visibly break a theme. Turn on one setting, load the site, then the next.
What to leave alone until you have a reason
Combining and inlining CSS, deferring JavaScript, and lazy-loading iframes are all real improvements and all of them can break a specific theme or slider. There is no way to know which without trying, so change one, look at the site, and keep a note of what you changed.
Excluding pages
Anything transactional should not be page-cached: cart, checkout, account pages, and any page that shows different content to different logged-in people. WooCommerce and Easy Digital Downloads pages are excluded for you.
If the site looks broken after switching something on
Turn off CSS/JS optimisation first — it is the cause the overwhelming majority of the time. Then purge everything and reload. If that fixes it, re-enable its settings one at a time until you find the one your theme dislikes.
Updates
The plugin updates itself from us, not from WordPress.org, so it will never be replaced by the upstream plugin it was forked from.
Still stuck?
Support is included on every plan and answers in your own language.
Contact support → All articles →