Title: Understanding expected cache length
Last modified: July 30, 2022

---

# Understanding expected cache length

 *  Resolved [MindingData](https://wordpress.org/support/users/mindingdata/)
 * (@mindingdata)
 * [3 years, 10 months ago](https://wordpress.org/support/topic/understanding-expected-cache-length/)
 * I’ve installed this plugin on my site and I think for the most part, it’s working
   as expected.
 * But what I do notice is that I’m getting a lot more “misses” and “expired” than
   I thought I would. I assumed that the pages would be cached almost indefinitely,
   but I can see they expire fairly regularly.
 * While I’ve been typing this, I clicked around the site for a bit just using the
   left hand menu, and I got a miss. The full result is as follows :
 *     ```
       alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400
       cache-control: s-maxage=31536000, max-age=60
       cache-provider: CLOUDWAYS-CACHE-DC
       cf-cache-status: MISS
       cf-ray: 7329f5558e8ba832-SYD
       content-encoding: br
       content-type: text/html; charset=UTF-8
       date: Sat, 30 Jul 2022 00:25:39 GMT
       server: cloudflare
       vary: Accept-Encoding
       x-cache: HIT
       x-wp-cf-super-cache: cache
       x-wp-cf-super-cache-active: 1
       x-wp-cf-super-cache-cache-control: s-maxage=31536000, max-age=60
       x-wp-cf-super-cache-cookies-bypass: swfpc-feature-not-enabled
       ```
   
 * Notice how the XCache says hit but Cloudflare says miss. If I refresh, obviously
   next load I got a hit.
 * This was maybe 5 minutes after the last refresh of this page I went from Hit 
   to Miss to Hit. Is this expected? In a similar vein, I can receive EXPIRED cloudflare
   headers when x-cache is a hit also.
 * Note that I am using Cloudways as a hosting provider, and I am using their “Breeze”
   plugin for caching (Similar to WP Super Cache etc), which is somewhat required
   now due to all the misses I seem to be getting.
 * It doesn’t seem that uniform. For instance on the homepage, I am currently seeing
 * `age: 1621`
 * Which would indicate that this is almost 30 minutes old in the cache. So I don’t
   think it’s necessarily something to do with headers as that would be across the
   entire site.
    -  This topic was modified 3 years, 10 months ago by [MindingData](https://wordpress.org/support/users/mindingdata/).
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Funderstanding-expected-cache-length%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 2 replies - 1 through 2 (of 2 total)

 *  Plugin Contributor [iSaumya](https://wordpress.org/support/users/isaumya/)
 * (@isaumya)
 * [3 years, 10 months ago](https://wordpress.org/support/topic/understanding-expected-cache-length/#post-15876362)
 * Hi,
    First of all this support is related to this plugin and not Breeze. Anyways,
   as I can see you are using both this plugin and Cloudway’s server level page 
   caching system from where the `x-cache` is coming from as that is not added by
   this plugin.
 * When using this plugin it is highly recommended not to use any other page caching
   system – be that plugin based or server level.
 * Now coming to cache lifespan, I will recommend you to enable Cloudflare Tiered
   Cache and if possible get Cloudflare Cache Reserve ([https://blog.cloudflare.com/introducing-cache-reserve/](https://blog.cloudflare.com/introducing-cache-reserve/))
   which will increase your HIT ration in cloudflare CDN.
 * Actually the lifespan of any request in Cloudflare cache depends on the traffic
   to it. To learn more read: [https://acnam.com/untold-truths-of-cloudflare-cdn/#cloudflare-cache-creation-replication-storage](https://acnam.com/untold-truths-of-cloudflare-cdn/#cloudflare-cache-creation-replication-storage)
 *  Thread Starter [MindingData](https://wordpress.org/support/users/mindingdata/)
 * (@mindingdata)
 * [3 years, 10 months ago](https://wordpress.org/support/topic/understanding-expected-cache-length/#post-15876381)
 * Hi Saumya,
 * Thanks so much for your help. I’ve definitely done more reading and it does seem
   it’s more likely that cloud flare is just evicting low requested pages after 
   some time (which makes sense given I’m on the free plan after all).
 * I use breeze/a WordPress caching plugin on the [site](https://itexamstudyguides.com)
   mostly because if it is a cloud flare miss, then having the back up of breeze
   is worth while (although am aware of the pain of multiple caches if I need to
   clear the cache in multiple places).
 * Basically, thanks so much for the help and everything is working fine for now!

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Understanding expected cache length’ is closed to new replies.

 * ![](https://ps.w.org/wp-cloudflare-page-cache/assets/icon-256x256.gif?rev=3234997)
 * [Super Page Cache – Cloudflare Cache, Page Speed & Core Web Vitals](https://wordpress.org/plugins/wp-cloudflare-page-cache/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wp-cloudflare-page-cache/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wp-cloudflare-page-cache/)
 * [Active Topics](https://wordpress.org/support/plugin/wp-cloudflare-page-cache/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wp-cloudflare-page-cache/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wp-cloudflare-page-cache/reviews/)

 * 2 replies
 * 2 participants
 * Last reply from: [MindingData](https://wordpress.org/support/users/mindingdata/)
 * Last activity: [3 years, 10 months ago](https://wordpress.org/support/topic/understanding-expected-cache-length/#post-15876381)
 * Status: resolved