script to measure page response times from client machines

I am running a web app on a large intranet. Some people are complaining of very bad load times on this app from their desktop machines, for others the response time is very good. the people complaining of the bad response times don't appear to have issues with other internal or external sites, just ours.

I believe its a network problem, but as I said its a large intranet with multiple large departments spanning an entire city, to get the engineers to prick up their ears and take a look at this issue I want to collect some data.

The users are not tech savvy and cannot assist other than to complain, sometimes loudly. What I would like to do is to place a small app on the users machines that access the website at various times during the day and logging the results. I envisaged a small script probably VBScript that can run quietly in the backgr开发者_开发知识库ound logging the load times of a page or number of selected pages from the site, then either posting the data to me or I get the user to post the log to me after say a week.

Does anyone know of such a script. or something close that I could modify to do what I want?

It would need to run on windows xp and not use anything that requires admin rights.

It might be good to do an audit of who is complaining of slow load times and what browser they are using. We recently had a similar problem and it turned out to be only the IE users complaining, since there's no net tab on the javascript version of firebug we couldn't track the site's performance... until we found fiddler: http://www.fiddler2.com/fiddler2/ - Fiddler is a Web Debugging Proxy which logs all HTTP(S) traffic between your computer and the Internet. Check it out, it might help you find where the slowdown is.

In the end it was decided it was too much effort and turned the problem over to system admin. as we were convinced it was a network issue and not related to the application server or browser.

They finally took us seriously enough and put a bypass on their caching proxy server. problem gone!

Moral of the story. sometimes you aren't to blame.

DC

I open a command prompt and type ping -t yahoo.com and let it run in the background forever. To note your response times, just look at the "time=ZZZms" number Anything greater than 40ms or so is bad. I reached this site looking for something better. Haven't found anything yet.