Comments on: Using HttpWatch to Measure Page Load Times for New and Existing Users http://blog.httpwatch.com/2008/05/14/using-httpwatch-to-measure-page-load-times-for-new-and-existing-users/ News, articles and all things HttpWatch Wed, 19 Nov 2008 23:39:25 +0000 http://wordpress.org/?v=2.6.3 By: Httpwatch Blog http://blog.httpwatch.com/2008/05/14/using-httpwatch-to-measure-page-load-times-for-new-and-existing-users/#comment-1264 Httpwatch Blog Tue, 29 Jul 2008 11:25:26 +0000 http://blog.httpwatch.com/2008/05/14/using-httpwatch-to-measure-page-load-times-for-new-and-existing-users/#comment-1264 Denny, We do not have plans to support mobile devices. Denny,

We do not have plans to support mobile devices.

]]> By: Denny http://blog.httpwatch.com/2008/05/14/using-httpwatch-to-measure-page-load-times-for-new-and-existing-users/#comment-1263 Denny Tue, 29 Jul 2008 10:49:37 +0000 http://blog.httpwatch.com/2008/05/14/using-httpwatch-to-measure-page-load-times-for-new-and-existing-users/#comment-1263 Does httpwatch has a plan to release on mobile devices, e.g. a plugin for IEMobile? Does httpwatch has a plan to release on mobile devices, e.g. a plugin for IEMobile?

]]> By: Httpwatch Blog http://blog.httpwatch.com/2008/05/14/using-httpwatch-to-measure-page-load-times-for-new-and-existing-users/#comment-383 Httpwatch Blog Fri, 23 May 2008 19:01:15 +0000 http://blog.httpwatch.com/2008/05/14/using-httpwatch-to-measure-page-load-times-for-new-and-existing-users/#comment-383 Tad, That's a good point about having to re-authenticate or re-submit data to get to certain pages. We tried to simplify the post by just showing how you could test something like a home page. The reason for having to restart IE is the image cache (see http://blog.httpwatch.com/2008/02/27/image-caching-in-internet-explorer/ ). You can cause a new browser session to be created by using 'Clear All Cookies' or 'Clear Session Cookies' in HttpWatch. This has the side effect of creating a new session. If you then navigate to another location e.g. about:blank before clearing the session you should see the normal automatic cache validation when you re-visit the page. Unfortunately, the IE image cache is not reset when a new browser session is created. So you are forced to restart IE if you want to replicate a primed cache visit and see which images are accessed by IE. Tad,

That’s a good point about having to re-authenticate or re-submit data to get to certain pages. We tried to simplify the post by just showing how you could test something like a home page.

The reason for having to restart IE is the image cache (see http://blog.httpwatch.com/2008/02/27/image-caching-in-internet-explorer/ ).

You can cause a new browser session to be created by using ‘Clear All Cookies’ or ‘Clear Session Cookies’ in HttpWatch. This has the side effect of creating a new session. If you then navigate to another location e.g. about:blank before clearing the session you should see the normal automatic cache validation when you re-visit the page.

Unfortunately, the IE image cache is not reset when a new browser session is created. So you are forced to restart IE if you want to replicate a primed cache visit and see which images are accessed by IE.

]]> By: tad http://blog.httpwatch.com/2008/05/14/using-httpwatch-to-measure-page-load-times-for-new-and-existing-users/#comment-381 tad Fri, 23 May 2008 17:29:44 +0000 http://blog.httpwatch.com/2008/05/14/using-httpwatch-to-measure-page-load-times-for-new-and-existing-users/#comment-381 The issue with starting a new instance of IE is that the session gets killed. You'd have to re-login, or in the case of a form, possibly resubmit data to get back to the page you want to check. The reason why you need to restart the session (which is missing from the article) is due to the way IE handles its cache. If you hit refresh, or navigate to the page without closing the instance, you'd get inconsistent results. For details, check out: http://msdn2.microsoft.com/en-us/library/bb250442(VS.85).aspx For these tests, you'd also want to make sure your cache setting is set to "Automatically." A different setting will also bring different results. The issue with starting a new instance of IE is that the session gets killed. You’d have to re-login, or in the case of a form, possibly resubmit data to get back to the page you want to check.

The reason why you need to restart the session (which is missing from the article) is due to the way IE handles its cache. If you hit refresh, or navigate to the page without closing the instance, you’d get inconsistent results. For details, check out: http://msdn2.microsoft.com/en-us/library/bb250442(VS.85).aspx

For these tests, you’d also want to make sure your cache setting is set to “Automatically.” A different setting will also bring different results.

]]>