Web Browser Grand Prix VI: Firefox 6, Chrome 13, Mac OS X Lion
-
Page 1:Crowning A Web-Browsing King In Windows 7 And OS X
-
Page 2:The Contenders
-
Page 3:A Spotlight On Lion's Safari
-
Page 4:Hardware And Test Setup
-
Page 5:Performance Benchmarks: Startup Time
-
Page 6:Performance Benchmarks: Page Load Time
-
Page 7:Performance Benchmarks: JavaScript, DOM, And CSS
-
Page 8:Performance Benchmarks: Flash, Java, And Silverlight
-
Page 9:Performance Benchmarks: HTML5
-
Page 10:Performance Benchmarks: HTML5 Hardware Acceleration And WebGL
-
Page 11:Efficiency Benchmarks: Memory Usage
-
Page 12:Efficiency Benchmarks: Memory Management
-
Page 13:Reliability Benchmarks: Proper Page Loads
-
Page 14:Conformance Benchmarks: HTML5, CSS3, JavaScript, And DOM
-
Page 15:Placing Tables
-
Page 16:Analysis Tables
-
Page 17:Two Winners: One In Windows 7, One in OS X
Efficiency Benchmarks: Memory Usage
Light Load

The placing for single-tab memory usage remains the same as what we saw in WBGP5, with IE9 in the lead, closely followed by Chrome, Safari, Firefox, and Opera.
On Mac OS X, all of the memory usage totals are higher than Windows 7, and the order is re-arranged. The top spot goes to Opera. Second place goes to Safari 5.1, with just under 100 MB. Chrome takes third, while Firefox uses nearly 130 MB to finish last.
Heavy Load
For the first time in the WBGP, Safari manages to fully load all 40 tabs at the same time without freezing. Previously, we had to open each of the 40 tabs individually in Apple's browser.
In WBGP5, we also reported some odd behavior from Internet Explorer 9 in these tests. Microsoft's browser would display certain white space-heavy pages in all black, and sometimes freeze entirely. This time around, we used the WHQL-certified AMD graphics driver provided by Windows Update instead of the company's website, and this phenomenon did not occur. After running through the full benchmark suite, we installed the latest Catalyst suite and retested. Sure enough, the wonky behavior returns with the Catalyst driver installed. The video below shows the white space issue on Wikipedia at 1:20:
The next video show the complete freeze-up at 1:50:
Now on to this story's 40-tab memory test:
The order again looks similar to what we saw last time. Safari uses the least amount of RAM to open 40 tabs. Firefox retains its second-place status, consuming three-quarters of a gigabyte. Opera is not far behind in third, still under 800 MB. Chrome 13 drops to fifth, allowing Microsoft's IE9 to jump into fourth.
In OS X, Safari 5.1 still uses the least memory of any Web browser, though nearly 100 MB more than it does in Windows. Opera moves to second place with 40 tabs open in OS X, hovering just over the 800 MB line. Firefox 6 uses nearly 1.2 GB to take third, while last-place finisher Chrome 13 uses a a whopping 1.8 GB.
- Crowning A Web-Browsing King In Windows 7 And OS X
- The Contenders
- A Spotlight On Lion's Safari
- Hardware And Test Setup
- Performance Benchmarks: Startup Time
- Performance Benchmarks: Page Load Time
- Performance Benchmarks: JavaScript, DOM, And CSS
- Performance Benchmarks: Flash, Java, And Silverlight
- Performance Benchmarks: HTML5
- Performance Benchmarks: HTML5 Hardware Acceleration And WebGL
- Efficiency Benchmarks: Memory Usage
- Efficiency Benchmarks: Memory Management
- Reliability Benchmarks: Proper Page Loads
- Conformance Benchmarks: HTML5, CSS3, JavaScript, And DOM
- Placing Tables
- Analysis Tables
- Two Winners: One In Windows 7, One in OS X
thank you, workin' on it
chrome13 completely obliterats it.
and firefox 8/9 are still a memory hog.
not really surprised by poor show of ie9. moat updates it gets are "security updates".
Yeah? And exactly what principle would that be?
Bring back the Google Dictionary, otherwise I will use Bing Search, Firefox and Facebook instead of Google Search, Chrome and G+.
According to the graphic on "Reliability Benchmarks: Proper Page Loads" on MacOS Firefox is actually second, not third.
thank you, workin' on it
These "browser" GP are getting more and more complete and the're always very interesting.
I have to say, I am a bit surprised to see FF being so close to Chrome now: kudos to Mozilla.
I have been using FF since 1.0 and only recently coupled it with Chrome (it is just convenient for me to have 2 completely different setups).
FF 7.0 should have a significant boost in memory efficiency: if everything else stays the same, we´ll have a new champion ...
But if anythin is clear from these reviews, is that nothing stays the same for very long in the browser´s domain (well, except IE).
Looking forward to GP7, whenever that will be.
You should've put more emphasis on the actual scores and performances in tests rather than count the times when certain browsers placed 1st. Thus a browser that had a small advantage in more and minor tests and at the same time severe handicaps in more important but fewer tests would seem better, when technically it is not. Suggestion: tie all the candidates when the differences between them in a certain test are less than a single digit percent. Good article anyway.
And to think Apple hates Flash...
There are no points in the analysis tables. They simply list how each browser rates per category of testing. The 'Strong' part of the table was added a long time ago and it basically means that it's right up there with the winner in terms of performance. When we get a solid point-based scoring system figured out 'Winner' will only receive a minor boost above 'Strong', whereas 'Strong' will receive a significant boost above 'Acceptable', and 'Acceptable' above 'Weak'. We're not there yet, but we're getting closer with every WBGP. The composite tests are a BIG step in that direction, and the new benchmark rankings further lay the groundwork for a fair scoring system which accurately reflects scale.
The analysis tables were created to balance the raw placing tables. The problem with what you're saying is that you would have to decide which categories are more important than others. Is JavaScript more important than CSS? Is HTML5 more important than Flash? This is going to depend on who you ask. People who only watch Netflix with an HTPC will put mega emphasis on Silverlight perf, whereas the chronic YouTuber will be more concerned with Flash, and devs are going to gravitate towards standards conformance. Ranking benchmarks based on the importance of what they test isn't a one-size-fits-all type of thing with Web browsers. As far as your other suggestion, dealing with practical ties, this is something we definitely want to look into moving forward. Thanks!