News Glossary of Terms FAQs Polls Cool Links SpeedGuide Teams SG Premium Services SG Gear Store
Registry Tweaks Broadband Tools Downloads/Patches Broadband Hardware SG Ports Database Security Default Passwords User Stories
Broadband Routers Wireless Firewalls / VPNs Software Hardware User Reviews
Broadband Security Editorials General User Articles Quick Reference
Broadband Forums General Discussions
Advertising Awards Link to us Server Statistics Helping SG About
The Broadband Guide
search advanced
 forgot your password?

Firefox / IE Browser Tweaks

2005.10.04 07:56 by Philip
Tags: tweak, browser, pipelining, Registry, Internet Explorer, Firefox

Below, you will find browser-specific settings and registry entries to speed up both Firefox and Internet Explorer. The settings are generally intended for broadband internet connections, and can noticeably improve your web browsing experience.


Internet Explorer

According to the HTTP specs, only a limited number of simultaneous connections to web servers are allowed, while loading web pages. With today's broadband connections, it is beneficial to increase the number of concurrent connections to reduce page loading time. To increase the number of concurrent connections, add the following entries to the Windows Registry (the settings are not present by default in all Windows versions).

Under Windows 9x/ME/2k/XP

Navigate to Start > Run, type: regedit , find the following locations and add the DWORD values:

HKEY_USERS.DEFAULT\Software\Microsoft\Windows\CurrentVersion\Internet Settings
"MaxConnectionsPerServer"=dword:00000008 (not present by default, recommended: 8)

"MaxConnectionsPer1_0Server"=dword:00000008 (not present by default, recommended: 8)

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings
"MaxConnectionsPerServer"=dword:00000008 (not present by default, recommended: 8)
"MaxConnectionsPer1_0Server"=dword:00000008 (not present by default, recommended: 8)


Internet Explorer 8 under Windows Vista/7/2k8 Server

Click the Windows button, type: regedit, and navigate to:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\MAIN\FeatureControl\
(DWORD, default: 4, recommended: 8)
FEATURE_MAXCONNECTIONSPERSERVER\explorer.exe=8 (DWORD, default: 2, recommended: 8)

The above should also work if you create a DWORD "iexplore.exe=8" instead of using "explorer.exe=8" (Windows 7 has explorer.exe in the registry by default).
Keep in mnd that setting those values exceed the HTTP RFC specs. Increasing the number of concurrent connections over 10 may cause problems with some websites not completely loading, or dropping/retransmitting some requests. If you experience problems, just reduce the numbers to a lower value, or return the settings to the Windows defaults (4 and 2 concurrent connections).

The above parameters, and the web patch in the downloads section of the site work with Internet Explorer versions 4 and above.

Alternatively, to apply the above tweak for Windows 9x/XP/Me/2k, you can download a web patch (sguide_webtweak_2k) from the download section of the website.

While these entries improve web page loading considerably, there is some concern that they tend to strain webservers more (they increase bursts of concurrent requests), but have no effect on average throughput.

Q183110 - "WinInet Limits IE connections per server"
KB282402 - "How to configure Internet Explorer to download more than two files at one time" 



Pipelining requests

This setting is equivalent to the IE tweak above. It allows for more simultaneous connections to web servers. Note that the HTTP specs suggest for 4 concurrent connections. Setting this value to 10 allows for more web page components being downloaded at the same time, noticeably improving browsing. To appy the tweak, follow the simple instructions below:

1. In the address bar, type:  about:config
2. Locate and change the following values (by double-clicking on them):
network.http.max-connections = 24 (default is 24)
network.http.max-connections-per-server = 10 (default is 8)
network.http.max-persistent-connections-per-proxy = 8  (default is 4)
network.http.max-persistent-connections-per-server = 4 (default is 2)
network.http.pipelining = true (default is false)
network.http.pipelining.maxrequests = 10 ( default is 4)
network.http.proxy.pipelining  = true (default is false)

3. Optionally, you can also tweak the following settings:
content.notify.backoffcount  = 5
ui.submenuDelay = 0

Note: Setting the number of connections per server to a much higher number (over ~10) can cause web servers to drop some requests, resulting in incomplete pages, increased retransmissions, etc., so it is not recommended.


Reduce Initial Page Delay

By default, Firefox waits 0.25 seconds (250ms) before beginning to draw web pages. To reduce this initial delay, do the following:

- In the browser address bar, type: about:config
- Anywhere in the browser window, right-click and create: NEW > String
- Name the string:  nglayout.initialpaint.delay  (no spaces) and set its value to an integer between 0 and 50 (something sensible, in milliseconds).

Note: This setting is not present by default. When not present, Firefox waits 250 milliseconds before first displaying the page.


Use memory cache

Firefox has the ability to write cached files to RAM instead of the hard disk. This is much faster, and reduces hard disk drive wear. It is highly recommended if using SSD drives.

To change the cache location to RAM:

- open Firefox
- type about:config in the address bar, Enter
- double-click browser.cache.disk.enable to set the value to False
- right-click anywhere  and create "New" "Integer" values with the preference name "disk.cache.memory.capacity"
- set value to memory size in KB. Enter 32768 for 32MB, 65536 for 64MB, depending on your RAM size.
- also add  another setting named "browser.cache.memory.capacity" and set to the same number.
- restart Firefox


Advanced Firefox Settings

Below, you will find settings that may increase your perceived page loading time a bit further. Note that those are most likely best left at the default values. These settings generally do no exist under the Firefox about:config, and need to be created if you'd like to experiment with them.

