Mozilla firefox slow navigating

C

car

Registered User
Messages
1,397
On both my home and office network and only on this client. Up to 10 second delay displaying some pages, including google.ie.

I disabled all add-ons, bounced, same behaviour.

Im running 2.0.0.14 which is the latest version.

Im not going through any proxies.

Ive cleared cache & temp files.

Internet explorer has normal response times.

Microsoft defender and symantec antivirus (coporate version) didnt show anything untoward.

Anyone know what it could be?
 
Try using ProcessExplorer to see what Firefox thread is causing the delay and the Google for further info perhaps? Read the ProcessExplorer help if this is Greek to you. It's always possible that it's some interaction with some other driver or piece of software. For example I had to ditch Comodo firewall and switch to Sunbelt/Kerio Personal Firewall because one feature caused my touchpad driver to eat CPU cycles (a known problem which is discussed online).
 
Try upgrading to Firefox 3 Beta 5 - it's the stable release version of the full Firefox 3 to be released later this summer.

I've found it seriously faster than the latest version of Firefox 2, and not as buggy. Just be aware that it is only still a Beta version so full stability is not guaranteed.
 
Update on this, I searched mozilla support, and found this [broken link removed] which looked liked the same problem as mine. One of the solutions,

Go to about:config
See if either of these two are enabled (true):
network.http.pipelining
network.http.proxy.pipelining
If so, then disable them (double click) and reboot Firefox.
Click to expand...

Seems to have worked and normal speed has resumed.

I tweaked the mozilla settings on about:config a long time ago in line with many online suggestions for improving my browsers speed. However, pipelining can apparently cause a detrimental effect according to this [broken link removed]. A strange one as Ive made no changes to the config for a while now (years?) and this performance issue has only appeared in the last few days.
 
If your still interested I should add I tried playing with the network.http.pipelining.maxrequests parameter and reducing it to as low as 2 (as per that article suggests) but it made no improvement. Setting the other 2 params to false seems to be the only way to get it improve, now have 1-2 second page loads instead of 9-10 second which is what I had been getting.
 
You must log in or register to reply here.
Back
Top