Web Browser Grand Prix: Firefox 15, Safari 6, OS X Mountain Lion

DOM And CSS Performance

DOM

Mozilla's Dromaeo DOM tests began working with Chrome for Windows again just a few days before publication, so Acid3 is no longer needed as a substitute.

Safari takes the lead at 1140 runs per second. Chrome earns a respectable second-place finish with 840 runs per second, followed closely by Firefox with 746 runs per second. Opera finishes a distant last place with just 227 runs per second.

Chrome takes the lead in Windows 7, followed closely by Firefox. Opera finishes in third place, but with just half the runs per second as Firefox. IE9 places last at just 373 runs per second.

CSS

Composite Scoring

The CSS composite is the geometric mean of the CSS Stress Testing & Performance Profiling bookmarklet applied to both the CSS and CSS3 versions of the CSS3 Speed Test demo pages.

With no more Microsoft Maze Solver exposing its bugs, Firefox takes a strong lead on both operating systems. Chrome places second on both OS X and Windows, and is the only browser to do better in this test on OS X than Windows. Safari places third on OS X, while IE9 takes third on Windows. Opera places dead last on both operating systems, showing scores that are significantly slower than the third-place finishers.

Drill Down

The charts below contain the results of the CSS Stress Testing & Performance Profiling bookmarklet applied to the CSS and CSS3 versions of the CSS3 Speed Test.

CSS PerformanceCSS PerformanceCSS3 PerformanceCSS3 Performance

Opera's scores are relatively terrible, whether in Windows or OS X, CSS or CSS3. We're seeking another set of CSS/CSS3 demo pages to see if this results is valid, since previous CSS performance tests show Opera to be pretty average.