content.interrupt.parsing - default/recommended is true. When true, parsing can be interrupted to process UI events.
content.max.tokenizing.time recommended value ~ 2250000. Defines maximum number of microseconds between reflows.
content.notify.interval - recommended value ~ 750000
content.notify.ontimer - recommended set to true. If so, doesn't reflow pages more often than the content.notify.interva timer.
content.switch.threshold - raising the value will make the browser more responsive at the expense of page load time.
browser.cache.memory.capacity - memory, in KB reserved for caching decoded images. Default varies with RAM



See this link for all Firefox about:config entries with descriptions and defaults. 

  User Reviews/Comments:
by philip - 2009.10.22 17:35
network.http.max-connections-per-server should not be more than 10, or you will run into issues with some web servers dropping some of the connections and not loading all page elements.
by chan - 2009.11.10 10:17
Mine Firefox 3.5.5, all the tweaks are working very well..i love it :) thanx speedguide
by dr0p0ut - 2009.11.21 02:59
this still rocks man... ^_^
by Quincy - 2009.11.25 12:27
content.notify.backoffcount = 5
ui.submenuDelay = 0

I have the latest 3.5.5 Firefox, but these values aren't shown. Are these values now absent from 3.5.5 release, or do I need to add them? If yes, would they be string, Integer or boolean?

by KHH - 2009.12.03 21:46
Will these settings affect the internet connection for other programs P2P, Torrent or messenger app???
by Philip - 2009.12.04 09:21
No, these are browser-specific tweaks; check out some of our other tweaking articles:
by TweakToTheBest - 2009.12.13 01:54
Very good Tweaks..

but the Advanced tweaks are they really necessary??

I applied tokenizing and time interval because they were already in the firefox.. and the others I need to confirm if it's safe
by Nibiru2008 - 2010.04.06 14:40
I leave the tweaks that are already higher than what is recommended for the newer versions of Firefox, such as v3.6.3

But some of the other suggested tweaks need to be more specific, such are they boolean, integer, etc.

The Firefox tweak section needs to be updated!

by Nibiru2008 - 2010.04.06 14:43
Optionally, you can also tweak the following settings:
content.notify.backoffcount = 5
ui.submenuDelay = 0

Are the above settings "string" or "integer" settings?

It's not stated what they should be. Please advise.
by Kriegar - 2010.05.27 14:23
Are there tweaks for Chrome yet?
by anonymous - 2010.07.16 20:26
I did this except the the ones in the advanced section and speed did not jump up that much, before I toke these steps download rate was 5.14 Mbps afterwords, it was 5.73 Mbps not very much.
by anonymous - 2010.09.24 19:22
For nglayout.initialpaint.... it's not a String, it has to be set as an Integer to work. The rest is good, the settings are all working well under XP and Win7.

I highly recommend using cFos, the best Internet Access Accelerator Software I ever met. Give it a try. Especially when your PC is directly connected to a Cable/DSL-Modem, you'll experience the difference.
by dnshah - 2011.03.25 04:44
I had been using FF since very long time and had always had very good experience with speeds it has using your guide. I always recommend FF to all my colleagues too.

The only major problem I face is the flash content viewing in FF which is very smooth in Dragon Browser (based on chrome), and it is sometimes faster than FF.

Recently I D/dled FF4, lets see what improvement is has in speed over previous versions.

Thanks over all to all the fans of FF and who readily help fellow FF'ians.

Keep it up & thumbs-up.
by D. W. Whitlock - 2011.07.23 21:52
Under your Firefox Browser tweaks; "Use Memory Cache".....I'd like to point out what appears to be an error;

The tweak shows to create a new preference: disk.cache.memory.capacity.
The Disk Cache has been disabled as per your tweaks, so this new value that you instruct to create appears to be incorrect.

The correct new value to be keyed in is: browser.cache.memory.capacity
set to 32768/32MB or 65536/64MB depending upon installed RAM.

By the way, I have used the TCP Optimizer with excellent results in my XP SP3 PC. Much snappier browsing.

by anonymous - 2011.08.27 13:35
Use memory cache

I'm afraid to do this tweak. If I will be letting FF use memory of my RAM wouldnt my RAM run slower then? If I do use this tweak, do I have the option to clear the RAM and put it back to normal? I'm using FF and my connection uses a USB Broadband. It is very slow and somethimes the page will be stuck and will only continue to load if I create a new tab(the page must be shy and needed me to go away before he can perform loading).
by anonymous - 2011.08.27 14:06
I downloaded the TCP Optimizer tool from here. After changng the settings to optimize, even after restarting, it goes back to default. I have administrator Privilages. What went wrong?
by Kriegar - 2012.10.25 18:50
by Kriegar - 2010.05.27 14:23
Are there tweaks for Chrome yet?
by anonymous - 2013.09.20 14:54
tip:you wont need more then one per l3 lane!
exemple:my cpu is an i5 2500k it has 12 lane on l3 and 8 lane on l2 so

max I need will be 12 !yes you can go higher but I suggest you don't go over your max l3

another exemple?mm take the intel 3820 ;this has a 20 way l3 so I wouldn't go past 20
by anonymous - 2014.04.02 22:59



Previous page (1) 1 | 2  comment print discuss top

exec. time: 0.01106 s
Copyright © 1998-2014 Speed Guide, Inc. All rights reserved.
Terms of Use | Privacy Policy