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

[Keisial]

address@hidden wrote:
> Hi All (Micah, Giuseppe, and Keisial),
>
> I did some further analysis/review. 
>
> As further background, the URL I was using was for initial page of a WebLogic 
> portal app.  
>
> Also, from reviewing the files that wget retrieved from my tests, there is 
> quite a bit of Javascript, and, in particular this uses Dojo, so given what 
> was said earlier, i.e., that wget won't 'follow' the Javascript, it sounds 
> like wget may not be the best tool for this.  I did do some testing 
> yesterday/last night, where I disabled Javascript on the browser (IE), and 
> when I did that, I was able to get to that initial page in about 5 secs.
>
> Also as mentioned earlier, the one environment where we're seeing the longer 
> response times is our production network, and it's locked down, and, in 
> particular, we don't have tcpdump or similar tools available.
>
> So, at this point, I'm not sure what the next step is.  We're also now 
> allowed to have things like Firebug, which makes this whole thing more 
> difficult :(...
>
> I appreciate the comments!
>
> Thanks again,
> Jim
>   

You can run the packet logger in the test machine (you may prefer the
graphical Wireshark, though) to see what is the browser requesting and
how is it being answered.
You can also go requesting each subfile from wget which should be enough
in your case to pinpoint the issue, although there are also extensions
in browsers designed to show you the request path and delays in loading.