This thread is closed for comments
57 comments
    Your comment
  • glurg
    chrome ftw
  • Eggrenade
    It would be nice if I could view the additional charts with only one click, and not in a separate window.
  • lahawzel
    It's nice to see Chrome performing so well, but I'm still waiting on the Chrome equivalents of all the plugins I use in FF before I think about switching. The web just doesn't feel the same without them.

    (The nice popular ones like ABP, Lazarus, Greasemonkey all have equivalents; some lesser-used plugins like Rikaichan also have ports by now. Only a matter of time!)
  • bennaye
    chrome is absolutely deserving of the award. say what you will about the frequent patch releases touted as upgrades, chrome is a very good browser, as shown by this month's article. even on OSX there is only a small margin separating chrome and safari. but the one qualm i do have with chrome is the lack of add-ons compared to firefox. and i a lot of people share this concern. the add-ons do make the experience that much better.

    as always, a great read.
  • Would like to see this again after IE10 is released.
  • JOSHSKORN
    How about 64-bit Internet Explorer 9 vs Waterfox 15.0?
  • adamovera
    bennayechrome is absolutely deserving of the award. say what you will about the frequent patch releases touted as upgrades, chrome is a very good browser, as shown by this month's article. even on OSX there is only a small margin separating chrome and safari. but the one qualm i do have with chrome is the lack of add-ons compared to firefox. and i a lot of people share this concern. the add-ons do make the experience that much better.as always, a great read.

    All versions of Chrome hold up incredibly well cross-platform, if you look back at the two Linux WBGPs, it won there, too. Thanks for reading!
  • adamovera
    AdamsTaiwanWould like to see this again after IE10 is released.

    Absolutely, a Windows 8-based WBGP is already in the cards for October.
  • adamovera
    JOSHSKORNHow about 64-bit Internet Explorer 9 vs Waterfox 15.0?

    When we have more [official] stable 64-bit browsers, I'll definitely do a 64-bit WBGP - including versus their 32-bit counterparts.
  • I wish Tom's would fiddle around with the settings of these browsers for these tests. In every System Builder Marathon you overclock the builds, why not try and crank the most speed while ensuring better memory management out of the browser as well?

    Testing these browsers at stock doesn't reveal even an eighth of the picture.
  • nitrium
    So OSX is really just a LOT slower than Win7 generally for web browsing on the identical hardware. Is that right?
  • shahrooz
    it would be nice to have unreleased(Beta/Aurora/etc) versions of the browsers in benchmarks and scoring but only stable releases in the crowning so it will be fair. many users opt for beta releases of browsers including myself, I use Firefox nightly(18.0a1)

    btw great work adamovera keep it up man
  • adamovera
    boopyI wish Tom's would fiddle around with the settings of these browsers for these tests. In every System Builder Marathon you overclock the builds, why not try and crank the most speed while ensuring better memory management out of the browser as well?Testing these browsers at stock doesn't reveal even an eighth of the picture.

    Interesting idea, so basically a tweaked-out edition of the WBGP, where we use all the tools available to each browser for performance gains... That could work, but I gotta warn you that the next three WBGPs are already decided, so it would probably be real late in the year, or even next year before I could get to it.
  • adamovera
    nitriumSo OSX is really just a LOT slower than Win7 generally for web browsing on the identical hardware. Is that right?

    Nearly every performance benchmark there is points in that direction. This probably has a lot to do with how much time developers spend optimizing for Windows - after all, Windows holds 90+% of the desktop user base. However, it is interesting that the rift between Windows and OS X is far greater than between Windows and Linux for the core stuff like JS, CSS, DOM, page loads, etc. Plug-ins are another story, they're always much better on Windows than the other two platforms.
  • merikafyeah
    All things considered, IE9 does pretty well for a browser that's not even in the double-digits.
  • adamovera
    shahroozit would be nice to have unreleased(Beta/Aurora/etc) versions of the browsers in benchmarks and scoring but only stable releases in the crowning so it will be fair. many users opt for beta releases of browsers including myself, I use Firefox nightly(18.0a1)btw great work adamovera keep it up man

    The big problem with including the dev channel browsers is the amount of time it takes to produce the article (testing/charts/writing/editing/translating), combined with the tendency of the dev channel to constantly update. Before testing is even completed it's certain that something will update. TBH, the stable channels of Chrome and Firefox are a handful as it is. For example, for this article I had to test 8 browsers (4 on each OS), but I ended up testing 18+ due to OS X, Chrome, Firefox, Opera, Flash, and Java updates. Sorry, but I'm just not sure it's even doable in this format. Thanks for reading!
  • shahrooz
    adamoveraThe big problem with including the dev channel browsers is the amount of time it takes to produce the article (testing/charts/writing/editing/translating), combined with the tendency of the dev channel to constantly update. Before testing is even completed it's certain that something will update. TBH, the stable channels of Chrome and Firefox are a handful as it is. For example, for this article I had to test 8 browsers (4 on each OS), but I ended up testing 18+ due to OS X, Chrome, Firefox, Opera, Flash, and Java updates. Sorry, but I'm just not sure it's even doable in this format. Thanks for reading!

    well I wanted to include it in my comment myself but I forgot I wanted to say if the timing allows :)
  • Meaningless tests designed to generate clicks. All browsers are mature enough at this point in terms of performance. Even the lowly IE is OK. What matters is who is the browser working for, the user, or the mothership? And that's where FF is king. It's about treacherous, gimmicky commercial software made to push standards lock-in and data mining your information, versus free open source software that serves YOUR needs. And it's not only about the code being open either (Chrome). Get savvy on this stuff. Performance metrics are for FPS nerd teenagers.
  • JoeMomma
    Call me Old Skool but for me functionality and ease of use far outweigh speed.
    My computer is fast enough that it does not really mater what browser I choose.
    In my case, ease of use means that I can see what is going on.
    I decry the trend towards dumbing down the UI on every program I use.
    (I also refuse to call software 'Apps', to me an app is a mini-program on a phone.)
    I always turn on all menus, buttons and labels in WaterFox.

    BTW: Good point.
    Why don't you include WaterFox in your testing?
    It is the 64 bit version of FireFox and I am sure that in your speed tests it may do a little better.
  • azathoth
    Internet Explorer is starting to look pretty good in terms of speed.
  • srap
    Adam, IonMonkey will come in FF18, and not FF17. You may want to correct this on the last page.

    For those who want x64 browsers in the tests: x64 is always weaker than it's x32 counterpart, for all browsers: IE, FireFox, Opera. There are hardly a few things where x64 builds get better results.

    Edit 1: Also, those who want Waterfox and Palemoon in the tests: You do realise that these browsers would not get any better if the new standard supports, optimalisations, or fixes wouldn't land on Firefox itself? They would heavily depend on it in these tests. Running them on these tests would just give constant points following a simple formula like WF points=FF points + 0.5 points at *random test part* - 0.5 points at *another random test part*.

    Edit 2: corrected some sentences.
  • mayankleoboy1
    Nice well-rounded review!

    1. I noticed that a lot of your benchmarks are from the "IE testdrive page". Any particular reason why ? These tests are semi biased against firefox. In the sense that they use code that is bad on FF.

    2.I think "Pure Javascript" benchmarks should be devalued more. JS is fast enough in most cases, and pure JS is rarely used. Its always used along with DOM and other things.

    3. Opera is great, but the release12 has been full of bugs. IMO, the devs got in a hurry to release a new version.

    4.Considering that Safari does nor run on Windows, and that all othe browsers performance is half as good on OSX as on windows, IMO OSX as a platform for the next WBGP is meaningless. I would rather like Win VS Linux comparison.

    5. I was surprised to see that Chrome do so bad on the responsiveness test. It has a different process for each tab, and should have been smooth whatever the load. Did you redo the test to confirm ?
  • JoeMomma
    I do not like Chrome or IE because they pare down the interface so much that I can not figure out how to use them for anything but the most basic functions.
    I am no noob, but I find those programs INFURIATING!
    All programs need basic FILE EDIT VIEW menus,
    please do not alienate power users by playing hide the buttons.
    They are trying to avoid scaring off the computer illiterate,
    by not giving anybody the chance to read the instructions.

    IE fail.
    Chrome fail.
    Windows 8 fail.
    I am sure the others can do it also, but in Firefox I have figured out how to have a industry standard user interface.
  • mayankleoboy1
    And why cant you put the graphs/charts in the same nice format as the two "best of " images on the end page ? Opening those graphs/charts is a real pain the ass. I didnt even bother reading most of them, because its too much of a bother to open them.