Web Browser Grand Prix: Chrome 25, Firefox 19, And IE10

Windows WBGP Winner's Circle

Before we crown a champion, let's see where the contenders stand in pure performance. The chart below only factors in the performance-based testing (startup time, page load time, JavaScript/DOM, HTML5, and HWA).

Wow. When we look strictly at the performance-oriented metrics, we almost have different winners for each version of Windows. While Chrome clearly takes the lead on Windows 7, Firefox almost scores a victory in Windows 8. IonMonkey narrowed the performance gap, just not quite enough. IE10 takes a distant third place under either OS, with IE9 in tow. Opera pitifully places last in performance testing, achieving one-third of the Chrome and Firefox scores.

Now we'll add efficiency, reliability, security, and standards conformance to the mix and see how the standings change. 

While it was a close race, Chrome's showing in all four of the remaining non-performance metrics was superior to Firefox, closing the deal. Firefox does place a very close second, especially in Windows 8, where it has an apparent advantage. In fact, looking at the performance index reveals that Firefox receives an even larger boost from the new version of Windows than IE10.

Speaking of, Microsoft's newest browser doesn't exactly shake the earth on either version of the company's ubiquitous OS, earning a mediocre third place. Opera and IE9 share last place, halving Chrome's score. It's hard to believe that the Norwegian browser went toe-to-toe with Google just a few short years ago. With version 12 a continuing disappointment, perhaps it's best that Opera join the ranks of Chrome clones.

Google Chrome remains the reigning Web Browser Grand Prix Champion for Windows (and Linux). Congratulations on the ninth WBGP victory!

TOPICS
  • mayankleoboy1
    1. I am assuming that IE9 was included just to show improvements in IE10, and IE9 will be retired in the next WBGP

    2. " Opera jumps on-board the Chromium bandwagon" is false. Opera is using Webkit rendering engine for rendering. We dont know what the Javascript engine and JIT compiler is going to be.

    3. On page4, in "the average wait time" , you are taking the Geometric Mean. I think that using values less than 1 in a geometric mean is skewing the results. Can you take a Arithmetic Mean, and check please ?

    4. Memory usage reporting of IE9 and IE10 is completely bogus. For some workloads, in TaskManager, IE10 is seen using about 300MB memory, while it is actually using around 3GB RAM ! :O . My 4GB RAM is completely used up, and disk-paging starts occuring.

    5. I am completely mystified why quite a few browsers do better in JS benchmarks on Windows8 . I can understand getting better scores in WebGL or HW acceleration tests (because of potential better Dx) , but JavaScript execution does not use Dx. Any ideas ?
    Reply
  • alidan
    i wish we could get some older browsers in here to to see the difference newerones make.

    i personally am still on ff10, memory is really the reason i use fire fox, along with chrome. i would love to see how older versions stack up to newer ones.
    Reply
  • bison88
    Opera is definitely lagging, but a I love it to death. Hope the switch to the Webkit platform gives them the motivation to start leading some of the boards again as it's still a great browser. The memory problem can get absurd sometimes and builds up fast. I have to say IE 10 has shocked me just toying around with it on Windows 7. The thing is smooth and fast, something I haven't seen since the days when it dethroned Netscape.
    Reply
  • adamovera
    mayankleoboy11. I am assuming that IE9 was included just to show improvements in IE10, and IE9 will be retired in the next WBGP2. " Opera jumps on-board the Chromium bandwagon" is false. Opera is using Webkit rendering engine for rendering. We dont know what the Javascript engine and JIT compiler is going to be.3. On page4, in "the average wait time" , you are taking the Geometric Mean. I think that using values less than 1 in a geometric mean is skewing the results. Can you take a Arithmetic Mean, and check please ?4. Memory usage reporting of IE9 and IE10 is completely bogus. For some workloads, in TaskManager, IE10 is seen using about 300MB memory, while it is actually using around 3GB RAM ! . My 4GB RAM is completely used up, and disk-paging starts occuring.5. I am completely mystified why quite a few browsers do better in JS benchmarks on Windows8 . I can understand getting better scores in WebGL or HW acceleration tests (because of potential better Dx) , but JavaScript execution does not use Dx. Any ideas ?1. Yup
    2. The press release mentioned "Chromium", so I'm assuming WebKit/V8.
    3. Yes, you're right! The last timers went by milliseconds, so that wasn't an issue - the replacement charts should appear soon. Good catch!
    4. It seems pretty reasonable to me, basically mirrors Chrome in this regard.
    5. Nope
    Reply
  • caspy7
    @mayankleoboy1
    #2, incorrect, they have said they're going with Chromium's V8.

    @alidan
    Mozilla saw the err of their ways and got after memory. The most recent version of Firefox should beat version 10 in both memory and performance. The last benchmarks I saw had it beating all the other browsers in memory usage as well. (In this article you can see a snapshot of this in the "40 tabs" graphic. Like many techies, this is more what my browsing looks like.)
    Reply
  • mayankleoboy1
    adamovera1. Yup2. The press release mentioned "Chromium", so I'm assuming WebKit/V8.3. Yes, you're right! The last timers went by milliseconds, so that wasn't an issue - the replacement charts should appear soon. Good catch!4. It seems pretty reasonable to me, basically mirrors Chrome in this regard.5. Nope
    #2 : I must have forgotten the release. Thanks for the correction.
    #4 : I am not saying that IE10 uses excessive memory. I am saying that the total memory used by all the ieexplorer processes in the task manager is incorrect. For some image heavy pages, total memory usage of IE as reported by task manager is about 300MB, but total system memory usage gets around 3GB!. So if you close IE10, system memory goes from 90% full to 50% full.
    Reply
  • slomo4sho
    I currently use Firefox, Chrome, and IE 10. They each have their own advantages. Thanks for the write up. When can be expect the Android browser round up?
    Reply
  • xintox
    Really? I thought you were better than that at Toms.
    The composite hardware acceleration scores is most likely the main reason why IE9/10 is so far behind Firefox and Chrome on performane. Yet, from what I can tell, this composite score is heavily influenced by the WebGL scores, which is exclusive to Chrome and Firefox.
    In that respect, MS has at some point stated that they do not even wish to support WebGL, as it represents a significant security risk, as it gives the browser close access to the computer hardware.
    Long story short, your methods of calculating performance scores heavily favors Chrome and Firefox as they are the only ones to implement support for WebGL.

    Additionally, I wish you would make it more clear how you arrive at your composite scores and of course the final Performance Index. How do you add numbers that are so varied in nature, without some method of normalizing the numbers?
    Reply
  • srap
    @adamovera
    I heard that Futuremark Peacekeeper is unreliable, it used to miscalculate it's own benchmarks and it's still a black box so it may still be buggy. Do you know anything specific about it?
    Reply
  • abbadon_34
    Nice to see IE9 AND IE10, as well as Win 7 AND Win8. But I am curious how the final scores were calculated, seeing how WebGL was only supported on 2 browsers, as well as how the other incompatible tests were scored. A 0 vs not including can make a good deal of difference.
    Reply