- Turn it on
- What is cached — and what never is
- Purge after every deploy
- Make your pages cacheable
- Static and PHP sites
Turn it on
Dashboard → Marketing → Marketplace → your app project → Ninza Speed card. Choose how long a page is kept (1 minute is a safe start; 5–30 minutes for content that rarely changes) and press Turn the page cache on. Free on every plan.
What is cached — and what never is
- Only GET and HEAD requests without cookies and without an Authorization header are cached, so signed-in users, admin pages and APIs that use tokens always reach your app.
- A response that sets a cookie, or says
Cache-Control: privateorno-store, is never kept. - The response header
X-CacheshowsHIT,MISSorBYPASS. Add?nocache=1to any address to see it fresh.
Purge after every deploy
Press Purge now after a deploy, or turn the cache off and on. Git deploys and restarts do not purge on their own, so a page may show its previous version until it expires.
Make your pages cacheable
- Express / Next.js / NestJS: do not start a session for anonymous visitors (e.g.
saveUninitialized: falsein express-session). Next.js pages that use cookies() or headers() are dynamic — keep them for signed-in areas only. - Django: anonymous pages without CSRF forms are cacheable; pages with forms set a csrftoken cookie and are bypassed (that is correct).
- Flask / FastAPI: send
Cache-Control: public, max-age=60on public pages; avoid setting a session cookie on every response. - Spring Boot: avoid creating an HttpSession for anonymous visitors (JSESSIONID); Spring Security’s defaults send
no-store— relax it only for public pages. - Put a page cache in front of pages that are the same for everyone: home, product and blog pages, landing pages.
Static and PHP sites
Static websites are already served straight from files by the web server — the fastest possible — so there is no page cache to add. Plain PHP sites run your own code on every visit and a shared cache could mix visitors’ pages, so it is not offered; cache in your code, compress images to WebP and keep scripts few. Both get a PageSpeed link in the same card.
Stuck? Our engineers answer support tickets around the clock. Contact us, or create an account and open a ticket from the dashboard — the same guides are there too.