I’ve linked to Steve Sauders‘ webcasts on website performance optimization before. Here’s another. Turns out that he’s co-chairing the O’Reilly Velocity conference in June.
More Web Performance Tips From Steve Souders
Hearing Steve Souders at WordCamp last week got me thinking about website performance, so I went looking for more. The slides from his WordCamp talk are online, but he gave a similar talk at Google I/O which got videotaped and posted richer detail than his slides alone will ever reveal.
Also on his blog: Use the Google AJAX Libraries API when you don’t have a CDN, and a post that asks why make users wait to download all your javascript before they see the page if you’re only going to use 25% of it at first?
Steve Souders On Website Performance
Steve Souders: 10% of the problem is server performance, 90% of problem is browser activity after the main html is downloaded. He wrote the book and developed YSlow, so he should know.
JavaScripts are downloaded serially and block other activity. Most JavaScript functions aren’t used at OnLoad. We could split the JS and only load essential functions up front, and load all the rest later. How much might that help? He says 25% to 50%. This quickly gets complex, but he’s got a simple plan that considers three questions:
- Is the script URL on the same host as the main HTML?
- Should the browser indicate it’s busy, or not?
- Does script execution order mater?
And at that point things started to get too interesting to take publishable notes. I clearly need to pay more attention to this guy.
Stats he mentioned without being specific about the source:
- Google: 200ms longer download time cut revenue by 20%
- Yahoo: 100ms of latency costs … big.