| HTML5 |
HTML5Test.com

In the HTML5Test, Chrome again leads the pack with a score of 340. Firefox 6 surges ahead of Opera to take second place, scoring nearly 50 points more than Firefox 5. Opera drops to third place. While Safari still places fourth, version 5.10 adds 65 points and two bonus points to its version 5.05 score. IE9 remains in last place, though it now scores 11 points higher than it did in WBGP5.

In OS X, Chrome is still in the top spot, but with one more point than in Windows 7. Firefox remains in second, while Opera drops to fourth, both with the same score as in Windows. Safari jumps to third, gaining 41 regular and six bonus points over the Windows edition.
| CSS3 |
CSS3 Selectors Test

With Chrome updating from 12 to 13, all five Web browsers now earn a perfect score of 574 in the CSS3 Selectors Test. Since they all pass with 100%, a comparison is pretty meaningless. So, we're officially retiring this test from the WBGP. The results will not be factored in to the Conformance Composite.
| JavaScript |
test262
The Ecma test262 benchmark is replacing the Sputnik JavaScript benchmark. Sputnik is one of the many casualties from the scuttling of Google Labs. Fortunately, the Sputnik developers gave their code to Ecma, another group interested in JavaScript conformance, so Sputnik is now a part of test262. 
The results of test262 in Windows largely differ from the Sputnik scores in WBGP5. In test262, Firefox earns the top spot, followed by IE9, and then Chrome. Safari takes fourth and Opera completely tanks the test. The only difference between the test262 scores in Windows and OS X is that Safari earns one extra point on its native platform.
| DOM |
Acid 3

The Acid 3 scores remain the same from WBGP3. Firefox 6 does not change Mozilla's score of 97. And Microsoft still holds a 95. The other browsers pass completely.
| Conformance Composite |
The table below displays the grade each Web browser earns for overall standards compliance. These figures are achieved by converting the test scores to a percentage of 100, then averaging the aggregate.

Google Chrome is still the conformance king with version 13, earning a B+ score of 89.6. Firefox 6 moves up to second place, earning a B rating and score of 87.4. Safari also earns a B by placing third with a Windows 7 score of 82.6 and 85.6 in OS X Lion. Opera 11.50 falls from second place to fourth as a result of our switch from Sputnik to Ecma's test262, landing it a solid C. Predicatbly, the HTML5Test shoots IE9 out of the sky; Microsoft's browser only achieves a 74.5, earning it a C grade.
- 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!