Home > Technology, Web 2.0 > Salesforce performance in Google Chrome

Salesforce performance in Google Chrome

by Matt on September 3, 2008

Google Chrome has just been released and naturally I just started using the nearest available application in “the Cloud” that I could lay my hands on… Salesforce of course.

Strike me dead, I swear Chrome is at least twice as fast as Firefox to use while navigating around Salesforce.

Pages load real fast, Salesforce now is an even more pleasurable app to use. (is that even possible?)

I think this probably would have something to do with Chromes fancy multi-threaded Javascript processor.

Salesforce uses alot of Ajax, and I can see alot of applications benefiting from this. More than anything that Chrome has to offer, I think performance with the latest and greatest Web 2.0 applications will be it’s biggest contribution to our working lives.

I’m convinced that as we move more and more to the “Cloud” for storing every aspect of life, every nano-second of performance will add up.

{ 1 comment… read it below or add one }

Steven Fine October 15, 2008 at 12:05 pm

Salesforce works smoother on Chrome than any other BROWSER except !!!!

I cannot send a Saleforce HTML template when using Google Chrome

Anybody have an idea why and if there is a way to get around this ?

THE ERROR SHOWING IS
____________________________________
To use the HTML Email & dynamic tracking feature you must upgrade to Internet Explorer (IE) version 6.0 or higher.

Upgrading to IE 6.0 or higher will allow you to take advantage of all the easy to use HTML tools to create professional, high impact email templates for your marketing, sales and support users. Upgrade now to take advantage of the following features:

Send professional, high impact HTML emails
Customize and personalize each email before sending it
Track when your prospect or customer read the email, and how many times!
Run reports on all HTML emails you’ve sent this week to see which have been opened the most

Leave a Comment

Previous post:

Next post: