Browser benchmark test

[Crashoran]

Chrome scored 715 points for me while Firefox only scored 364.
Just installed Safari 4 and scored a 945 :)

Test your browsers here: http://service.futuremark.com/peacekeeper/index.action

[Davidtxs]

Firefox 758
Chrome 1158
IE yuck 223

[mjdmike]

IE 7.0 = 245
Firefox 3.0 = 452
Chrome = 1290
Safari 4.0 = 1622

All run from Windows Server 2008 x64

[srwatters]

Safari 4 - 1385
FireFox 3 - 332 (ouch!)

[Kalrog]

FF 3.0.10 : 277
Konqueror 4.2 : 440

[Imagebuffet]

I have a dozen Firefox browser windows open, plus an IE 7 window, plus Adobe PSE 5, plus a folder browser. I'm running this on a Dell Dimension E510 that I bought 3 or 4 years ago. Here are my test results:

Firefox 3.0.10: 254
Internet Explorer 7.0: 103

[Crashoran]

I think the test works best when only one browser is open with no additional tabs.

[Rson]

FireFox: 604
with many tabs, Couterstrike and other running.

[AndrewCCM]

XP 64bit, 8GB RAM
CPU: AMD Phenom II X4 920
GPU: NVIDIA GeForce 8600 GTS

Firefox 3: 580
Safari 4: 1455
IE 7 (64bit): 272

[Rson]

1618 on Safari......still playing CS

[ggeen]

Firefox 3.1.10, was the fifth tab in my browser, 374, on wireless.

thanks for sharing.

[Buddha]

for anyone interested in giving Firefox a little kick to speed it up, I've pasted some tips below. You can see the source for yourself. I've done what the tips say and it works.


PC Magazine Ziff Davis Media
The Independent Guide To Technology

Is Speed-Boosting Firefox Wrong?

When you live on the tech edge, especially in the online world, you take chances. Last column, for example, we discussed what happened when we accidentally violated Google's AdSense policy by asking users to click on our blog's ads. (Short answer: it made Google very, very angry and got a lot of our readers here up in arms as well.)

So…what if we told you that this week we found a way to boost browser performance in Firefox (and Mozilla) to a level you literally won't believe? The update takes two minutes, requires no add-ins or purchases, and blows your hair back when you surf even the most dog-slow Web sites.

The instructions are being posted as we speak on blogs all over the Internet. I saw them on ForeverGeek.com, but the exact text is posted on blog after blog, so my apologies to the original author. Here's the bottom line. To boost Firefox, simply do the following after launching your browser.

1. Type "about:config" into the address bar (no spaces) 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 at a time to a Web page. When you enable pipelining, the browser 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 tells the browser to 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 acting on received information.

Okay. That's all it takes. But now let's dig into the controversy that is foaming up discussion boards across the land. The term the hard core use for opening 30 server calls at one time is not pretty, but says it all: server raping. Taking up 30 simultaneous sessions is a major don't, since most servers bomb out at around 100. If four people using this tweak hit a page at the exact same time, they would crash everything, warned many a geek.

But not so, according to the other camp, who explain that pipelining is not about opening multiple sessions but simply changing how a single session pulls down information. The irony is that most developers gave up on pipelining after broadband became more widespread, and browsers today ship with this default set to "Off" or "False" to protect servers from throwing up bugs during a rapid pipeline burst.

We have to say that we have been using our jacked-up Firefox and have not crashed sites or been denied access because our browser's action was confused for a flood attack. We did see some bad code, though in third-party ads, mostly. Not in Google ads—and whatever you do, don't think we just told you to click on them!

So, give this a try, and report back in the discussion areas. We would love to hear from some hardcore pipeline guys and gals and figure this out once and for all. Is the hysteria just hype as we suspect, or is boosting Firefox technically bad for the Internet?
http://kb.mozillazine.org/Firefox_:_...config_Entries

Privacy.*
Name Type Meaning of Values
privacy. popups. disable_from_plugins Integer Sets limits on popups generated from plugins (e.g. Flash)
0: lets all popups through
1: limits their number to dom.popup_maximum (even with popup blocker disabled)
2: blocks popups from plugins

Whitelisted sites will still be able to open popups, regardless this setting.
privacy. popups. firstTime Boolean
True (default): The user has never hidden the popup blocker notification bar before, so show a dialog explaining the status bar icon
False: The user has been informed of the status bar icon

privacy. popups. policy Integer Determines the popup blocker behavior.
1: Allow popups
2: Reject popups
Note: Seems to be deprecated in favor of dom.disable_open_during_load

privacy. popups. showBrowserMessage Boolean
True (default): Display a message at the top of the browser window when a popup has been blocked
False: Display a status bar icon to indicate when a popup has been blocked



COLOR MANAGEMENT
Okay since Firefox 3 was released today, it is a color managed browser. But it is not on by default. Here is a add-on which enables it so you do not have to goto about:config and enable the color managed feature

https://addons.mozilla.org/en-US/firefox/addon/6891

If you do not want to login then just go to the developer's website
http://seanhayes.name/2008/06/16/color-management-04/

Here is a website to test and see if your browser is color managed.
http://www.color.org/version4html.xalter

And here is some info if you want to do it manually.
--To enable it you must set gfx.color_management.enabled to true (via about:config) and restart Firefox