Quote:
Originally Posted by leon
Browser you say, I use Seamonky, seems to work quite well.
|
oooooooooookkkkkkeee-dokey... SeaMonkey uses the Mozilla engine (same as FireFox) so I'm going to ask a few questions and we will see where it takes us...
Let's break the problem down into sections... I'm using FireFox, so SeaMonkey may be a little different. However, I've noticed that Mozilla products tend to standardize the interface. Note that some of your menus may be a little different, so hunt around.
If we can't actually solve the problem, I'll install SeaMonkey and have a play... so here goes.
Quote:
Originally Posted by Section 1
Potential problem with connection
Quote:
Originally Posted by Try This
Go to http://www.speedtest.net/ and test your connection speed. Post results here directly or link the results.
Believe it or not, IIS is a fairly basic website and does not require a lot of overhead, so even a relatively modest connection should be able to load a page quickly... To put this in context, the IIS home page is only 1.1MB (including images)...
|
|
Quote:
Originally Posted by Section 2
Potential cache is filled and SeaMonkey is having to delete old items every time a new one is loaded...
Quote:
Originally Posted by Try this
goto options, click on the Advanced tab, then network.
Look for something labeled "Offline Storage". There should be a "Clear Now" button. Click on that and the try IIS
|
|
Quote:
Originally Posted by Section 3
Your configuration for loading webpages is not optimized...
Quote:
Originally Posted by Try this
Open a tab for browsing and type "about:config". In the filter bar at the top, type "network" and hit enter.
Scroll through the list and look for the following and tell me what you have them set to. Just send the following and don't try to alter any of the other values, as some are co-dependent on others.
network-http-pipelining
network-http-pipelining.maxrequests
|
BTW: Mine are set to the following:
network-http-pipelining: True
network-http-pipelining.maxrequests: 30
|
OIC!