| 12:35 am on Mar 16, 2009 (gmt 0)|
Are you wanting to check on the load time that your users are actually experiencing, or the speeds you are seeing at your end?
| 9:31 am on Mar 16, 2009 (gmt 0)|
What I'm seeing on my end would be sufficient. I know that Firebug, et al can do those things but, ideally, what I'd want would be to have something that I could run 10/20/n times and I could programatticaly store the results in a database. Firebug does what I want but I have to manually copy/paste into an Excel spreadsheet, for example.
If there isn't an easy way then I'm fine using something like Firebug to copy/paste; I was just hoping there was/is a more elegant way. I'd like to be able to do reporting against and say, "Bounce rates were 12% higher whenever Google Analytics tracking code load time exceeded 1000ms" or whatever.
| 9:53 am on Mar 16, 2009 (gmt 0)|
this paper might give you some good ideas.
Episodes: a Framework for Measuring Web Page Load Times:
| 9:59 am on Mar 16, 2009 (gmt 0)|
|the problem with that example is that the vendor's code is not meant to be placed in the <head>; it is meant to be placed in the <body> |
maybe i misunderstood you but fyi you can put script tags in the <body> - i always put the GA js code immediately before the </body> tag.
| 11:10 am on Mar 18, 2009 (gmt 0)|
Thanks to all for ideas. What I eventually did was to just use HttpWebRequest and HttpWebResponse to time the calls to the scripts. It's not perfect but I can now store in a database.
| 11:39 am on Mar 18, 2009 (gmt 0)|
|HttpWebRequest and HttpWebResponse |
| 1:08 pm on Mar 18, 2009 (gmt 0)|
Yes - ASP.NET