Trending

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

By

Important versions of Chrome and Firefox were released since our last installment, and though we're ready to leave Windows 7 behind, IE10 brings us back for one more round. Naturally, our exhaustive suite of benchmarks undergoes a massive update as well.

Chrome, Firefox, Internet Explorer, Opera

As you may have heard, Safari for Windows is no longer with us. Thus, the top five are now the top four. Before Opera becomes yet another Webkit browser and we're down to the top three, let's quickly check the vitals of today's four contenders.

Windows 8 Web Browser Grand Prix Competitors

Chrome

Vendor:GoogleDebut:9/02/2008Layout Engine:WebKitJavaScript Engine:V8Current Version:25Supported Platforms:Android, iOS, Linux, OS X, WindowsWBGP Championships:Eight (Win7: 5 / Win8: 1 / Linux: 2)Download Google Chrome

Firefox

Vendor:MozillaDebut:11/09/2004Layout Engine:Gecko 2.0JavaScript Engine:IonMonkeyCurrent Version:19Supported Platforms:Android, Linux, OS X, WindowsWBGP Championships:Three (Windows 7)Download Mozilla Firefox

Internet Explorer

Vendor:MicrosoftDebut:8/16/1995Layout Engine:TridentJavaScript Engine:ChakraCurrent Version:10Supported Platforms:Windows 7, Windows 8, Windows RTWBGP Championships:Two (Windows 7)Download Internet Explorer

Opera

Vendor:Opera SoftwareDebut:12/09/1996Layout Engine:PrestoJavaScript Engine:CarakanCurrent Version:12.14Supported Platforms:Android, iOS, Linux, OS X, WindowsWBGP Championships:Two (WinXP: 1 / Win7: 1)Download Opera

Let's take a quick look at the test setup and current benchmark suite before we get started.

84 Comments Comment from the forums
  • mayankleoboy1 14 March 2013 05:31
    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 14 March 2013 05:40
    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 14 March 2013 06:43
    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 14 March 2013 07:01
    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 14 March 2013 07:15
    @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 14 March 2013 07:30
    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 14 March 2013 07:32
    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 14 March 2013 07:51
    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 14 March 2013 07:54
    @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 14 March 2013 08:10
    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