| |
|
Welcome to KnowledgeSutra - Dear Guest | |
Faster Page Loading...
Started by bigboss, Feb 14 2005 02:05 PM
19 replies to this topic
#1
Posted 14 February 2005 - 02:05 PM
This will make your pages load even faster.
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: (by double clicking them)
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. (I changed mine to 100, works great.)
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 recieves.
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: (by double clicking them)
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. (I changed mine to 100, works great.)
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 recieves.
#2
Posted 15 February 2005 - 03:33 PM
bigboss, on Feb 14 2005, 02:05 PM, said:
Normally the browser will make one request to a web page at a time. When you enable pipelining it will make several at once
Pipelining was introduced in 1996 with HTTP 1.1, and IE still doesn't understand it...
#5
Posted 03 March 2005 - 01:15 AM
Thank you for this information. I have been using Firefox for about a month and the pages would load so slow, but this helped a whole lot. Of course, do you think that 100 requests would affect the server the browser is trying to reach? That could potentially be a pain for someone if that is what is happening.
#6
Posted 03 March 2005 - 03:10 AM
solankyno1, on Feb 15 2005, 09:22 AM, said:
you're right, i have to admit the mods aren't doing they're fullest job, we'll try to work harder.
#10
Posted 09 October 2006 - 08:21 AM
I tried that, the settings that were on here already that were supposed to be changed to true were already true.. I havent done a lot of browsing since so i have no clue if its gonna be going any faster or not, i've got a t3 connection so i dont think i have a big problem with it to start with though.. hmm we'll see
Reply to this topic

1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users















