With the Firefox 10, Opera 12 and Internet Explorer 10 releases just around the corner, guys from TomsHardware have decided to test the latest stable builds of the top 5 web browsers on both Windows 7 and Mac OS X Lion.

How did your favorite web browser perform? Let’s find out.

Tested versions

Internet Explorer 9
Firefox 9
Google Chrome 16
Opera 11.60
Safari 5.1.2
<!--more-->

Startup Time Performance Benchmarks

Web browser benchmarks on Windows and Mac OS X.

With the recent Firefox and Google Chrome releases, TomsHardware has decided to test all the competitors in both Windows and Mac OS X operating systems.

There’s no time to waste, so let’s dive into the results.

Startup Time

Page Load Times

With the release of Firefox 5 and Opera 11.50, TomsHardware took 5 most popular web browsers and compared them against each other.

Internet Explorer 9
Google Chrome 12
Firefox 5
Opera 11.50
Safari 5

What are the results? Let’s check them out.

Startup Time

Page Load Times

JavaScript

Silverlight

JSGameBench

Psychedelic Browsing

Memory Usage

Battery Life

Conclusion

Conformance Testing

Standards Conformance

When it comes to summarizing all the results, Google Chrome 12 takes the crown and is followed by IE9, Firefox 5, Opera and Safari.

So here you have it folks. Whether or not Chrome will continue to be the king of the hill with the upcoming releases of Internet Explorer 10, Firefox 6 and Opera 12, remains to be seen.

With the release of the Internet Explorer 10 Platform Preview 2, Microsoft has decided to post results of the JavaScript Standards Test, which scores are available below.

The following web browsers were tested:

Internet Explorer 10 (Platform Preview 2)
Internet Explorer 9
Firefox 5
Google Chrome 13 (13.0.782.41)
Google Chrome 12 (12.0.742.112)
Safari 5.0.5 (7533.21.1)
Opera 11.50

As you can see from the results, IE10 has scored 99%, followed by Firefox 5.0, IE9 and Google Chrome 13 Beta. Surprisingly or not, Opera 11.50 has scored only 65%, lowest of all the web browsers.

What is test262?

test262 is a test suite intended to check agreement between JavaScript implementations and the ECMA-262 Specification (currently 5th Edition). The test suite contains thousands of individual tests, each of which tests some specific requirements of the ECMAScript specification.

Surprised, excited or both?

Benchmarks are incredibly important for influencing the direction of JavaScript engines. Over the past two years, JavaScript has gotten dramatically faster across all major browsers, particularly in areas that popular benchmarks measure. As it turns out, browser developers are a competitive bunch. However, as JS engines get faster, benchmarks must evolve in order to keep pushing them in the right direction.

We’ve been constantly updating our V8 benchmark suite to force us to get faster in areas that are important to web developers. We’ve fixed bugs and added new tests for regular expressions and memory management. We’re very focused on JavaScript performance, so we scrutinize our benchmark carefully to make sure that it’s as useful a measuring stick as possible.

The two other widely cited JS benchmarks are SunSpider from Apple, and Kraken, a new benchmark from Mozilla.

SunSpider was one of the first suites of tests, first appearing in 2007. It’s done a lot to help improve JS engines, but many of the tests in the suite are less relevant to the web in 2011. Even for the more relevant tests, JavaScript has gotten so fast that many finish in only a few milliseconds. This just isn’t long enough to figure out which engine is faster--a golf cart and a Tesla will finish a 10-foot race in nearly the same time.

To make the benchmark more meaningful, we’ve experimented by making the race longer by running each of the tests in SunSpider 50 times consecutively. While repeating a trivial test many times isn’t a great solution, it does provide an opportunity for some optimization. With this change, the results begin to reflect Chrome’s true performance. It’s more than 30% faster on the SunSpider suite overall and up to 4x faster on some of the individual tests.

Kraken, a more modern benchmark, is in better shape. Unfortunately, the canonical version of the benchmark has not been updated to reflect all the latest changes which address at least one important bug. As a result, the benchmark is less useful and has even (mis)led us to spend time making some irrelevant optimizations in Chrome. To help us focus on the right things, we’re now testing the latest version of Kraken built directly from Mozilla’s source code repository.

We’re posting a modified version of SunSpider and the latest version of Kraken to make it easy to run the benchmarks in your own browser and compare results.

Some time ago, TomsHardware has published a nice list of benchmark results for the top 5 web browsers. Unfortunately, they did not test the final version of Firefox 4.

Well, this is no longer the case as the most recent tests now include the following:

Internet Explorer 9
Firefox 4
Google Chrome 10
Opera 11
Safari 5

