Tweaking firefox to load faster

Discussion in 'other software & services' started by ejr, Mar 18, 2007.

Thread Status:
Not open for further replies.
  1. ejr

    ejr Registered Member

    Joined:
    Nov 19, 2005
    Posts:
    538
    I found this tip on-line but have not tried it. has anyone done the below to speed up firefox?


    forevergeek.com has a useful guide on speeding up firefox for broadband users. basically after getting to the hidden config settings you set the browser to request more data that it usually does.

    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!
     
  2. WSFuser

    WSFuser Registered Member

    Joined:
    Oct 7, 2004
    Posts:
    10,632
    Between FireTune and Tweak Network Settings I have enabled some of those tweaks.

    Also iirc, setting "network.http.pipelining.maxrequests" to anything higher than 8 does nothing.
     
  3. Mrkvonic

    Mrkvonic Linux Systems Expert

    Joined:
    May 9, 2005
    Posts:
    8,699
    Hello,
    I don't see any delay in speed.
    Besides, your ISP / firewall are much more important than other settings, regarding the browsing speed.
    Mrk
     
  4. ErikAlbert

    ErikAlbert Registered Member

    Joined:
    Jun 16, 2005
    Posts:
    9,455
    The very first opening of FF+6ext. takes 3 seconds, but after that less than 2 seconds.
    On my old computer it took much longer than 3 seconds, but I didn't care because FF is a very good browser and I can't do anything with speed.
    Why is speed so important for a browser, don't you read the webpages or do you read like Superman ?
     
  5. incursari

    incursari Registered Member

    Joined:
    May 16, 2004
    Posts:
    153
    Location:
    SG
    Rofl.
    Even without any tweak I found Firefox reasonably fast.
     
  6. Q Section

    Q Section Registered Member

    Joined:
    Feb 5, 2003
    Posts:
    771
    Location:
    Headquarters - London & Field Offices -Worldwide
    There is fast and then there is faster.
     
  7. argus tuft

    argus tuft Registered Member

    Joined:
    Sep 20, 2006
    Posts:
    280
    Location:
    Australia
    hi, It does make a noticeable difference, though I think it was mainly the nglayout.intialpaint.delay =0 what did it, not vital, but there you go...
    I actually misread the title, I read somewhere that you could speed up the loading of firefox, not the webpages, but the browser itself. It was something to do with compressing stuff I think, but not really sure. Does anyone know what I'm talking about?
     
  8. NGRhodes

    NGRhodes Registered Member

    Joined:
    Jun 23, 2003
    Posts:
    2,331
    Location:
    West Yorkshire, UK
    http://kb.mozillazine.org/Network.http.pipelining.maxrequests

    The max supported is only 8 (as mentioned by WSfuser) ... default is 4. Guideline from the http 1.1 specs is 2, but not concrete.

    The aim is to pack multiple http requests into one tcpip packet, obviously this reduces tcpip loads.

    Setting the value too high will cause the first request to take longer to process (as all requests need to be received in that pipeline before the first will commence) and can actually lead to slower browsing.
     
Loading...
Thread Status:
Not open for further replies.