Presentation from the October 2011 meeting of the Northern Virginia Test Automation Interest Group on testing web performance.

1. Web Performance Testing NoVa Test Automation Interest Group Patrick Meenan Twitter: @PatMeenan [email_address] blog.patrickmeenan.com

2. Front-End vs. Back-End

4. Back-End This is the HTML that largely contains the content of the page and defines the structure.

5. Front-End CSS : Layout and style Images Graphical Elements

6. Waterfall Diagram Base Page CSS Images and Graphical Elements Javascript Start Render Document Complete (onLoad)

7. Front-End vs Back-End Base Page Back-End Processing

8. Front-End: 3.2s* Back-End: 0.010s* *WebPagetest performance as measured by New Relic

9. Measuring Performance

10. velocityconf.com/velocity2011/public/schedule/detail/18039

12. US Broadband Bandwidth www.fcc.gov/document/measuring-broadband-america-report-consumer-broadband-performance-us

13. US Broadband Latency www.fcc.gov/document/measuring-broadband-america-report-consumer-broadband-performance-us

14. Bandwidth/Latency Impact www.belshe.com/2010/05/24/more-bandwidth-doesnt-matter-much/ (Fixed 60ms RTT) (Fixed 5Mbps Bandwidth)

15. Backbone Testing Actual Users

16. DSL – Back-End: 17% Backbone – Back-End: 52%

18. When is “Done”? Twitter onLoad (1.9s) Twitter end of activity (6.8s)

22. Resource Timing (draft) w3c-test.org/webperf/specs/ResourceTiming/ Timing for every network-loaded resource

23. _gaq.push(['_trackPageLoadTime']);

26. Back-End Only

27. Frontend Single Point Of Failure

29. It prevents Frontend SPOF User stares at a blank window for 21 seconds (usually < 2 seconds)

30. What it feels like

32. WebPagetest

34. From multiple locations globally…

36. What it looks like

37. What it looks like

38. What if…

39. Comparing arbitrary tests

40. The comparison