Keynote Systems - Designing for and Managing Performance in the New Frontier of RIA's - Part 3

web 2.o performance challenges

1) Javascript - every javascript file is serialized which slows down the code so don't make many external js files (minimize) and move them down in the page load because the entiere js needs to load in each js file before the page will visually load

2) Client side Processing - some major sites are more than 50% performance on client side processing compared to the time on the network. Monster.com is using 80% of it's performance on client side processing

2a) Flash Initialization - they are showing a very fast loaded flash file, but a 1s delay after that before hitting the next file to download... due to bad flash initialization

2b) JS and Css Rendering - identify and improve client side processing

3) Third party Quality - (omniture, google analytics, ad tracking, etc), if their tool fails, your browser can have a huge impact on load. Make sure you have a way of managing the third party. Put the file in the footer which will allow the page to load first, and if the third party fails you only lose the footer, not the entire page

4) Web Service Performance - establish sla's with web services

5) Flash Performance - based on how you implement flash, you can cause delays in calling next modules, etc. You also don't want to have too many modules of them