Speed Up Your Firefox by Adjusting Your HTTP Pipelining
Mozilla Firefox is quite a useful, powerful and full-featured web browser for net users who don’t really like the Internet Explorer series. Developed by Mozilla Corporation, Firefox is quite commonly used by net users nowadays. It features all the useful tools to facilitate you on net browsing such as tabbed browsing, incremental find, Live Bookmarking, Pop-up blocking, spell checker, integrated Google search function, etc. Besides installing the necessary plug-in, net users can actually enhance and increase their Firefox browsing speed by changing the HTTP Pipeline.
HTTP Pipelining
Hypertext Transfer Protocol or HTTP is a request/response protocol used to transfer or convey information between clients and servers. In simple words, the client makes an HTTP request and the responding server (Origin Server) which stores the resources or information will respond to it. HTTP Pipelining is a technique in which multiple requests will be send out without waiting for the corresponding responses. By customizing the HTTP Pipelining in Firefox, it helps to speed up the browsing capability. The customizing process can be done step by step as follows: -
Run your Firefox. Type in “about:config” into the address bar and press Enter. Scroll down the page and look for “network.http.pipelining“, “network.http.proxy.pipelining” and “network.http.pipelining.maxrequests“. You can also use the filter bar to search for these three entries.
Double click “network.http.pipelining” and “network.http.proxy.pipelining”. The “False” value will automatically change to “True” Value.
Double click “network.http.pipelining.maxrequests”, change the integer value in the pop-up window to 30. By entering 30, this means it will make 30 requests at once to the responding server.
Finally, just select any of the browsers and do a right-click. Select “New” followed by “Integer”. There is a small pop-up box which requires you to enter the preference name. Just type in “nglayout.initialpaint.delay” and set its value to “0″ in a subsequent pop-up box. This signifies to the browser to act immediately on the information it receives without waiting for any lapse of time.
Your Firefox browser will be much faster after you have made the aforesaid.
Related Articles
- How to Enable TraceMonkey JavaScript Engine in Firefox 3.1 to Speed Up Web Browsing Response Time
- Speed Up Copy and Paste Process With AutoCopy Firefox Plugin
- Change the Position of FireFox Tabs Close Button (or Revert Back to FireFox 1.5 Style at the End of Tab Strip)
- Firefox Tips: Refresh Firefox Webpage Content Without Clearing Cache & Disable Automatic File Scanning after File Download
- Firefox Prompts Users to Update the Latest Firefox 3.0.1
- Tweak (Increase or Change) Maximum Simultaneous HTTP and Downloads Connections to Web Server
- Manage Firefox Add-ons Via Firefox Add-on Collections
- Protect Firefox Password Manager Saved Passwords for Sites
- Firefox Unresponsive Script: Increase JavaScript Execution Waiting Time
- How to Resize Toolbars and Page Content in Firefox 3
Entries (RSS)
June 27th, 2009 11:45
Thanks a lot!! its working
February 23rd, 2009 02:13
i would murder you if you tried 30 connections at once to my server
February 9th, 2009 20:47
nice
January 22nd, 2009 13:26
Thanks!!!
Its Working…
September 13th, 2008 08:57
Thank you a lot
September 9th, 2008 13:40
[...] i used to throttle my mozilla, when its 2.0, am looking for new ways to do the same to 3.0 goodluck speed up your firefox by adjusting your http pipelining
June 22nd, 2008 18:44
[...] I’m into a new billing period lol. The pages are loading much faster but only after I did a little tweak with [...]
April 26th, 2008 23:52
Thankz Man!!!
March 11th, 2008 22:13
[...] [firefox] – 造成cpu100%問題 Windows 的 IE 基本上如非必要， 它已經不認識我了， 我也對它很陌生， 而現在我的好朋友是 fixfox 但近來好朋友有時多問它幾個問題(多開幾個瀏覽器) 它就給我鬧脾氣， 害我的cpu總是常上衝到100% 最後沒辦法只要找一個能夠滅火的方式… Speed Up Your Firefox by Adjusting Your HTTP Pipelining [...]
October 31st, 2007 14:21
…edit to correct…“it’s not a bad idea to get a screen-cap/print-out of this page for the original set-up before beginning… should read get a screen cap of when you open FF to mod before you change to new.
October 31st, 2007 14:14
Interesting comment, Henrik.
Are you suggesting not to do this @ all, or would adding a different value be the way to go? If so, would you care to fill in the newbz (me)?
Or can this step be omitted?
In any event, I’m sure it’s not a bad idea to get a screen-cap/print-out of this page for the original set-up before beginning should something go wrong.
I’m still N00b enough to be well acquainted w/ uninstall/reinstall/update pretty much sucks @$$.
October 17th, 2007 16:04
Using a value of 0 for nglayout.initialpaint.delay isn’t a good idea. In such a case Gecko will repaint the viewport multiple times until the whole site is finally loaded. That can result in a higher cpu usage as without adding/modifying this preference.
October 17th, 2007 12:27
Thank you.
October 17th, 2007 06:53
Cool Tip — Faster is better !!!
October 17th, 2007 05:34
[...] This is from MyDigitalLife: [...]