In our tests of Chrome, Edge, Firefox, IE and Opera, the worst web browser for Windows 10 was easy to spot: Internet Explorer 11. But the best choice? That depends.
By Steven J. Vaughan-Nichols for Networking | January 15, 2016 -- 13:14 GMT (05:14 PST)
On earlier versions of Windows, the best browser you can run today is clearly Google Chrome. But, what about Windows 10? There, it's a different story.
On Windows 10, it's not crystal clear what the best web browser is. It is, however, obvious what the worst one is: Internet Explorer 11.
sjvn
With Windows 10, you have another choice: Microsoft's replacement for Internet Explorer (IE), Edge. For now Edge is only available on Windows 10. Since Microsoft recently open-sourced ChakraCore, Edge web browser JavaScript engine, it' possible we may yet see Edge running on Windows 7, 8, and 8.1. Indeed, Microsoft is porting ChakraCore to Ubuntu Linux!
When last I looked at Windows 10's web browsers, I looked at a late beta in June 2015. Now, Windows 10 has been released and then massively upgraded. For my tests on this run, I used Windows 10, version 10586.63, the latest update as of mid-January 2016.
I ran these performance tests on an Asus CM6730. This desktop PC is powered by a third-generation 3.4Ghz Intel Core i7-3770 processor. This is supported by a Nvidia GeForce GT 620 graphics card. The PC also has 8 GBs of RAM and a one TeraByte hard drive.
On this system, besides the latest versions of Edge (25) and IE 11, I tested at the latest versions of the most popular desktop web browsers. These are Chrome 49, Firefox 43, and Opera 34. I didn't include Safari in this round-up because Apple no longer releases new major versions of Safari for Windows. Apple does, however, still support Safari on Windows with security updates.
Here's how well each browser did on the respective benchmarks.
Jetsteam 1.1: This JavaScript benchmark builds on the foundation of the no longer supported SunSpider, It combines several JavaScript benchmarks to report a single score that balances them using geometric mean. Jetstream includes benchmarks from the SunSpider 1.0.2 and Octane 2 JavaScript benchmark suites. This test suite also includes benchmarks from the LLVM compiler open-source project, compiled to JavaScript using Emscripten 1.13. It also includes a benchmark based on the Apache Harmony open-source project's HashMap and a port of the Cdx realtime Java benchmark, hand-translated to JavaScript. Larger scores are better on this benchmark.
While Chrome dominated on older versions of Windows, Edge took first place on JetStream with a score of 231.78. A good distance behind came Chrome with 196.86; Opera with 186.29; Firefox with 182.46, and, way in the back, IE with 133.07.
Kraken 1.1: This benchmark, which is based on the now obsolete SunSpider, measures JavaScript performance. To this basic JavaScript testing, it added typical use case scenarios. Mozilla, Firefox's parent organization, created Kraken With this benchmark, the lower the score, the better the result.
With Kraken, it was a different story. Here, Chrome took first with 1,009.8 milliseconds (ms). Chrome was followed by Opera, 1037.0 ms. Edge took third place with 1,052.5 ms. Firefox, even though its parent company wrote the benchmark, came in fourth. IE? Don't ask. It was a distant last with 1826.7 ms.
Octane 2.0: Google's contribution to JavaScript testing also includes scenario testing for today's highly interactive web applications. Octane is not Chrome specific. For example, it tests how fast Microsoft's TypeScript compiles itself. In this benchmark, the higher the score, the better.
Google may have wrote this benchmark, but Edge took first place going away with a score of 36,544. Chrome rallies to second place with 33,926. The third spot went to Firefox, 31,339. Opera took fourth place with 27,736. IE's results were ugly. With 17,571, it couldn't even reach half the score of its younger brother, Edge.
RoboHornet: This benchmark doesn't just focus on JavaScript. Instead it "encompases all aspects of browser performance and everything that matters to web developers, like performance of layout and localStorage." Once more, on this benchmark, the higher the score the better.
On this performance test, Chrome kicked rump and took names with a total of 175.73. Opera made a contest of it with a score of 165.13. For once, IE didn't make a fool of itself. It took the bronze with 117.78. Firefox took fourth place with 115.13. Oddly enough Edge turned in its worse score on this benchmark: 102.23.
HTML5 Test: Finally, I checked to see how well each browser complies with today's web standard: HTML 5. This "test" isn't a benchmark as such. It just shows how close each browser comes to being in sync with the HTML 5 standard. A perfect score, which no one got, would have been 550.
Chrome took home the gold by a nose over Opera, 521 to 520. Firefox came in third with a score of 468 and Edge was fourth with 453. Coming in dead last, once more, was IE, 343.
First things first: The browser you don't want to run on Windows 10 is IE 11. It simply isn't competitive with its rivals.
By the tale of the benchmark, it's between Chrome and Edge.
Benchmarks aren't everything. For example, as ZDNet's Mary Branscombe, observed recently, "I was surprised by just how many other browser features Edge is missing, from tab groups that collect together pages I opened from one search, to being able to pick from a list of the tabs I closed recently rather just the last slip of my finger, to being able to search through my history."
What I miss --and why I can't consider Edge for my primary Windows 10 web browser -- is its lack of support for extensions. On Chrome, my main browser on all platforms, I use over a dozen extensions every day. They allow me to search through a site using Google, invoke the ZenMate virtual private network (VPN), and save pages to Google Drive. I'm not moving to a web browser without extensions in this lifetime.
There are also some sites, most noteworthy is Facebook, which don't play well with Edge. Still, that isn't so much Microsoft's problem as it is Facebook playing fast and loose with web standards. Of course, that's not going to matter to you if you're having fits making Facebook comments.
Taken all-in-all, Chrome's my first pick for Windows 10. However, I can see why some of you would prefer Edge. I will be watching Edge closely. I'm told by friends at Microsoft that the company is putting lots of resources behind it. By this time next year, Edge may be the unqualified best Windows 10 web browser, but it's not there yet.
By Steven J. Vaughan-Nichols for Networking | January 15, 2016 -- 13:14 GMT (05:14 PST)
On earlier versions of Windows, the best browser you can run today is clearly Google Chrome. But, what about Windows 10? There, it's a different story.
On Windows 10, it's not crystal clear what the best web browser is. It is, however, obvious what the worst one is: Internet Explorer 11.
sjvn
With Windows 10, you have another choice: Microsoft's replacement for Internet Explorer (IE), Edge. For now Edge is only available on Windows 10. Since Microsoft recently open-sourced ChakraCore, Edge web browser JavaScript engine, it' possible we may yet see Edge running on Windows 7, 8, and 8.1. Indeed, Microsoft is porting ChakraCore to Ubuntu Linux!
When last I looked at Windows 10's web browsers, I looked at a late beta in June 2015. Now, Windows 10 has been released and then massively upgraded. For my tests on this run, I used Windows 10, version 10586.63, the latest update as of mid-January 2016.
I ran these performance tests on an Asus CM6730. This desktop PC is powered by a third-generation 3.4Ghz Intel Core i7-3770 processor. This is supported by a Nvidia GeForce GT 620 graphics card. The PC also has 8 GBs of RAM and a one TeraByte hard drive.
On this system, besides the latest versions of Edge (25) and IE 11, I tested at the latest versions of the most popular desktop web browsers. These are Chrome 49, Firefox 43, and Opera 34. I didn't include Safari in this round-up because Apple no longer releases new major versions of Safari for Windows. Apple does, however, still support Safari on Windows with security updates.
Here's how well each browser did on the respective benchmarks.
Jetsteam 1.1: This JavaScript benchmark builds on the foundation of the no longer supported SunSpider, It combines several JavaScript benchmarks to report a single score that balances them using geometric mean. Jetstream includes benchmarks from the SunSpider 1.0.2 and Octane 2 JavaScript benchmark suites. This test suite also includes benchmarks from the LLVM compiler open-source project, compiled to JavaScript using Emscripten 1.13. It also includes a benchmark based on the Apache Harmony open-source project's HashMap and a port of the Cdx realtime Java benchmark, hand-translated to JavaScript. Larger scores are better on this benchmark.
While Chrome dominated on older versions of Windows, Edge took first place on JetStream with a score of 231.78. A good distance behind came Chrome with 196.86; Opera with 186.29; Firefox with 182.46, and, way in the back, IE with 133.07.
Kraken 1.1: This benchmark, which is based on the now obsolete SunSpider, measures JavaScript performance. To this basic JavaScript testing, it added typical use case scenarios. Mozilla, Firefox's parent organization, created Kraken With this benchmark, the lower the score, the better the result.
With Kraken, it was a different story. Here, Chrome took first with 1,009.8 milliseconds (ms). Chrome was followed by Opera, 1037.0 ms. Edge took third place with 1,052.5 ms. Firefox, even though its parent company wrote the benchmark, came in fourth. IE? Don't ask. It was a distant last with 1826.7 ms.
Octane 2.0: Google's contribution to JavaScript testing also includes scenario testing for today's highly interactive web applications. Octane is not Chrome specific. For example, it tests how fast Microsoft's TypeScript compiles itself. In this benchmark, the higher the score, the better.
Google may have wrote this benchmark, but Edge took first place going away with a score of 36,544. Chrome rallies to second place with 33,926. The third spot went to Firefox, 31,339. Opera took fourth place with 27,736. IE's results were ugly. With 17,571, it couldn't even reach half the score of its younger brother, Edge.
RoboHornet: This benchmark doesn't just focus on JavaScript. Instead it "encompases all aspects of browser performance and everything that matters to web developers, like performance of layout and localStorage." Once more, on this benchmark, the higher the score the better.
On this performance test, Chrome kicked rump and took names with a total of 175.73. Opera made a contest of it with a score of 165.13. For once, IE didn't make a fool of itself. It took the bronze with 117.78. Firefox took fourth place with 115.13. Oddly enough Edge turned in its worse score on this benchmark: 102.23.
HTML5 Test: Finally, I checked to see how well each browser complies with today's web standard: HTML 5. This "test" isn't a benchmark as such. It just shows how close each browser comes to being in sync with the HTML 5 standard. A perfect score, which no one got, would have been 550.
Chrome took home the gold by a nose over Opera, 521 to 520. Firefox came in third with a score of 468 and Edge was fourth with 453. Coming in dead last, once more, was IE, 343.
First things first: The browser you don't want to run on Windows 10 is IE 11. It simply isn't competitive with its rivals.
By the tale of the benchmark, it's between Chrome and Edge.
Benchmarks aren't everything. For example, as ZDNet's Mary Branscombe, observed recently, "I was surprised by just how many other browser features Edge is missing, from tab groups that collect together pages I opened from one search, to being able to pick from a list of the tabs I closed recently rather just the last slip of my finger, to being able to search through my history."
What I miss --and why I can't consider Edge for my primary Windows 10 web browser -- is its lack of support for extensions. On Chrome, my main browser on all platforms, I use over a dozen extensions every day. They allow me to search through a site using Google, invoke the ZenMate virtual private network (VPN), and save pages to Google Drive. I'm not moving to a web browser without extensions in this lifetime.
There are also some sites, most noteworthy is Facebook, which don't play well with Edge. Still, that isn't so much Microsoft's problem as it is Facebook playing fast and loose with web standards. Of course, that's not going to matter to you if you're having fits making Facebook comments.
Taken all-in-all, Chrome's my first pick for Windows 10. However, I can see why some of you would prefer Edge. I will be watching Edge closely. I'm told by friends at Microsoft that the company is putting lots of resources behind it. By this time next year, Edge may be the unqualified best Windows 10 web browser, but it's not there yet.