Startup

Now here is a new benchmark for you to talk about: power consumption.

Turns out, Microsoft optimized Internet Explorer 9 not only for the performance but also for your wallet and productivity.

According to IE Blog, when it comes to power consumption, IE9 and Firefox 4 are the browsers to die for.

Want some good news? Just by using Internet Explorer 9 over Opera 11 you can have an extra hour of the battery life on your laptop!

What do you think about the results? For even more details, visit the original post.

TomsHardware has posted a nice benchmark and compared some of the most popular web browsers. Unfortunately, Firefox 4 was not included.

Browsers
Google Chrome 10.0.648.134
Firefox 3.6.15
Internet Explorer 9
Opera 11.01 (build 1190) 51
Safari 5.04 (7533.20.27)

Startup Times

Page Load Times

It looks like the 64 bit version of Google Chrome web browser might be coming in the near future as AreWeFastYet.com now lists both OS versions:

Mac OS X, 32-bit
Mac OS X, 64-bit

However, don’t get too excited yet. When comparing benchmark results, 64 bit version actually scored much less than the 32 bit version: 5600 points vs. 6700 points (V8 benchmark).

Judging from test results, 64 build still has a long way to go.

Google released the newest Google Chrome 10 build to the beta channel yesterday, boasting progress in the form of revamped browser settings, password sync features, as well as JavaScript performance.

V8, Chrome’s JavaScript engine, now runs intense JavaScript applications faster than in the past. To be more specific, the V8 benchmark suite indicated an improvement over the current stable release of 66%. See the chart below to see how it compares with prior versions of Chrome.

GPU accelerated video is now also a part of the new beta, reducing CPU usage for and improving battery life. The highest recorded drop in CPU usage was 80% when using full screen mode.

Saved passwords can now be synced across numerous computers as well. It was previously only extensions, themes, bookmarks, and preferences that could be synced. Passphrases can be utilized to encrypt passwords for additional security.

With regards to the revamped browser settings, they now open in a tab instead of a window.

A search function has been introduced to allow users easily find the feature they wish to change the settings for (with results updating as you type). Settings pages now have their own URLs as well, giving users the ability to navigate straight to a particular setting.

The race is on.

Google Chrome fans will scream out of the excitement, as Google has recently released the very first build of Google Chrome 10 with Crankshaft.

What is that?
It is a new compilation infrastructure for Google’s V8 JavaScript engine.

Vygantas, it’s confusing and such, just give us benchmarks already.

According to Google, Crankshaft has four main components that help to achieve such performance improvements:

• A base compiler which is used for all code initially.
• A runtime profiler which monitors the running system and identifies hot code, i.e., code that we spend a significant amount of the time running.
• An optimizing compiler which recompiles and optimizes hot code identified by the runtime profiler.
• Deoptimization support which allows the optimizing compiler to be optimistic in the assumptions it makes when generating code.

In case you want to test it as well, just head over to the canary builds page and seek for download link.

Today, we test five most popular web browsers to find out, who leads and who lags in the HTML5 Benchmark.

Browsers

Internet Explorer 8
Internet Explorer 9
Firefox 3.6
Firefox 4
Google Chrome 7
Google Chrome 8
Opera 11
Opera 10.6
Safari 5
WebKit

Results

Higher is better. Maximum score: 377 points.

Internet Explorer 8 – 32
Internet Explorer 9 Beta – 80
Firefox 3.6.10 – 145
Firefox 4 Beta 6 – 235
Google Chrome 7.0.517.41 – 248
Google Chrome 8.0.552.11 Beta – 262
Opera 11 Alpha – 223
Opera 10.63 – 203
Safari 5.0.2 – 178
WebKit r70433 – 196

Conclusion

As per our test, Google Chrome 8 takes the lead, followed by Google Chrome 7 and Firefox 4 Beta 6.

Unfortunately for Internet Explorer 9 and 8, they are in the bottom, followed by Firefox 3.6 and Safari 5.

Thanks to Nox for the tip.

As Google Chrome 7 (dev) now includes hardware acceleration, guys from DownloadSquad decided to test it along with Internet Explorer 9 (developers preview) and Firefox 4 (beta).

What are the results?
Google Chrome 7 utilized the most of the hardware resources, delivering better FPS (frames per second) than Internet Explorer 9 or Firefox 4, which took the last place.

However, as those are not the final builds, don’t draw your conclusions yet, things might change in the future.

Thanks to geek for the news tip.

In rather pointless benchmark, DownloadSquad has tested latest Internet Explorer 9 build against Google Chrome 6 dev.