I don’t know but after some version updates suddenly, I started feeling that Firefox is much slowed down and also being heavy on resources. In reality, no matter what you do your Internet Speeds will depend upon the ISP (Internet Service Provider for e.g. Airtel, BSNL, Vodafone etc). Then your hardware like Modem, Router and lastly; very little on your browsers and other things.
However, there are something are important from Browser point of view. Like response time, Acid Test, First Run and Second Run memory usage etc. The most important is Response time. When you enter an URL and hit enter it takes sometime for browser to connect, resolve and start loading the webpage from server. If the response time just before this period is very high, then you will end up showing No Page to Display etc. Yeah! Sometime server may also not respond; it happens in both cases. You can make your Browser lighter and faster here with less Response times and faster page processing.
Here is the method.
I am hoping that you already have Firefox, or you haven’t been reading this. 🙂
1. Open your browser and type “about:config” in URL space (yeah Address Bar). Press Enter. A warning will appear. Just select ‘I will be careful’. (Lol! They don’t want us to Tweak It)
2. Now press Ctrl+F and find Network.http.keep-alive. (what? You didn’t know that you can search a inside a webpage? Man! You gotta be kidding!). Now, check the value of this entity. Double click and set it to TRUE. If it’s already TRUE; leave it.
3. Now there is other entry called Network.http.version. You must change it to 1.1; if you don’t wanna crash your browser. (Or you can leave it, if you hate Firefox too much…)
4. Next is, Network.http.pipelining. Turn it to TRUE from FALSE.
5. Just below that you will find Network.http.proxy.pipelining. Set these value to TRUE.
6. Lastly, Network.http.pipelining.maxrequests must be set to 8. It sets the Max Value for Requests.
7. Now these one is good one. Right-click anywhere (but not on any Value or Key, please) and select New. There you can make some new things. Don’t go after everything we just need an INTEGER. Create one and rename it to nglayout.initialpaint.delay. Now give it a value of 0 (that’s a ZERO not ‘O’). It will set time for browser to wait before it shows you the information it receives.
Little changes for BroadBand users:
Follow everything as it is including the INTEGER step but for Network.http.pipelining.maxrequests, you can set value to 30. Oh.. Come on, you are a broadband user, it can handle that much.
However, I still feel that Firefox can’t beat Chrome at any point. I was a fan of Firefox from years but after just trying Chrome’s latest version and watching Benchmarks, I said Man! This is what I need.
So you can consider that. Have fun!