I have IE9 with all updates running on Win7 64bit with all updates.
Some webpages are very slow in loading (up to 1.5-2 minutes on some).
I checked the Add-ons and disabled those that I was not too sure about
(but kept the ones from Microsoft, Adobe, Oracle & Symantec as I have
products running from them). Is there anything else I can look at to
determine why the sites are so slow in loading? One you can check if
you like is
http://chevronfcu.org/Pages/CFCULandingPage.aspx.
Let me know any thoughts that might help or if you might need
additional info to reply.
FYI, I will also post this note on the InternetExplorer Newsgroup, so
you might see it there as well.
Thanks for any insights.
charliec
Wireshark captured 1.1MB total for the above named web page
(that's the size of the capture file). That doesn't mean there
was a total of 1.1MB of packets or anything. That's just to establish
an upper limit on content. There were around 1400 packets or so total.
First response from the server, was at nine seconds after T=0. All
the activity was between T=9 seconds and T=20 seconds.
Part way through, I started seeing "TCP Dup Ack" in Wireshark
(that degrades bandwidth). That happens with a lot of sites,
and is all part of the TCP protocol's ability to deal with
issues for you. There could be ten hops between you and the
server, so the packets "travel a tortured path".
I "stopped trace" after about 20 seconds, so whatever the sequence was,
it was all over in 20 seconds.
Note that a server may respond differently to each client loading
the page. Not the same download packets result from using IE9 versus
Firefox. In some cases, if you use an old enough browser, the site
doesn't even render the page, and instead puts up a warning dialog
that the "browser is too old". So it's not like my test is definitive
or anything. I used Firefox or Seamonkey for my tests, and didn't see
anything out of the ordinary.
Try Wireshark, and see what you can find.
http://en.wikipedia.org/wiki/Wireshark
Note - depending on the OS, Wireshark needs to be run as administrator.
(It would be the WinPCAP that runs as admin, rather than the main program.
Admin is needed to access the network interface, which is what the separate
WinPCAP does.) At one time, this would only have been a problem for a
Unix user, but Windows is catching up to the "being an inconvenient OS"
part :-( So if your attempts to run it aren't completely successful,
it's likely to be a permissions problem. Older OSes might be less
of a problem - but modern versions of Wireshark, no longer run on
older OSes, and without a release note stating which version to
use with which OS, you end up playing "version roulette". I had to
do that, when working on someone else's computer a couple weeks
ago. Try one version after another, to get it to run.
Paul
