Cache performance

​​ Optimize cache ratios

Depending on the cache status you receive, you can make modifications to improve your cache ratio. To review the list of cache statuses, refer to Cloudflare cache responses .

• Dynamic: Default response for many file types including HTML. To cache additional content, refer to custom caching with page rules Open external link .
• Revalidated: To address an abnormal quantity of revalidated content, consider increasing your Edge Cache TTLs via a Page Rule or max-age origin directive .
• Expired: Consider extending Edge Cache TTLs for these resources via a Page Rule or enable revalidation at your origin.
• Miss: Although tricky to optimize, there are a few potential remedies:
  • Enable Argo Tiered Caching Open external link to check cache in another Cloudflare data center before checking the origin web server.
  • Create a custom cache key for multiple URLs to match the same cached resource, for example by ignoring query string.

​​ Example reports for troubleshooting cache performance

Several examples of helpful insights into your site performance via Cache Analytics include:

• Not caching HTML.

  • Identify the issue: Click Add filter and select Cache status equals Dynamic.
  • Resolution: Set a Cloudflare Page Rule to cache dynamic content .

• Short cache expiration TTL.

  • Identify the issue: Click Add filter and select Cache status equals Revalidated.
  • Resolution: Increase Cloudflare’s Edge Cache TTL via a Page Rule .

• Need to enable Tiered Cache or Custom Cache Key

  • Identify the issue: Click Add filter and select Cache status equals Miss.
  • Resolution: Enable Argo Tiered Caching or create a custom cache key .

• Interaction of HEAD requests with Cache

  • Cloudflare converts HEAD requests to GET requests for cacheable requests.
  • When you make a HEAD request for a cacheable resource and Cloudflare does not have that resource in the edge cache, a cache miss happens. Cloudflare will send a GET request to your origin, cache the full response and return the response headers only. Make sure the origin server is setup to handle GET requests, even if only HEAD requests are expected, so that compatibility with this behavior is ensured.