Testing and Optimizing of what I call "traditional" page-based web applications is not too hard to do. You simply test the individual URLs, for example the individual news section pages of CNN. When optimizing these pages we follow the recommendations of tools such as dynaTrace AJAX Edition, YSlow or PageSpeed which focus on optimizing the initial page load time by applying common Best Practices.

This is great for traditional web sites but doesn't work anymore for modern Web 2.0 Applications that provide most of their functionality on a single page. An example here would be Google and their apps like Search, Docs or GMail. Only a very small time is actually spent in the initial page load. The rest is spent in JavaScript, XHR Calls and DOM Manipulations triggered by user actions on the same URL. The following illustration gives us an overview of what part of the overall User Interaction Time actually gets analyzed with the current Best Practice Approach and which parts are left outside:

>> Read the full blog from Andreas Grabner on how to automate testing and optimization of Web 2.0 Applications

Not Logged In? Customers and AJAX Edition Users Login with your Community Account