1. Web Site Performance What makes web sites slow? Back end Front end Tools for measuring performance Firebug / YSlow Visual Studio Test Edition W3.org html and css validators

2. Back end – Many Culprits Db queries Calls to 3 rd party systems (e.g. mainframe) Mashups of multiple sources Intensive computation Web server performance settings (IIS) Hardware, network bandwidth … Web Site Performance

3. Back end – Many Solutions DB Tuning Indexes, table joins, archiving SQL Server Profiler, Tuning Advisor IIS Tuning MaxConns, IOThreads, WorkerThreads Caching Web Site Performance

4. Caching – First Steps Identify expensive data or output Evaluate volatility Evaluate frequency of use Separate volatile data from non-volatile Choose the appropriate caching mechanism Web Site Performance

5. Caching Output Caching Data Caching Cache Dependencies Web Site Performance Demos…

6. Output Caching - OFF Web Site Performance Max User Load15 Requests/Sec7.50 Requests Failed0 Requests Cached Percentage0 Avg. Response Time (sec)2.01 Avg. Content Length (bytes)1,083 Tests/Sec7.50 Tests Failed0 Avg. Test Time (sec)2.01 Avg. Transaction Time (sec)0 Avg. Page Time (sec)2.01

7. Output Caching - ON Web Site Performance Max User Load15 Requests/Sec1,017 Requests Failed20 Requests Cached Percentage0 Avg. Response Time (sec)0.011 Avg. Content Length (bytes)1,083 Tests/Sec1,017 Tests Failed20 Avg. Test Time (sec)0.012 Avg. Transaction Time (sec)0 Avg. Page Time (sec)0.011

8. Output Caching - OFF Web Site Performance Requests/Sec7.43 Avg. Response Time (sec) 2.02 Requests/Sec1,202 Avg. Response Time (sec) 0.0088 Requests/Sec988 Avg. Response Time (sec) 0.012 Output Caching - ON Output Caching - ON (10 seconds)

9. Front end … for most web pages, less than 10-20% of end user response time is spent getting the html document from the web server to the browser. If you want to dramatically reduce the response times of your web pages, you have to focus on the other 80-90%... - Steve Souders, High Performance Web Sites Web Site Performance

10. How browsers work with HTTP 1.1 Web Site Performance Two requests at a time per hostname

11. Rule #1: Make Fewer HTTP Requests Web Site Performance Combine javascript files Combine css files Use image maps or css sprites

12. Rule #2: Use a CDN Web Site Performance

13. Rule #3: Add an expires header Web Site Performance <clientCache httpExpires="Mon, 5 Apr 2010 00:00:00 GMT" cacheControlMode="UseExpires" />

14. Rule #4: Compress the response Web Site Performance

15. Rule #5: Put the stylesheets at the top Rule #6: Put the javascript at the bottom Web Site Performance

16. Rule #10: Minify Javascript and CSS Web Site Performance

17. Rule #11: Avoid redirects Web Site Performance

18. Extras: Make sure your html and css are valid (http://validator.w3.org/) Turn off View State for controls that arent using it Web Site Performance