I took the newly released Google Chrome web browser for a test drive today. I Had the official web page on refresh and so I had downloaded my copy as soon as it became available there. Using a newly released browser, which has also taken most of the known Internet by storm was a pretty overwhelming experience for me.
The browser’s currently released build is 1583 (first public beta) and is based on Mozilla 5, Gecko 1.9.1 and most importantly on WebKit 525.13, meaning that it has the ability to achieve a 100/100 pixel perfect score on Acid3 Tests. It uses the V8 engine for ECMAScript compilation, which is reportedly two times faster than Firefox 3 and Safari 4.
Well this is about enough on the Basics of the browser, and I’m sure that you would like to know how it performs in the world wide web? Well I took this new baby out for a spin on some of the most popular (and most demanding) websites on the Internet today. The browser turned out to be one of the fastest ones I had ever seen (surely giving Safari 4 a run for its money) and had performed above expectations on most sites.
Starting of with my favorite social networking site (yes I’m not a MySpace fan), I performed a couple of common tasks like updating my status and posting a note. I was expecting much especially because of my experience from Internet Explorer 8, but Chrome held out pretty well when tasked to handle all of the original Facebook code. Unfortunately there were JavaScript and AJAX related problems on some third party applications which were specifically designed for Firefox 3. I also had some trouble posting comments on just about anything. But they weren’t as bad as what had happened in IE 8.
Gmail
If anyone would be thinking that Gmail may have some issues with Chrome, then you should probably go back to kindergarten. Google had worked out all the bugs for Gmail before handing out Chrome to the public so you can rest assured that all your emails would be safe and secure.
Yahoo! Mail
When it comes to web-mail, most of the population is either using Yahoo! Mail (like me) or Gmail. If you happen to use any other service (comment below if you use Live Mail) then I recommend that you sign up for either one of these. Back on the subject, Yahoo! Mail had given me quite a surprise when I loaded it! There was no compatibility warning – meaning that Google and Yahoo! had already communicated regarding the new browser. Needless to say Yahoo! Mail performed great and surprisingly fast as compared to the Yahoo! endorsed Firefox 3.
Yahoo!
The Yahoo! home page took an instant to load up and there were no graphical problems with the rendering. All the features were working smoothly and the AJAX-Flash blending was perfect.
Wikipedia
One of the biggest surprises came from Wikipedia. I have a very demanding visual theme setup on Wikipedia along with a lot of JavaScript based plugins. It only took a second to load all of that! that was nearly half the time it takes on Firefox or Safari for that matter. There were no rendering issues with the interface, though some plugins refused to work as they didn’t reccognize the browser and chose not to load at all.
YouTube
I had a pretty bad experience while testing YouTube on IE 8 a few days ago. But I wasn’t expecting to run into any problems on Chrome as both are Google products. My expectations prooved correct and YouTube performed quite smoothly and a few bugs I experienced in Firefox were absent here, like it takes too much time to navigate from a video page when a video is playing. This was due to the multiprocess architecture of Chrome.
Flickr
Flickr was working fine and there were no speed or compatibilty issues. The newly integrated Picnik had a bit of slow start but once loaded, worked out pretty much fine.
Last.fm
The social music site Last.fm had a bit of performance issues as they are very much tailored for Firefox. Thier Flash based players worked great though.
Memory
The resource utilization of Chrome was a bit high. It used some more CPU (due to its architecture) and memory compared to Firefox or Safari, but the overall memory utilization was great with no apparent memory leaks.
Acid3
This was the biggest surprise of the day! Google Chrome actually scored 78/100 on the Acid3 test even in its infancy. This shows the power of the underlying WebKit and V8 engine. The only known browser to pass the Acid3 test is Apple Safari 4 beta, with the latest beta versions of Opera and Firefox close behind. Internet Explorer family is long way off from this standard as the current version of IE 8 only manages around 20/100.
Silverlight
Silverlight has some strange issues on Chrome, mostly related to UI and interaction with the mouse. I tested this on numerous silverlight sites including PopFly.
Flash
Flash content worked smoothly, although not as fast as Firefox. Chrome uses the same plugins as other browsers so there may be some issues regarding the plugin architecture in Chrome. Flash crashed after sometime (about 4 hours) while I really stressed it on YouTube, but the good thing was that it didnt affect anything else.
Conclusion
Even though I have tested it for only a few hours right now, I say that Chrome is a pretty strong browser at such an early stage. Its open source and its based on some of the most proven technologies (like WebKit) meaning it has all the ingredients to become one of the best browsers out there giving a lot of competetion to the elites Firefox, Opera and Safari (Sorry Internet Explorer doesn’t qualify here). If you haven’t already then download Google Chrome and give it a go yourself to see what I mean. As always, you can share you’re experiences via comments.















