In what seems like forever ago, Microsoft’s Project Spartan was announced at the January 21st event in Redmond. This project kept the same rendering engine, Trident, and ECMAScript (JavaScript) engine, Chakra, as Internet Explorer, but stripped out much of the old code for backwards compatibility and moved forward with a push towards better performance and web standards support. I took a look at the performance of Project Spartan back in January when it could be enabled inside of Internet Explorer. The performance jump from Internet Explorer was extremely large, which was a good indication of what was to come.

Moving forward, Project Spartan got a name in Microsoft Edge back at Build. Over the last several months, Microsoft has put out quite a bit of information on the new features they are adding to Edge over on the Microsoft Edge Dev Blog including support for the latest ECMAScript standards, asm.js, SIMD support, and much more, all in an effort to bring their browser up to par for the modern web. It is likely not a surprise to many that Internet Explorer has had a tremendously long development cycle, especially compared to browsers like Chrome, and now Firefox, which are updated almost continuously. Some of that was due to the reliance of old features which were used in businesses, and Microsoft’s strong adoption in the enterprise has certainly held them back when it comes to large scale changes to the browser. Internet Explorer will be sticking around for those who need it (for example if you need ActiveX Controls on your page) but for the rest of Windows users, Microsoft Edge will now be the new default browser out of the box.

I’ve gone over some of this in the past, but it is likely worth a refresher anyway. Edge is bringing some new features such as integrated Cortana support built right into the browser to offer contextual search within a web page, or to offer answers to questions right in the address bar. It will also have support for annotation of web pages using a pen, mouse, or touch, and annotated pages can easily be shared. It has a reading view, a reading list, and while not available next week when Windows 10 ships, it will be gaining extension support very similar to Google Chrome to add even more functionality to the browser. This, combined with better web standards support, and a much quicker update cadence (this will have to be proven by Microsoft after release, but they have committed to quicker updates of Edge through the Windows Store) should result in a much better browsing experience than was available in Internet Explorer. If you have already switched from IE to Chrome, Firefox, or another browser, it may not be enough to sway you back – especially without extension support at launch – but it is at least worth a look. I’ll get more into my takes on Edge in our Windows 10 review.

For now, what we can examine is browser performance, not only because it is important, but because Microsoft has been making a lot of statements about improved performance of Edge as recently as last week when Windows 10 Build 10240 was released. When a company says a product is “blazing fast” it is a good idea to check it out to see if it actually lives up to that performance level.

Luckily I did run numbers in January on my desktop which features an Intel Core i7-860 processor. None of the hardware has changed, so I decided to re-run the tests with the latest version of all of the browsers. I kept the original numbers for IE 11, but I did re-run the tests to verify that they did not change.

Browser Performance - Core i7-860
Benchmark IE 11 (Jan) Spartan (Jan) Edge 20 (July) Chrome 40 (Jan) Chrome 43 (July) Firefox 35 (Jan) Firefox 39 (July)
Sunspider (lower is better) 149.7ms 144.6ms 133.4ms 260.9ms 247.5ms 220.1ms 234.6ms
Octane 2.0 (higher is better) 9861 17928 22278 17474 19407 16508 19012
Kraken 1.1 (lower is better) 3781.2ms 2077.5ms 1797.9ms 1992.8ms 1618.7ms 1760.4ms 1645.5ms
WebXPRT (higher is better) 913 1083 1132 1251 1443 1345 1529
Oort Online (higher is better) 1990 2170 5470 5370 7620 3900 7670*
HTML5Test (higher is better) 339 344 402 511 526 449 467

In every single instance, Microsoft Edge outperformed Project Spartan from back in January which is a good sign. It is the quickest browser in Google’s Octane 2.0 benchmark, and by a good margin. It is still the slowest in WebXPRT 2013 though. One of the biggest improvements though was the WebGL performance in the Oort Online benchmark, which went from terrible to good.

The other browsers have not been sitting idle though, and in that time they have also made gains in their performance. But the story is still a good one for Edge. It really is right up there with the rest of the browsers in terms of performance. It is quicker in some workloads, and slower in others, but generally performance should not be an issue. It still falls behind in the HTML5 test, but it has made big improvements there as well.

One thing that did pop out though is how much of a gain Firefox made in the WebGL test. Firefox went from middle of the pack to leading in the overall score, but if you noticed in the table I had to put an asterisk beside its score. The performance was quite good, but it achieved this performance by not rendering the scene correctly at all which contributed to its high score. In Oort Online’s benchmark, there is a snow scene, which Firefox rendered as blinking lights, and a rain scene, which was rendered as a couple of horizontal lines as seen in this screenshot.

Firefox Rain Rendering (Incorrect)

Edge Rain Rendering (Correct)

It is great to see Microsoft focusing on browser performance again, and especially not sitting idle since January, since the competition in this space has not been idle either. Only time will tell how Edge holds up over time, and if it continues to receive updates on a quicker cadence, but considering it is already at version 20.10240.16384.0, it does appear that Microsoft has jumped on the rapid release cycle with regards to their browser, which will only help them moving forward.

Comments Locked


View All Comments

  • Brett Howse - Wednesday, July 22, 2015 - link

    No this is just stock out of the box for all of the browsers.
  • redviper - Friday, July 24, 2015 - link

    Can you add the optimized versions also. I imagine most people would turn on almost all the optimizations in situations that require performance. Eventually I hope MS sets them on by default. They really make a big difference on weaker hardware and particular for touch (though thaws unrelated to performance).
  • mayankleoboy1 - Wednesday, July 22, 2015 - link

    Regarding the best score in Google Octane 2.0 , please read :

    tl;dr :

    Both Edge and Chrome have optimized their JavaScript engie to get higher score in this benchmark, while negatively affecting real world code.
  • redviper - Friday, July 24, 2015 - link

    As far as I can see that comment only applies to one test and doesn't apply to Edge at all.
  • ie5x - Wednesday, July 22, 2015 - link

    Did the Chrome and Firefox instances you tested had extensions installed? That may impact the scores.
  • Brett Howse - Wednesday, July 22, 2015 - link

    No extensions on either.
  • lilmoe - Wednesday, July 22, 2015 - link

    BTW Brett, you have very interesting results. I ran Oort on my laptop (FF and Edge) and I got very different results. It's Core i7 4702MQ, Intel HD 4600 (with a Radeon dedicated GPU, but the iGPU is used for browsers, and 16 GB of RAM.

    I got 2600 (15fps avg.) on FF and 6670 with Edge (35-50 fps). It's worth noticing that FF only managed a max of 70% GPU utilization while Edge was constantly above 90% (GPU-Z 0.8.4).

    What GPU were using again?
  • Brett Howse - Wednesday, July 22, 2015 - link

    GPU is a GTX 760, so clearly some work to do there to have Edge work better with NVIDIA, but it's the same GPU as I tested in January.
  • lilmoe - Wednesday, July 22, 2015 - link

    Well, the difference is too big... Do you have a system with an iGPU or an AMD? If so, why not make the same test on that other system and compare?
  • qlum - Wednesday, July 22, 2015 - link

    As a webdevoloper I am already seeing that for a part edge is behind Firefox / chrome in support of new html features though still ahead of Safari. However my experience tells me that Edge will be far further behind when the percentage of users finally drops low enough to ignore it in terms of support. Nowadays we are finally getting to the point where we can slowly start to ignore IE 9 / 10.

Log in

Don't have an account? Sign up now