Details my top 6 techniques for reducing page load speed on SP2010 internet sites, with a focus on page-level optimisation. Also covers techniques/tools for measuring page load speed, load testing etc.
Amazon:<br />100ms improvement = 1% revenue increase! [Source: Amazon]<br />Google:<br />500ms delay = 20% loss of traffic & revenue<br />40% of consumers will wait no more than 3 seconds for a Web page to load before abandoning a retail site [Source: Forrester]<br />After 3 seconds, each additional second causes 16% drop in satisfaction [Source: Forrester]<br />Stats<br />
Key optimisation forms<br />If code/infrastructure are OK, performance issues often caused by ‘page-level’ factors, e.g. too many HTTP requests, page weight<br />Page-level optimisation<br />Code<br />Infrastructure<br />
Can cache heavily when users get same content<br />E.g. anonymous users<br />Lesser gains for personalised/collab/ security-trimmed content, but:<br />Post-cache substitution (“donut caching”) can help:<br /><asp:Substitution> control<br />SP2010 internet specifics<br />
Output caching (if appropriate, e.g. anon)<br />Little/no processing for server!<br />BLOB caching<br />Static files (images/CSS/JS/media) served from WFE filesystem + browser cached<br />Ensure max-age attribute set to avoid HTTP 304s<br />CSS sprites<br />http://CssSprites.com<br />Updating is painful <br />Optimisation top 6<br />
Several forms of optimisation<br />Page-level optimisation still required in SP2010<br />DIY approach or Aptimize<br />Measuring is key<br />Load test to establish page load speed during spike <br />Combine with PAL to analyse hardware bottlenecks<br />Summary<br />