Hi J.Hov,
1. By default pages use ASPNET caching. If you want you can create your own caching provider and use it with pages. However I believe that you have enabled page caching through backend UI.
In the following section called caching you set caching duration ( in seconds) and slidingExpiration.
slidingExpiration - The data will remain in the cache until two minutes passes without anything referencing it.
Required. Time, in seconds, the page should be cached. Must be a positive integer.
Generally everything is standard ASP.NET implementation.
The following articles described everything about ASP.NET caching
ASP.NET Caching Features
ASP.NET Caching
ASP.NET Caching: Techniques and Best Practices
Anyway, the problem with your pages comes from the server. There is a duration during returning the request from a server once a page is called. So when I request a page there is about 3-6 seconds that I am waiting for a response message from the server.
Generally when a page is accessed for the first time it opens slowly, but it goes to the ASP.NET Memory cache and then after the second request the response is faster. My test ( which is attached ) shows that I receive the second, third and fourth request are faster. If one of the next request is handled by not the same server ( I suppose you have two servers in load balance) the response will be slower again.
The attached xml includes report for the response time of http://demo.thedominion.ca/MediaCentre/MediaSummaries.aspx?Year=2009 at our end. The check is made with HTTP WATCH. This is what we could say for now.
Kind regards,
Ivan Dimitrov
the Telerik team