Caching resources is one of the most popular web performance optimization techniques used today. Caching means that the data is temporarily stored closed to the users so that they do not have to systematically be fetched through the network.
This technique improves overall web performance. First, it dramatically reduces the time required to fetch resources. Secondly, it helps reduce the stress put on the origin server.
Caching can be implemented at an intermediate proxy server level (server-side caching) or at the user's browser level (browser-side caching). Please refer to this blog article for more details.
Kadiska provides visibility on browser-side caching. For server-side caching, Kadiska can still identify the hostname delivering the content (proxy server, CDN, gateway,...).
Browser-side caching level is shown as a pourcentage of resources that are cached vs uncached.
This information is available in the "Resources Analysis" section. It can be grouped at different levels:
|Level||Base of pourcentage calculation|
|Pages||% calculated for all resources (hits) that are part of specific pages|
|Resource Type||% calculated for specific resources types|
|Hosts||% calculated for all resources that are delivered by specific hosts|
|Resources||% calculated for specific resources|
|iniator Type||% calculated for resources fetched from specific Initiator Types|