QUOTE(jolmy @ Jun 6 2008, 09:43 PM)
it's not compatible. You may want to force it to work with the Nightly Tester Tool Addon.
Otherwise, you can always go to about:config and make changes to your settings for the following:
network.http.max-persistent-connections-per-proxy
network.http.max-persistent-connections-per-server
network.http.pipelining
network.http.pipelining.maxrequests
network.http.proxy.pipelining
For more information & details, you can check this out
:-
QUOTE
network.http.max-connections [Integer] (48) - This setting determines how many simultaneous HTTP connections can be made by Firefox. The default is already 24, however for most people on moderate to fast Internet connections you can try raising this to a value like 48 or even 96 to allow for more open connections, thereby speeding up browsing multiple pages. The maximum is 65535, but remember that by raising this setting you are only raising the maximum possible number of connections. You aren't forcing Firefox to increase the actual number of connections it makes every time; if your system actually attempted to force 300 connections to open at once for example it would likely slow down to a crawl.
network.http.max-connections-per-server [Integer] (16) - This setting determines how many simultaneous connections can be made to a single server. The default is 8, however you can increase the value for broadband connections to something like 16 or 32 to attempt to increase browsing speed. The maximum is 255, however note that raising this setting to a high value (in conjunction with a high value for the network.http.max-persistent-connections-per-.* settings below) may be construed as a DDoS (Distributed Denial of Service) attack by some servers and your connection may be refused or even permanently banned. I strongly suggest that you keep this value sane. Simply increasing the number of connections to a server doesn't necessarily make things any faster, and indeed if every Firefox user does this then overall most sites will become slower.
network.http.max-persistent-connections-per-proxy [Integer] (8) - If you are connected to a proxy, this setting determines how many connections to keep alive at any time. The default is 4, however you can attempt a higher value such as 8 to improve browser speed. As mentioned in the settings above, raising this to a very high value will put additional stress on the proxy server and may ultimately result in slower browsing for everyone on the proxy and/or a refused connection.
network.http.max-persistent-connections-per-server [Integer] (8) - If you are not connected to a proxy, this setting determines how many connections to a single server to keep alive at any time. The default is 2, however you can attempt a higher value such as 8 to improve browsing efficiency. The maximum possible is 255, and as mentioned in the settings above, raising this to a very high value will put stress on the particular websites you are connected to and will either result in a refused connection, or slower response times from the web page for every person trying to connect to it. Do not raise this value to one which is very high as it is inconsiderate and counter-productive if everyone does so.
network.http.pipelining [Boolean] (True) - If set to True, this setting uses the HTTP Pipelining feature supported by some servers and proxies. This can improve browsing speeds, however because the feature is not supported by all servers you may experience problems on some sites with it enabled. I recommend setting this to True and only disabling it if you experience problems such as refused connections or unusual behavior.
network.http.pipelining.maxrequests [Integer] (8) - This setting determines the maximum number of requests to send when using the HTTP Pipelining feature (see above). The default is 4, and the maximum possible is 8 (higher values are ignored), while a value of 1 disables pipelining. I recommend setting this to 8 and only reducing it back to 4 if you experience any problems with the Pipelining feature.
network.http.proxy.pipelining [Boolean] (True) - If set to True, this setting enables the HTTP Pipelining feature (see network.http.pipelining above) for proxy servers. This can improve browsing speeds, however because the feature is not supported by all proxies you may experience problems. I recommend setting this to True and only disabling it if you experience such problems as refused connections, longer page loading times, or unusual behavior. Note that network.http.proxy.keep-alive must be set to true for this to work.
network.http.redirection-limit [Integer] - This setting determines how many consecutive redirects Firefox will accept. For example if you click on an outdated link to a particular site, once arriving there you may be automatically redirected to the new address for that site. That would be one redirect. If you want to block sites which spam multiple automatic redirects (usually malicious sites), you can lower this value to 10 for example, or even less. I don't recommend disabling automatic redirection (i.e setting this to 0) as many sites use legitimate redirects, such as most Internet forums after you have posted a message. I also don't recommend raising this limit above 20.
network.prefetch-next [Boolean] (False) - This setting determines whether to use a Firefox feature called Link Prefetching. See the Neat Stuff & Conclusion section for a practical example, and why you may want to set this preference to False.
nglayout.initialpaint.delay [Integer] *Create - This setting determines how many milliseconds Firefox should wait before it starts to display the page contents. This brief delay allows Firefox to load and arrange the various page components as correctly as possible. The default is 250 milliseconds which isn't very long, but you can try setting this to 0 to see if it improves the responsive feel of Firefox at the expense of slightly longer load times. Some users report faster overall page load times with the default value or even higher, so experiment to see which value suits your browsing habits, and if in doubt do not create or alter this setting.
This post has been edited by ash.ashie: Jun 6 2008, 10:39 PM 
May 17 2008, 05:00 AM, updated 18y ago
Quote
Love it
hoh, fariz... i'm on 3GB system le... 
, for some add-ons, it'll work... and some, they just won't work/functional weill
aik? unlike mine, i can't use the Tab Mix Plus 
It still can't beat the M$ IE dominance but it certainly have evolved into a very robust browser with the release of FF3 
0.0981sec
0.37
6 queries
GZIP Disabled