Reliability Benchmarks: Proper Page Loads

The first chart says "higher is better" for the load time

thank you, workin' on it

Chrome is the best browser out there right now. While FireFox maybe more popular then Chrome is, Chrome has shown why it is the best browser out today. If you haven't used Chrome yet it's def worth a look.

The reader function in safari actually looks really nice. Although I'd never use Safari on principle. I hope other browsers implement a similar function.

why does firefox(6/8/9) performa so horribly on the IE9 maze solover test?
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".

Being on a Macbook with only 3GB of memory, memory is the most important factor for me. I open a LOT of tabs and I keep them open for long periods. For awhile I used Chrome, but recently switched to Firefox 6 and saw my memory utilization drop by well over 1GB. Granted with Firefox I was able to do something I am not able to do in any other browser, I could group my tabs into tab groups. I believe this allows for more efficient memory management, i.e. only the current group uses much memory. Not having done any tests, this is pure speculation. All I know is that I'm seeing MUCH lower memory usage with Firefox on OSX. Despite what this article would suggest.

@soccerdocks

Yeah? And exactly what principle would that be?

@Google:
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.

I keep Opera, more memory used and time to load pages is nothing when it load pages correctly; and the feeling in its interface is the greater.

while these articles are entertaining, giving straight points skews the results a bit IMO. I think it would give more insight to give percentages in the analysis tables rather than just ranking them. After all, giving 1 pt for 5% better result out of the 5 is 20%, kinda throws off actual performance.

thank you, workin' on it

On OSX browser 'vendors' are denied access to certain os hooks that would make their browsers better than they are.

Nice overview: thank you.
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.

Adam, you should have mentioned in the end that even if Safari won on OSX, the victory is a pyrrhic one as OSX lacks in Java and Silverlight plugin performance; OSX Lion is also very poor at system memory management and reliability.

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...

Tried Chrome, but somehow it doesn't behave the way I wanted. Browsing pages is faster with Firefox on 384 kbps internet. Makes me wonder...

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!