Cached traffic is traffic that is delivered from CDN edge’s cache without request to the origin server.
You may track the Cache Hit Ratio percentage on the Report tab.
Cache Hit Ratio depends on the number of requests and the amount of traffic. If you have noticed that the cache hit ratio is 60% or less:
- Make sure that your website or application is integrated with CDN successfully: the static content is delivered through a custom domain, the custom domain is set up correctly.
- Make sure that more than 2 days have passed since you have started to use CDN.
- Deliver more content through CDN, if possible.
If you already set up CDN delivery for all possible static content, but the cache hit ratio remains low, revise the CDN resource’s cache settings:
CDN Caching option
Check if this option is added and activated. If you use this option with Origin controlled parameter make sure that origin settings are suitable for caching.
CDN caches according to Cache-Control headers from your origin.
Note: Cache-control directives that are not suitable for CDN: no-cache, no-store, private, max-age=0
Query-String and Set-Cookies options
CDN caches content with different query-strings and Set-Cookie headers separately by default If you have such content on your website or application, we recommend you to use Ignore Query-String and Ignore Set-Cookies options for the CDN-resource. It will help to decrease the number of requests from CDN to the origin server and increase the Cache hit ratio.
Large Files Delivery Optimization
Use the Large Files Delivery Optimization option for the large content caching. You may know more about the option from the article.
If you add any parameters (for example, a unique signature for users) to the URL, but not as a query string (
http://cdn.example.com/image.jpg?id=1), it requires custom caching keys set up.
Contact technical Support for manual settings and describe the URL scheme: which parts should be cached and which – should not.