182FF with cup packs
I'm having an issue tracking down an issue for a client.
They claim that HTTP browsing performace is rubbish through their firewall. Every test I have done seems to show no issues with their firewall, yet I still see anything from a 1sec to a 10 second delay when someone hits enter in their browser.
I can't see any massive gaps in responses from packet captures, so I'm pretty stumped.
So what I need is some sort of app where I can stick in a URL and it will breakdown the amount of time that it takes for each step of the connection process, so it will tell me how long the DNS lookup took, how long the initial 3 way handshake takes, how long for the first HTTP response and then how long it takes for the actual webpage to load.
I'm sure that such a thing exists out there somewhere, but my Google-Fu is failing me :dapprove:.
I would also like it if this took was also proxy capable so I can test through their proxy as well (as I think that the likely cause is here)
Preferably running under windows (as the client is a windows only place, the only *nix device is the firewalls themselves (well, IPSO actually, but close enough) and I don't particularly want to run it on the firewalls.
They claim that HTTP browsing performace is rubbish through their firewall. Every test I have done seems to show no issues with their firewall, yet I still see anything from a 1sec to a 10 second delay when someone hits enter in their browser.
I can't see any massive gaps in responses from packet captures, so I'm pretty stumped.
So what I need is some sort of app where I can stick in a URL and it will breakdown the amount of time that it takes for each step of the connection process, so it will tell me how long the DNS lookup took, how long the initial 3 way handshake takes, how long for the first HTTP response and then how long it takes for the actual webpage to load.
I'm sure that such a thing exists out there somewhere, but my Google-Fu is failing me :dapprove:.
I would also like it if this took was also proxy capable so I can test through their proxy as well (as I think that the likely cause is here)
Preferably running under windows (as the client is a windows only place, the only *nix device is the firewalls themselves (well, IPSO actually, but close enough) and I don't particularly want to run it on the firewalls.