September 3, 2008 at 14:22 UTC
[...] Google Chrome Hands On Test Drive 4 hours ago [...]
September 3, 2008 at 14:33 UTC
I am being constantly blocked by the lack of Java support. Many sites use Applets for various things, from simple graphics to complex functionality. The fact that they are not rendered makes the site unusable.
September 3, 2008 at 14:55 UTC
The fact that I didnt do Java testing was that Java Applets wouldn’t recognize the browser yet. The same problem was with some JavaScripted RIAs which were designed to only work with Firefox, Safari, Opera or IE.
In the coming weeks, we can expect developers to add support for Chrome as it is one of the fastest beasts I have seen.
September 3, 2008 at 19:09 UTC
[...] All the screen shots are taken in the newly released Google Chrome browser. Picnik loading in Google Chrome After you log in, you are greeted with this My Facebook [...]
September 4, 2008 at 16:35 UTC
If you search support for chrome, you’ll see that you need java6 update 10 to work with Chrome. Available here:
http://java.sun.com/javase/downloads/ea.jsp
September 4, 2008 at 20:53 UTC
I don’t know if it’s just me but… Did the smooth scroll worked for you guys? I could only scroll down but not up sites…
September 4, 2008 at 22:04 UTC
@Larry
Thanks for the heads up. It really works.
@Alex
Its working fine here. I mean if you mean page scrolling then I have had no trouble with it.
September 4, 2008 at 22:27 UTC
I can’t scroll up pages
September 4, 2008 at 22:51 UTC
Its working perfectly here. Arrow keys, Scroll bars, mouse wheels, everything. There might be a problem with your system?
September 4, 2008 at 23:28 UTC
[...] Central. The news came on September 2 on WinCustomize, when most of the world was waiting for the launch of Google Chrome. Here’s what the official press release had to say: The betas for WindowBlinds 6.3 and [...]
September 5, 2008 at 20:47 UTC
Problems with Chrome…Well there are some. It IS the fastes and most stable thing around AND with some thinkering you can make java& Flash work BUT 1.)Java applets ONLY work if you use the new in a web page instead of . I dont think it is a bug i think it is a standardization.. applet tag is deprecated according to w3. But shockwawe dont work at all and flash sometimes behaves like running a 3d game on a very old system
September 5, 2008 at 22:17 UTC
Well I tried two different versions of Flash… Flash Player 9 Update 3 is more stable than Update 4.
And I didn’t test it on Flash Player 10 yet but will do that tomorrow.
September 8, 2008 at 16:34 UTC
No problems so far (other than company Intranet – ludits work on our systems) – performance does seem impressive.
No crashes yet either!
September 8, 2008 at 19:41 UTC
[...] and have there own separate memory. This feature has been presented in other browsers as well, like Google Chrome, but Prism gives more flexibility even though it is still in the [...]
October 3, 2008 at 17:32 UTC
I have noticed that developer updates are resolving some of the issues you have pointed out. Try using the dev updates tool from chrome and you may have better luck on some of these sites.
October 4, 2008 at 21:24 UTC
[...] the main problems addressed and fixed with this update are related to the Flash plugin. I had reported earlier about the issue on my previous review, and it seems like the developers listened to it. More [...]