I recently read an article about Firefox tweaks that would speed up page loading time by changing several settings in the about:config dialog. I knew those tweaks but decided to take a look if my settings were different from the ones mentioned in the article.
I found out – to my big surprise – that I was running Firefox with the default settings and not the tweaked settings. I had the feeling that Firefox was running slower than before after the latest update but I was not able to determine the cause, until now that is.
I would suggest you take a look at the following settings as well and see if you are using Firefox with tweaked settings or the default ones. If the latter is the case I suppose you change the settings to the same values that I changed them to, again..
Type in about:config and filter the name network.http.pipelining. The default values are that network.http.pipelining is set to false and network.http.pipelining.maxrequests is set to 4.
If your settings are optimized network.http.pipelining should be set to true and network.http.pipelining.maxrequests to a value of 30, 32 or 34.
After that filter for browser.turbo.enabled. If no result comes up you don’t have that setting yet. Right-click the blank space and select New > Boolean from the menu. Name it browser.turbo.enabled and set it to true.
If you happen to make a mistake, e.g. create a String with the name browser.turbo.enabled, you can correct it by navigating to your Firefox profile folder and edit the prefs.js file by hand. Just search for the line and delete it. Close Firefox before you edit the file.
Related posts:
Tweak Firefox with about:configFirefox Search Tweaks
Firefox Memory Tweaks
Firefox Tweaks, Extensions and Optimizations
Two Firefox Sidebar Tweaks
Advanced Firefox Configuration Tips
Speed Up Firefox By Limiting The History
10 lesser known Firefox about:config parameters
7 Responses to “Check if you Firefox speed tweaks are still active”
Trackbacks/Pingbacks
-
[...] 原文链接。 I hope you enjoyed reading this post. You may now subscribe to my RSS Feed, scroll down to 留下评论 or get back to the homepage. I recommend Giganews, the ultimate P2P alternative: Read here why [...]
There’s no use in using anything higher than 8 in network.http.pipelining.maxrequests. See http://kb.mozillazine.org/Network.http.pipelining.maxrequests#Possible_values_and_their_effects
I concur,
All this FFox settings tweaking just strains servers.
Unless you’re using a really old version of Mozilla Suite (now Seamonkey), browser.turbo.enabled has no effect. On Mozilla it preloads some libraries when windows boot so the application itself seems to launch a bit quicker.
Firefox preloader / quickstart for windows:
https://sourceforge.net/projects/ffpreloader/
Yeah, setting it higher than 8 doesn’t do anything: http://egonitron.com/2007/05/25/the-truth-about-the-firefox-pipelining-trick/
Concur that setting higher than 8 in network.http.pipelining.maxrequests does indeed do the opposite and slow down access to sites instead so have it at 8 now and all back to normal.
Setting maxrequests higher then 8 will not slow you down, the reason is it will default to 8 if set higher even if it says 30.
Browser.turbo.enabled Is empty, It does nothing, it used to be a feature that would help open the browser faster, but for whatever reason, it became outdated and unnecessary. Creating it and/or Enabling it does nothing.
I’m so sick of people who don’t know what they are talking about displaying wrong info about this everywhere. This is a message to the internet… Get your facts strait or don’t bother.