Improving SugarCRM client-side performance: The browser

sugarcrmdevelopers —  July 12, 2011 — 8 Comments

This article is the first in a three part series of articles where we will be addressing client-side performance with using SugarCRM. In these articles, we’ll touch on ways to improve performance on the browser, ways to optimize your server configuration for better performance, and a peek into the future of how we are improving SugarCRM for better performance.

The first thing we’ll tackle in this series is improving performance on the client end. When it comes to the browser, there’s really only one important rule to remember, which is…

Browser choice does matter

But why is this? Well’s look at a some testing charts that can help tell us the story better ( taken from )

The chart above throws a lot of random numbers at us. Here’s a quick rundown of what it all means:

  • Security tests performed means whether a browser support the various Javascript APIs and best practices for interactions between sites. The ability to perform attacks like XSS ( Cross Site Scripting ) are measured.
  • The Rich Text, Selectors API, JSKB, and Acid3 tests measure the various HTML and JS abilities of the browser itself.
  • The Network tests measures how well connection related activities are done, such as caching, number of connections available for a request, and how the CSS and JS files are parsed.

Let’s couple this with a chart showing Javascript performance across browsers ( taken from ). You’ll see many of these comparisons all over the web ( each one having slightly different results, depending upon which tools are used  ).

So what is overall message here? I think it breaks down to two things:

  • Keeping your browser up-to-date is much more important these days. And I don’t mean installing more service packs on aged versions of IE 6, but truly upgrading to the latest and greatest browser versions. The charts above show the clear advantages of this, and with shorter release cycles of browsers upgrading from Google Chrome 11 to 12 is much less daunting than moving from IE 6 to IE 7.
  • Making sure your computer has adequate processor speed and memory is very important. Because so much processing is done on the client side these days, have a 1GB or more memory and a newer computer will definitely make things faster.

Here at Sugar we are big fans of Google Chrome and Mozilla Firefox as our primary browsers, because of the performance they provide as well as the developer tools that are available to help us build a modern web application easily. How about you? What browsers are you using and why? Sound off in the comments or let us know on Twitter.


8 responses to Improving SugarCRM client-side performance: The browser

    Enrico Simonetti July 14, 2011 at 8:55 am

    On the other hand, I would suggest not upgrade too soon your browser.
    Make sure first that the newer version is going to be 100% compatible with your SugarCRM version, reading the supported versions on the release notes.


    I think these things are important, but what do you when you are servicing a chain of hospitals that are still on IE7. I also just found out that IE8 will no longer be supported.

    Nice work John as always 🙂


      I would start by illustrating all the security and usability problems of IE 7, and then point out that other vendors like Google are also moving away from older IE platforms. Or perhaps have them move to Firefox/Chrome instead.

Trackbacks and Pingbacks:

  1. Choosing the best browser for SugarCRM | Faye Business Systems Group, Inc. - July 14, 2011

    […] Improving SugarCRM client-side performance: The browser Share and Enjoy: […]

  2. SugarCRM Developer Blog » Blog Archive » Improving SugarCRM client-side performance: The server - July 25, 2011

    […] is the second part in a three part series talking about client-side performance in SugarCRM. In the first part of the series, we looked at how browser choice makes an impact on the client experience, as newer browsers are […]

  3. Long Loading Time - SugarCRM Forums - August 24, 2011

    […] […]

  4. SugarCRM Developer Blog » Blog Archive » Improving SugarCRM client-side performance: The SugarCRM AjaxUI - September 30, 2011

    […] the SugarCRM client side user experience. Previous parts of the series focused on server side and client side performance and what can be done to improve things. In this part, Senior Engineer David Wheeler […]

  5. Speed issues in Community edition - June 5, 2012

    […] […]

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s