Knowledge base
What the cache layer does, when to clear it, and why your change may not be showing yet.
Most of what a visitor loads never reaches PHP at all — it is served from cache, which is the single biggest reason a site here is fast.
The CDN, if you have one, serves images and static files from near the visitor. The server cache holds whole rendered pages, so a repeat visit does not run PHP. The Zinn® cache plugin on WordPress sites decides what is cacheable and clears the right pages when you publish.
Publishing, editing a post, or changing a menu clears the affected pages on its own. You need to clear it by hand after changing something the plugin cannot see you changed — a theme file edited over SFTP, a setting changed directly in the database.
Sites → your site → Cache → Clear.
Check in this order, because it is almost always the last one:
a local cache, and no amount of clearing ours will fix it.
Logged-in sessions, carts, checkouts and admin screens. A shop does not serve one customer another customer's basket, and that is enforced rather than configured.
What we have been writing about hosting, SEO and running sites at scale.
How hosting shapes indexing and link equity in 2026: keeping pages indexed, vetting aged domains before you build on them, link building without a footprint, and an honest line on what infrastructure can and cannot do for SEO.
Read the post →A practical checklist for fast, secure WordPress: server-level caching, a per-site object cache, the handful of plugins worth running, keeping the stack current, and the WooCommerce pages you must never cache.
Read the post →What actually separates good managed hosting from a cheap box with a control panel — migrations, backups, isolation, real caching and honest scaling — and how to judge it before you commit.
Read the post →Support is included on every plan, the desk is open 24 hours a day, and you can write to us in any of our 58 languages — we answer you in yours.
Contact support → All articles →