«

[nace]

OK. Here`s my contribution to the society:

I just learned this, and it works.

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 a maximum value of "8". But DO NOT set a number larger than that.

It`s about this thing called "pipelining". A fellow over there explained the thing:

Pipelining was possible in firefox since ages now, but somehow no one ever thought hat enabling it by default and puttin a value of 8 would help..
Btw, 30 is way too more and might break your connection to the website (weak packets dying) thus giving you slowdowns. Using 8 should be enough.

Btw, pipelining doesn't mean making more connections to a website, but mostly like cutting 1 connection in X parts.



I'll try to explain why 30 is a bit too much. This is explained in a childish way and doesn't exactly reflect reality:
Polobunny pipeling bedtime story for kids
First, firefox cuts the connection in 30, sending 30 scavenger bots retreive data.
Fact: Some scavenger bots are bigger, thus slower.
The smaller bots are returning fast to their base, while the bigger bots take more time.
Some scavenger bots can die of "horrible scavenger crash". The bot size has nothing to do with their crash, unless they are way too big (that almost never happens).
If too much big scavenger bots die (and all the bots returned) and the page isn't loaded completely, firefox will send 30 other bots. (doubling the process time)
Fact: When putting more bots they'll need to be faster or they'll die of being too old (again, this is a fictive representation)
Fact: A bot speeding at 100mph has more chance or crashing then a bot running at 50mph.
Scavenger bots all returned safely and has jillions of kids and lived happily.
End

So now that you understand pipelining, and if this firefox trick doesn't really help you, try to lower the pipelining.maxrequests number. If you rconnection is weak you'll get nothing if you put 30.
[/b]

A quote from polobunny - thanks dude.

__________________________________________________ ______________
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 are using a broadband connection (whatever this means ) you would load pages MUCH faster.

Thanks to Kazauya and polobunny.