go back to the blog

Performance testing of web applications across multiple browsers

  • 14/10/2010
  • no comments
  • Posted by EuroSTAR

Very often when we carry out performance testing of web applications, we pay attention to server side performance, whereas client side performance is left unattended .Today a large number of web browsers exist in the market unlike the earlier days when all applications used the same web browser.  End user experience can be different for users when they use the same application with diverse web browsers. Certain components, images, widgets do not get displayed properly on all browsers. Factors like java script rendering, average CPU usage under load , CSS rendering speed , browser cache performance differs  amongst web browsers.

Provided below is the comparison of five major web browsers (Mozilla Firefox 3.5, Google Chrome 3.0, Microsoft Internet Explorer 8.0, Opera 10.0, and Apple Safari 4.0) with respect to JavaScript rendering speed

(   )


So now consider, if you are performance testing a JavaScript heavy application, and we use a browser that takes a longer time to render the JavaScript, then the final response time would get compromised.   Similarly other factors like CSS rendering speed , browser cache performance could affect the end response time result.

Hence performance testing the application across the identified set of browsers in use is important as it will help us find out if web browser performance is impacting the application performance. Tools that help analyze client side statistics ( e.g.  number of http requests, redirects, use of combined style sheets , scripts  etc) can be used in tandem to analyze the overall client side performance .

And now its Twiz Time for the last time J

Web browser : Chrome :: Memory stress test tool  : ?

Blog post by

go back to the blog


Leave your blog link in the comments below.

EuroSTAR In Pictures

View image gallery