Understanding Cache templates

Cache is now in limited release. Visit our Help Centre guide for details on how to join.

Cache templates determine when and how we store webpage data to make sites load faster. The goal is to cache as much as possible without saving content that might change frequently or be unique to a user.

To decide what to cache, we ask questions like:

  • Are there pages or URLs that always return different content?
  • Do certain cookies indicate that the response is unique?
  • Do specific URL parameters (like search queries) change the response?

Based on these rules, we optimise cache templates for different types of websites:


  • WordPress Caching

    For a basic WordPress site:

    • Pages usually stay the same for all visitors, except when users are logged in.
    • Blog posts and static pages don’t change per visitor, so they can be cached.
    • We do not cache admin pages, AJAX calls, or pages shown to logged-in users.





  • WooCommerce Caching (E-commerce Sites)

    E-commerce sites require a more complex approach because:

    • Product pages don’t change for guests but may update quickly (e.g., showing live stock levels).
    • To avoid showing outdated product info, we cache product pages for a short time.
    • We never cache cart and checkout pages because they are unique to each user.
    • Any request with cart-related cookies is ignored to prevent caching personalised shopping cart details.





  • Default Caching template

    If a website doesn’t use WordPress or WooCommerce, we take a cautious approach:

    • It’s better not to cache a page than to cache one that shouldn’t be.
    • We skip caching for URLs that contain words like “login,” “register,” “api,” or “admin.”
    • We also ignore requests with any cookies to prevent storing user-specific content.

    This template ensures safe caching for websites that don’t have a specific optimisation in place.





  • What content is cached and what is not?

    What is cached:

    • Images
    • Javascript
    • CSS
    • Static pages

    What is not cached:

    • POST requests
    • Ajax calls
    • Any content over 5MB
    • Any unique content
      • Site content when logged in to CMS backend
      • Site content when visitors are logged in their account on your website
      • Any cart or checkouts pages 
      • URLs that contain login, register, api, admin or anything admin related



Related Posts: