Skip to main content

Which Web Browser Is Best Under Windows 8?

JavaScript And DOM Performance

JavaScript/DOM Composite Score

Since JavaScript and DOM are basically inseperable, and in order to further cut down on the performance-oriented weighting in our final score, we're combining the JavaScript and DOM test results into a single composite score.

Chrome takes a strong lead under Windows 8 and Windows 7. Firefox comes in second place on both versions of Windows, finishing a ways behind the leader, but even further ahead of the third-place finisher. Even though it places slightly lower than IE10 in JavaScript, Opera moves up to third place due to its far stronger DOM scores. IE takes last place on both platforms, although IE10 performs notably better than IE9.

JavaScript

The JavaScript composite score is the geometric mean of the results from RIABench JavaScript, FutureMark Peacekeeper, Mozilla Kraken, and Google's modified version of Apple SunSpider. Neither IE9 nor Opera 12.10 will complete Google Octane, so that test is excluded.

Chrome steals the show in JavaScript performance once again, and without any Google benchmarks backing it up. Firefox earns second place, a ways behind Google Chrome. IE10 takes third place on Windows 8, while IE9 finishes last in Windows 7. Opera loses to IE10, but still beats IE9, placing fourth on Windows 8 and third under Windows 7. All four browsers demonstrate improved JavaScript scores in Windows 8, with IE10 showing a 40% increase over IE9.

Drill Down

The charts below contain the individual results for each JavaScript performance benchmark. The single RIABench score that is factored into the JavaScript composite is derived from the geometric mean of all nine RIABench JavaScript tests.

Image 1 of 5

RIABench - Windows 8

Image 2 of 5

RIABench - Windows 7

Image 3 of 5

Peacekeeper

Image 4 of 5

Kraken

Image 5 of 5

SunSpider

IE10 shows the most remarkable improvements in the Kraken and SunSpider benchmarks, while RIABench and Peacekeeper only reflect a marginal improvement over IE9. Chrome is the hands-down winner, as it has been for nearly the entire lifespan of Google's browser.

Seeing as how Internet Explorer 10 doesn't take the JavaScript crown, and Opera has been relatively stagnant in this discipline lately, hopefully Mozilla's upcoming IonMonkey engine can truly give Chrome a run for its money.

DOM (Document Object Model)

We use the DOM Core subsection of Mozilla's Dromaeo DOM tests to represent DOM performance in our final scoring. The Dromaeo results are an average of two iterations.

Naturally, Chrome also takes the lead in DOM core performance, followed closely by Firefox. Opera trails far behind in third place, with IE bringing up the rear. Unlike the JavaScript numbers, the DOM scores do not favor either version of Windows.

  • mayankleoboy1
    1. Did you ensure that Opera has Hardware acceleration and WebGL enabled in about:config ? AFAIk, Opera does not enable HWA by default.

    2. I find the over-reliance on "Internet Explorer Test drive" benchmarks disturbing. Most use code that is inefficient and not used anywhere else on the web, making it quite theoretical.

    3. +1 for using Google Octane benchmark. Both google and mozilla agree that this is a good real-world benchmark.

    4. Addition of the "Maze solver" benchmark is disappointing.

    5. Why remove the subjective smoothness ? 95% of the time, subjective smoothness is what lures a person to use a specific browser. People use a browser, not run benchmarks on it all day. Subjectively, no browser can beat Google Chrome. Then comes Opera , Firefox and far lastly, IE10.
    Reply
  • mayankleoboy1
    Any technical reason why browser performs generally better in Win8 ? Even the 'WHQL' drivers from Nvidia and AMD arent quite mature for Win8.
    Games and applications did not show any improvement in Win8 over Win7.
    Reply
  • adamovera
    mayankleoboy11. Did you ensure that Opera has Hardware acceleration and WebGL enabled in about:config ? AFAIk, Opera does not enable HWA by default.2. I find the over-reliance on "Internet Explorer Test drive" benchmarks disturbing. Most use code that is inefficient and not used anywhere else on the web, making it quite theoretical.3. +1 for using Google Octane benchmark. Both google and mozilla agree that this is a good real-world benchmark.4. Addition of the "Maze solver" benchmark is disappointing.5. Why remove the subjective smoothness ? 95% of the time, subjective smoothness is what lures a person to use a specific browser. People use a browser, not run benchmarks on it all day. Subjectively, no browser can beat Google Chrome. Then comes Opera , Firefox and far lastly, IE10.1) We use fresh installs at default settings; Opera does not enable HWA by default.
    2) The only IETestDrive tests we use are Psychedelic Browsing and Maze Solver, and IE regularly loses to competitors on both.
    3) Octane was not used because it had issues with IE9 and Opera 12.10.
    4) We definitely need a new CSS test, but the only other options are outdated or on IETestDrive - unfortunately, Kaizoumark doesn't work with IE10.
    5) It's really difficult to see that kind of stuff on a modern test system, but I will say that Chrome and IE10 are about equal in that department, with Firefox and Opera noticeably more choppy right at the beginning of the 40-tab load.
    Reply
  • adamovera
    mayankleoboy1Any technical reason why browser performs generally better in Win8 ? Even the 'WHQL' drivers from Nvidia and AMD arent quite mature for Win8.Games and applications did not show any improvement in Win8 over Win7.Not sure, the Nvidia drivers used were the same version on both OSes.
    Reply
  • And we're also passing the torch from Windows 7 to Windows 8.
    We are going to miss you on Web Browser Grand Prix, Windows 7
    Reply
  • mayankleoboy1
    10447137 said:
    1) We use fresh installs at default settings; Opera does not enable HWA by default.
    2) The only IETestDrive tests we use are Psychedelic Browsing and Maze Solver, and IE regularly loses to competitors on both.
    3) Octane was not used because it had issues with IE9 and Opera 12.10.
    4) We definitely need a new CSS test, but the only other options are outdated or on IETestDrive - unfortunately, Kaizoumark doesn't work with IE10.
    5) It's really difficult to see that kind of stuff on a modern test system, but I will say that Chrome and IE10 are about equal in that department, with Firefox and Opera noticeably more choppy right at the beginning of the 40-tab load.


    1. IMHO, enabling these settings would have made Opera more competitive and this article fairer.

    3. Whoops, misread that. But this is a good benchmark. Robohornet and robohornet pro are complete jokes.
    4. Just exclude the maze solver. Its bad coding, as any web developer can tell you.
    5. Thats exactly what i'm saying. This needs to be factored in the overall score. You want the browser UI to always remain smooth. UI choppiness is unacceptable and sloppy coding. We are not living in the 90's anymore.


    The one thing i dislike in Chrome is the memory bloat when opening many tabs. In the 40tab test, FF uses 600 MB. Chrome uses 1600MB :O. That is probably an iverhead of using separate processes for each tab. That is excellent for smoothness and UI fluidity. But shameful for memory consumption. I guess devs need to find a middle path.
    Reply
  • mayankleoboy1
    Both 'mozilla kraken' and 'Google sunspider' benchmarks need to be retired . They are old, and all the major browsers have optimizations to score better on them.
    Plus, they heavily test features that are not used anywhere else on teh web.

    Example : Sunspider makes a billion manipulations to the the "date" variable. Mozilla did not have any optimization for this. So it scored poorly on Sunspider. After numerous 'review sites' started using sunspider to test FF Vs Chrome, mozilla developers had to reluctantly add the same optimisation (which is basically a separate buffer to store the date). Of course, nowhere on the web is the date variable used in this manner. So its optimization for an artificial test.
    Reply
  • wilem_WAR246810
    "The King Is Dead, Long Live The King!" am I the only one who thought of Megadeth?
    Reply
  • deepblue08
    mayankleoboy1Any technical reason why browser performs generally better in Win8 ? Even the 'WHQL' drivers from Nvidia and AMD arent quite mature for Win8.Games and applications did not show any improvement in Win8 over Win7.
    As far as I heard there are significant under-the-hood improvements in Win8, in terms of memory efficiency and multi-core usage.
    Reply
  • epileptic
    Is it Opera x64 or x86? I remember having tested Opera 12 and the startup was very slow. I'm still using 11.64 atm. The only thing keeping me from moving to Firefox is how sluggish the UI feels... I'd also have to find a new mail client. :/
    Reply