CirTap
04-24-2005, 12:03 PM
Hi y'all,
since the advent of FF and TB 1.0 I made several friends of mine to successfully switch from their MS counterparts. However, one of them has complained about FF beeing extremely slow when browsing the web.
TB works like a charme and MSIE is "lightning fast" compared to what FF has to offer.
For that reason I don't think that the TCP/IP settings are messed up in general, but the prob's purely related to FF.
Because I'm the "PC guy" around, she asked (well, actually insisted <g>) for help, since it was my glory idea to make her use FF for "safety, useability and speed reasons" ... :blush: She saw the useability and safety benefits, but no speed. And I must agree: FF is painfully slow on this machine.
This has been true with both XP Home SP1 and also after updating to SP2 just recently.
Especially eBay and Amazon are a no-go, as well as other sites using resources from several sub-domains (like images or scripts) are a real PITA to browse with FF.
I checked all available IP and network settings, DNS cache and alike, and also "hacked" some settings via about:config in FF to make it use more connections and the "nglayout.initialpaint.delay" with no success (taken from some Mozdev-Forum IIRC).
Well, to be honest: except for the nglayout delay set to zero, the proposed networking/http settings had no great impact on my machine either, but I thought to give 'em a try. From what I see in the rest of about:config / networking.*, all values are the defaults -- like on my machine which runs fine.
There aren't any extensions installed either that could probably interfere with these settings.
My friend's computer uses an ISDN dial-up connection which is quiet fine in "speed" for any other application using TCP/IP (MSIE, TB, BitDefender etc. pp)
There's no difference if I disable BitDefender (incl. background services) so I don't think that its firewall or AV engine are causing this.
I mean the pages show up, but it takes over a minute for them to complete, compared to several seconds only in MSIE.
Also it doesn't matter if the dial-up is initiated by FF/MSIE or manually. In any situation MSIE beats FF in speed, which makes it hart for me to argue for FF.
I did or course a clean install of FF (1.0.1 at that time) after dumping the profile/app folder - no success.
Any ideas anyone?
Thanx.
Have fun,
CirTap
since the advent of FF and TB 1.0 I made several friends of mine to successfully switch from their MS counterparts. However, one of them has complained about FF beeing extremely slow when browsing the web.
TB works like a charme and MSIE is "lightning fast" compared to what FF has to offer.
For that reason I don't think that the TCP/IP settings are messed up in general, but the prob's purely related to FF.
Because I'm the "PC guy" around, she asked (well, actually insisted <g>) for help, since it was my glory idea to make her use FF for "safety, useability and speed reasons" ... :blush: She saw the useability and safety benefits, but no speed. And I must agree: FF is painfully slow on this machine.
This has been true with both XP Home SP1 and also after updating to SP2 just recently.
Especially eBay and Amazon are a no-go, as well as other sites using resources from several sub-domains (like images or scripts) are a real PITA to browse with FF.
I checked all available IP and network settings, DNS cache and alike, and also "hacked" some settings via about:config in FF to make it use more connections and the "nglayout.initialpaint.delay" with no success (taken from some Mozdev-Forum IIRC).
Well, to be honest: except for the nglayout delay set to zero, the proposed networking/http settings had no great impact on my machine either, but I thought to give 'em a try. From what I see in the rest of about:config / networking.*, all values are the defaults -- like on my machine which runs fine.
There aren't any extensions installed either that could probably interfere with these settings.
My friend's computer uses an ISDN dial-up connection which is quiet fine in "speed" for any other application using TCP/IP (MSIE, TB, BitDefender etc. pp)
There's no difference if I disable BitDefender (incl. background services) so I don't think that its firewall or AV engine are causing this.
I mean the pages show up, but it takes over a minute for them to complete, compared to several seconds only in MSIE.
Also it doesn't matter if the dial-up is initiated by FF/MSIE or manually. In any situation MSIE beats FF in speed, which makes it hart for me to argue for FF.
I did or course a clean install of FF (1.0.1 at that time) after dumping the profile/app folder - no success.
Any ideas anyone?
Thanx.
Have fun,
CirTap
