for FF users...

[Wally Pipp]

simple but effective:

surf to "about:config" (in address bar)

find and modify the following:

1.) network.http.pipelining
2.) network.http.pipelining.firstrequest
3.) network.http.pipelining.maxrequests
4.) network.http.proxy.pipelining

set #3 to something like 32 and #1, #2 and #4 to true (by double clicking and changing the value).

Poof, speeds up your browser by a considerable amount.

Peruse the about:config for your own experimenting pleasure. Perhaps you'll find other hidden gems. Here is a comprehensive list of what each item is for.

[Merri]

I couldn't find the second one from my list of variables. I haven't yet noticed any difference, but I have loaded only two pages since doing the changes.

[Wally Pipp]

well, at least 25%-30% speed increase here. I kid you not.

[Merri]

Hmm, I probably have too much slowdown getting the data off from this site, so I can't see much difference (atleast not enough to be sure to say if it is faster or not). And the other site I tested is a damn fast one... I should have compared with some mid-speed site, but getting too lazy to do comparison. I'm happy with the speed I have

[NoteMe]

You can do the same by editing the user.js file. I have done this since verison 0.6....

[techgnome]

I've also found that setting network.http.request.max-start-delay to 0 speeds things up as well. At the very least it begins the rendering process sooner.


Tg

[NoteMe]

I've also found that setting network.http.request.max-start-delay to 0 speeds things up as well. At the very least it begins the rendering process sooner.


Tg

Only if you have a fast machine...it will slow things down if you have a slow machine.


And as a note to the first post. The pipelining, will only help on servers where pipelining is enabled. On other servers, it won't matter at all.


ØØ

[ice_531]

I must say ... "wow" and "i love you"

Well, it sped things up for me considerably...not that things went slow before, all though now im thinking it did