What’s in a Browser?

Perhaps the most interesting part of testing these browsers is just how the results are a snapshot in time. With credit to Google, browser development happens at a very rapid pace, so these results may skew one way or another with time, with the tendency for better performance as time goes on, but sometimes there is some degradation as well. It will be interesting to check back again in a year.

Microsoft Browser Evolution

When Windows 10 was first announced, Microsoft was very keen to promote their new browser, eventually named Edge. They took their Trident rendering engine from Internet Explorer, and stripped it back to its core, then rebuilt it as a more modern, and more standards compliant browser than they had ever done previously. Unfortunately for Microsoft, Google’s Chrome browser continued to gain usage share, and with it came developers testing against Chrome. There was a years-long PR war with Microsoft begging developers to write websites to standards and features, rather than just based on a User Agent String, but that war was lost, and in a surprising, but also necessary move, Microsoft abandoned its browser and joined the Chromium gang. While it is great to see them embracing open source and the Chromium project, it is also somewhat sad to see the open web consolidating so much around Chromium. Firefox remains the only major browser in the PC space to not utilize Chromium. Apple continues to utilize WebKit, which was the code base that Chromium’s Blink came from, but Apple’s strong developer relations (current feuds not withstanding) and presence in the mobile market will keep WebKit as a valid option for them.

Google Chrome is currently the most popular browser on the PC

While there was no decisive winner in any category, there were trends in the data worth covering. First, the performance of all modern browsers is similar enough that choosing a browser based only on performance is not necessary. It should be features that drive usage, and it seems like we are close enough on performance to see that happen. Of the Chromium-based browsers, somewhat surprisingly Google Chrome was not the winner here, at least with the versions tested. Microsoft has made the best of their move to a new browser engine, outperforming both Chrome and Opera by a small margin in all tests. The differences were not massive, but they were there consistently. Mozilla Firefox was able to hold its own as well, scoring a few wins, and almost obtaining the same HTML5 score as well.

On the battery life side, it is clear that Microsoft did give up its advantage there, with classic Edge easily outclassing the field, but with low usage, and issues with website compatibility mostly stemming from the low usage, Microsoft will have to continue their efforts, but this time those efforts will be shared among all of the Chromium browsers. In our testing, Chromium Edge, as it did on the performance side, slightly outperformed Chrome and Opera. Firefox was not quite as competitive, but not so far from the rest that it would likely sway someone to use another browser over Firefox if that is already their preference, unless they really need that extra runtime.

It may seem a bit anti-climactic to say that all the browsers tested performed well, but that was the case. Choosing a browser based purely on performance is not necessary at the moment, as no single browser easily out-muscles its competitors. One of the big questions was in regards to Microsoft’s move from EdgeHTML to Blink, but it is definitely a win in terms of browser compatibility, and even if it did result in a net-loss of power savings, having a power efficient browser you can not use on your favorite website helps no one. Chromium Edge has been in alpha and beta versions for some time, and Microsoft started making it available as a released version earlier this year. The new Edge is great and should only get better. Whether it puts a dent in Google’s dominance is something only time will tell.

HTML 5 Compatibility and Web Browser Battery Life
Comments Locked

121 Comments

View All Comments

  • skavi - Thursday, September 10, 2020 - link

    Thanks for making this! I'd love to see Safari included next time.
  • casperes1996 - Thursday, September 10, 2020 - link

    Whenever Big Sur is released I'd love a Mac version of this with the new Safari in the mix - It's one of basically 3 unique browsers left, and on my 2020 iMac it was faster than Chrome in every single test as well as using fewer system resources, and on my MacBook, gives better battery life with light usage
  • OreoCookie - Thursday, September 10, 2020 - link

    I was so excited to read this article — until I realized the author was going to exclude Safari. Given that there are three browser engines of relevance these days, Chromium, Gecko and WebKit, excluding the one that is in the #2 spot (since it is on all iOS devices) makes this article worth much less.
  • Brett Howse - Friday, September 11, 2020 - link

    It's tough to include Safari in an article where I want to see how Microsoft's move from EdgeHTML to Chromium went, when Safari is only on the Mac.
  • OreoCookie - Saturday, September 12, 2020 - link

    Why is that tough, I think it is really easy? Just use a Mac, install Boot Camp on it and make it dual boot Windows. You then have a perfectly fair way to test all browsers natively. It'd also be interesting to see if there are any speed differences between the OSes. And since you are not benchmarking hardware, any Mac will do.
  • Lord of the Bored - Sunday, September 13, 2020 - link

    Because the underlying OS is a factor. You simply can't compare Safari on OSX to Edge on WinX. It is a meaningless metric.

    Hell, you can't even compare Chromium Edge on WinX to Old Edge on a diffrent WinX service pack.
  • OreoCookie - Monday, September 14, 2020 - link

    Chrome and Edge run perfectly fine on my Mac. So you could account for differences in the OS.
  • casperes1996 - Sunday, September 13, 2020 - link

    Understandable, and with the focus on Edge going Chromium for this article that's a sensible choice. - But for a future article with the focus shifted more onto the nature of what is essentially a three horse race in the browser space, I'd love to see some numbers behind Safari's impressive speed and battery life, though comparatively lacking feature set
  • OreoCookie - Sunday, September 13, 2020 - link

    Regarding feature set, AFAIK the main reason for Safari “lagging behind” is security and that Apple and Google have fundamentally different opinions about how HTML5 should evolve. Google is prioritizing features that allow for richer web apps. But these features could become liabilities as far as privacy and security is concerned. And they could become battery life hogs. And Apple thinks native apps are better than web apps, and making HTML5 into an app platform would be worse for HTML5 and the consumers.

    Personally, I agree with Apple here, I hate web apps and apps that are mere HTML wrappers. The user experience is very lackluster and performance nowhere near as good. Websites that could be super simple already require me to download megabytes to view read an article that is a few kB in size.

    Independently on how you feel about that, a browser review that leaves out the #2 engine seems like it is missing the mark.
  • asmian - Thursday, September 10, 2020 - link

    It would have been interesting to see some significant and by now completely different forked versions like Pale Moon included to see how the debloating of Firefox code and a different rendering engine affects results.

Log in

Don't have an account? Sign up now