[Bug-wget] Using wget to measure web response times?

[ohaya]

Hi,

I'm new here, and I hope that this is the correct mailing list...

We are having response time problems, and I've been testing with wget to see if 
it would be helpful to try to determine what might be going on.

Some background:

Our application is running on WebLogic server, and it's a WebLogic Portal 
application.

We have this application deployed to several environments, and, response times 
for all of those environments, except for one of them, are fairly reasonable, 
typically ~3-5 seconds for the initial portal page to load into a browser.

However, on that one environment (unfortunately, our production environment) we 
are seeing very long response times for that same initial page to load, on the 
average, > 30 seconds.

I have been using wget, together with 'time', with the following command line 
parameters:

time wget --page-requisites --secure-protocol=SSLV3 --load-cookies cookies.txt 
--keep-session-cookies https://portal.foo.com/test/appmanager/portal/desktop

However, when I do this, on the same environment where we see > 30 seconds 
response to a browser, I get 'real' response times from the 'time' command of 
3-5 seconds.  That would SEEM to indicate that the browser is taking 28+ 
seconds to render the portal page.

So I was wondering:  Is this a valid test and use of wget?  And, am I 
interpreting the test results correctly?

Thanks,
Jim