easy firefox tweaked

[Moebius]

Hey! thanks Moebius!

You're welcome.

[phoenixsansbury]

So what are the changes done after the fire-fox is tweaked and I would like to know more on this, I have seen this fire-fox tweaks in many websites and they all say that after tweaking the fire-fox the pages are opening faster then before.

[Admin-Amir]

Hello phoenixsansbury .

I have add one more part to the Guide that will give you one more option with the browser.
To use the swiftfox browser instead of FireFox:
posting.php?mode=edit&f=69&t=4763&p=51822#preview

[DaringSoule]

So what are the changes done after the fire-fox is tweaked and I would like to know more on this, I have seen this fire-fox tweaks in many websites and they all say that after tweaking the fire-fox the pages are opening faster then before.

here u go
Content.max.tokenizing.time
The maximum number of microseconds (1 second = 1,000,000 microseconds) between reflows. (Default: triple the value of content.notify.interval) Default = 360000, 0.36 seconds
suggest = 3 seconds

content.notify.backoffcount [integer]=200
After this number has been reached, the page will only reflow once it is finished downloading.
default = -1: unlimit

network.dnsCacheEntries[integer]=256
The number of DNS results to cache.
default = 20

network.dnsCacheExpiration[integer]=86400
The number of seconds to cache DNS results. (Default: 60)

network.ftp.idleConnectionTimeout[integer]=60
The number of seconds before the FTP connection times out. (Default: 300)

network.http.keep-alive.timeout[integer]=30
Amount of time in seconds to keep keep-alive connections alive. Default: 300 seconds.
HTTP keep-alive connections can be re-used for multiple requests, as opposed to non-keep-alive connections, which are limited to one request. Using keep-alive connections improves performance. This preference determines how long keep-alive connections are kept alive.

network.http.max-persistent-connections-per-proxy[integer]=24
the total number of HTTP keep-alive connections the application can make to it is limited by this preference. If more connections are needed, they are queued until a connection "slot" is available.
This preference takes values between 1 and 255 inclusive, directly corresponding to the maximum number of HTTP keep-alive connections the application can have open at once to the proxy server. (Minimo default: 2. Firefox 3: 8. All others default: 4.)

nglayout.initialpaint.delay [string]=0
Since the start of a web page normally doesn't have much useful information to display, Mozilla applications will wait a short interval before first rendering a page. This preference controls that interval.
The number of milliseconds to wait before first displaying the page. (Default: 250)

network.http.pipelining [boolean] = true
Attempt to use pipelining in HTTP 1.1 connections?
default: false
In HTTP 1.1, multiple requests can be sent before any responses are received. This is known as pipelining. Pipelining reduces network load and can reduce page loading times over high-latency connections.

network.http.pipelining.maxrequests[integer]=8
the maximum number of requests to pipeline at once when pipelining is enabled.
default: 3

network.http.max-connections[integer]=96
the maximum number of HTTP connections Mozilla can have open at once.
Users on slower connections may want to reduce this number to help prevent HTTP connection timeouts. Users on faster connections may want to increase it.
This integer preference takes values between 1 and 65535 inclusive.
default: 30

network.http.max-connections-per-server[integer]=32
The maximum number of connections of any type to a single server
1 and 255 inclusive
default: 15

network.http.max-persistent-connections-per-server[integer]=8
the maximum number of HTTP keep-alive connections the application can have open at once to a single server.
1 and 255 inclusive
default: 6

spellcheck your forms
Layout.spellcheckDefault = 1 (Enable spellchecker for multi-line controls)

Increase/Decrease History Undo Close Tab Limit ( Recently Closed Tabs )
browser.sessionstore.max_tabs_undo= #
Firefox 2.0 introduces a built-in Session Restore feature, allowing the user to continue browsing from where they left off if browser restarts. Since this feature lends itself well to keeping track of data about tabs and windows, it’s also used for re-opening recently closed tabs. This preference controls how many closed tabs are kept track of via the Session Restore service.
default: 10

this is a good share of the tweaks i have put into this... when i get time i will be researching 3.7

If you want to read the background of a key, please read http://kb.mozillazine.org/KEY_NAME, for example, http://kb.mozillazine.org/content.interrupt.parsing

[jshuford]

Thank you