Show top un-cached urls per week
under review
D
David Sayre
The goal is to get as much content cached in Cloudflare as possible. This benefits clients by having fast globally distributed websites. This benefits WPengine by having cloudflare take nearly all of the traffic and reduces the origin server resource usage.
However, there are ample opportunities where Wordpress is misconfigured (plugins) or custom code is not correctly configured to set request headers. Those need to be identified and addressed. Most clients have NO insight into what requests are cached or not becuase WPengine's Cloudflare is effectily secret data (except for the dashboard and detailed metric rollups). Cloudflare's API can produce the top 20 urls that were MISS or BYPASS and having that reported means it can be adressed and clients and WPengine benefits.
Having worked with dozend of WP sites, there are misconfigurations due to 3rd party plugins all the time, needlessly wasting hosting resources that could be solved with Cloudflare HIT caching.
A
Anna Blednova
marked this post as
under review
Thanks for sharing this feedback David! We actually have a couple of things already in the works to bring more visibility to the different cache statuses across both the CDN and origin caches, and it's helpful to understand how you might use the additional URL specific detail.
I'm curious to know if this type of analysis is something you would do on a site by site basis, perhaps as you're working on optimization, or something that you would want aggregated across any number of sites that you work on to better identify patterns across the board?
D
David Sayre
Anna Blednova Hi, We have several client sites under development and maintenance at any given time. We do periodic review of the site performance which includes looking at the site Cloudflare metrics, error logs, wordpress updates, plugin updates etc. Looking at the client's Cloudflare dashboard and seeing the Miss/Hit Ratio is an important health check. We have seen several client sites where a 3rd party plugin is installed by a client that will break the cache headers and we have to track it down to fix it.
We don't need a rollup across multiple sites becuase the 'fix' is always per site. But thank you for brainstorming this enhancement :)