Skip to content

Accelerate Firefox/Mozilla

January 27, 2005

forevergeek posted this list of Firefox (or Mozilla) mods. Some initial testing proved them to be quite effective, but as someone who runs websites, may I suggest you be a good netizen and set your maxrequests to something friendlier, like 10.

Here’s something for broadband people that will really speed Firefox up:

1.Type “about:config” into the address bar and hit return. Scroll down and look for the following entries:

network.http.pipelining network.http.proxy.pipelining network.http.pipelining.maxrequests

Normally the browser will make one request to a web page at a time. When you enable pipelining it will make several at once, which really speeds up page loading.

2. Alter the entries as follows:

Set “network.http.pipelining” to “true”

Set “network.http.proxy.pipelining” to “true”

Set “network.http.pipelining.maxrequests” to some number like 30. This means it will make 30 requests at once.

3. Lastly right-click anywhere and select New-> Integer. Name it “nglayout.initialpaint.delay” and set its value to “0”. This value is the amount of time the browser waits before it acts on information it receives.

If you’re using a broadband connection you’ll load pages MUCH faster now!

Advertisements

From → Interweb

5 Comments
  1. omg … this *so* rocks! thx bro.

  2. Yusuf Goolamabbas permalink

    You might want to read this irc exchange between gecko developers on the issues with enabling pipelining. Also changing paintdelay to 0 increases overall page load time
    http://christopher.aillon.org/blog/dev/mozilla/20050105-pipelining.html
    I encourage you to ping the Sun Beijing Mozilla team and ask them for more zen on Gecko optimisations. Maybe they can use Dtrace to wring some perf wins from Mozilla/Firefox.

  3. Anonymous permalink

    No offense to Rama, but these guys are dirtbags: “Normally the browser will make one request to a web page at a time. When you enable pipelining it will make several at once, which really speeds up page loading.” Yeah–for one person at the expense of everyone else. The HTTP specs and browsers specifically limit the number of connections they make to avoid overwhelming servers; this is not just a bandwidth issue. This hack, especially if even somewhat widely used, will seriously degrade the performance for the majority of users.

  4. jockey111 permalink

    One site that I was on got mad that I was using more than 3 simultaneous connections and cut me off.

  5. Anonymous permalink

    oh so hoooooooorny

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: