Web Browser Grand Prix VIII: Chrome 16, Firefox 9, And Mac OS X

Features
By
published

Back in August, Mozilla took the WBGP crown with Firefox 7. Can Firefox 9 retain that title? And how are the top Web browsers doing in Mac OS X? We used a Hackintosh last time. This time, we're testing on the world's first Ultrabook, the MacBook Air.

Crowning Two Champions In Windows 7 And OS X

Web Browser Grand Prix Champion, The Windows Circuit

Although Firefox demonstrates the least number of wins (one less than IE9, Opera, and Safari, and two less than Chrome), it achieves the highest number of strong scores and only turns in one weak performance. Firefox 9 solidifies Mozilla's Web Browser Grand Prix championship, which was precariously handed out to Firefox 7 last September. Congratulations Mozilla! It's good to see that this browser war veteran still has some fight left in it.

Chrome 16 is still just a minor performance update away from matching or perhaps even surpassing Firefox 9 though, and the recent improvements to Firefox seem to have absolutely no effect on Google's march to the top of Web browser market share.

Opera is still hanging onto a strong third-place position with version 11.60, especially considering it still lacks HTML5 hardware acceleration and WebGL support. But Opera 12 is on the way, and it promises to seriously shake things up, just like the last two whole-number releases out of Norway.

Microsoft Internet Explorer has been stagnating for several months, and it's really starting to show. Last year, IE9 won two consecutive Web Browser Grand Prix championships and stayed near the top of the pack for some time afterward. The browser now resides at the bottom of the heap, tied for last place Apple's offering in Windows 7.

While the Windows version of Safari moved forward since our last look, the progress isn't enough to move the browser out of last place. In Windows 7, that is...

Web Browser Grand Prix Champion, The Mac OS X Circuit

Despite the best efforts of Google, Mozilla, and Opera, Apple Safari retains its OS X Web Browser Grand Prix crown. With a staggering number of wins and an equally impressive lack of weaknesses, Safari 5.1.2 simply owns on its native platform.

The OS X runner-up, on the other hand, is highly debatable. We're going call it in favor of incumbent number two, Google Chrome. Firefox 9 really pulled ahead from the last-place finish it received back in August, though.

Unfortunately, the Mac version of Opera is a mere shadow of its Windows version, landing the Norwegian powerhouse in last place.  

Operating System Comparison

The red bars that occasionally appear in our charts denote when an OS X-based browser beats all of the Windows 7-based competition. We use the word occasionally because we only had to switch the Mac OS X green bars to red four times. That's four out of 35 eligible charts, as opposed to the 10 out of 29 OS X earned on the Hackintosh system we used in Web Browser Grand Prix VI: Firefox 6, Chrome 13, Mac OS X Lion. While many Mac fans expected to see OS X really hammer Windows 7 on a genuine Mac, the home court advantage didn't do Apple any favors.

So, Redmond wins yet another Mac versus PC Web Browser Grand Prix, this time on a mobile system (and a brand new Core i7-based MacBook, to boot). Ouch.

Follow Adam on Twitter.

TOPICS
Adam Overa
152 Comments Comment from the forums
  • twztechman
    Been using Firefox for years - it works best for me.
    Reply
  • shiftmx112
    This makes it worth putting up with the constant updates on Aurora. :)
    Reply
  • The best part is I'm quite sure that this is using an out of the box build. Using a PGO compiled nighlty build, with about:config properly configured, and addons like Adblock/NoScript blocking things from ever loading Firefox is significantly faster than these benchmarks state.
    Reply
  • frost_fenix
    I have use firefox and chrome interchangeably for a few years now. I enjoy chromes streamlined design but have recently discovered the noscript addon for Firefox and have since favored Firefox. I have also found Firefox to be more compatable with school webpages and application pages. Still either firefox or chrome is better than IE.
    Reply
  • pharoahhalfdead
    Good point Stoof. I have IE9 and the newest FF, and with the FF add ons, it blows IE out of the water. The majority of IE pages like yahoo video links, boxingscene etc take 6 or more seconds to load, whereas FF is only a fraction of the time.

    I think add ons are much easier to find with FF, and there seems to be a wider variety. Then again I do realize this article wasn't about browsers with add ons.
    Reply
  • hardcore_gamer
    The only one thing I hate about firefox is that it takes a lot of time to launch.
    Reply
  • adamovera
    stoofThe best part is I'm quite sure that this is using an out of the box build. Using a PGO compiled nighlty build, with about:config properly configured, and addons like Adblock/NoScript blocking things from ever loading Firefox is significantly faster than these benchmarks state.Yes, we're using everything stock. There is no one-size-fits-all combination of plug-ins to standardize on, and every browser might not have the exact same plugins available. So that throws out a fair comparison between browsers - wouldn't work for the WBGP. Perhaps an article concentrating specifically on Firefox (or another Web browser) with and without various plug-ins would clear that up?
    Reply
  • Please use Firefox's latest logo, the one with the shiny orb in Mozilla's press kit! The one they're using now is the old one. http://www.mozilla.org/en-US/firefox/brand/identity/
    Reply
  • nevertell
    Chrome is the easiest to use if you've got lots of tabs open. Scrolling through them with mouse is a breeze and tab management is just excellent.
    Reply
  • soccerdocks
    frost_fenix. I enjoy chromes streamlined design but have recently discovered the noscript addon for Firefox and have since favored Firefox.
    Why do people seem to forget Chrome has this built in. All you have to do is go into the options menu and disable JavaScript.
    Reply