Measuring web performance
Upcoming SlideShare
Loading in...5

Measuring web performance



Things to be aware of when you are measuring the performance of your web sites (both synthetic testing and Real User Monitoring).

Things to be aware of when you are measuring the performance of your web sites (both synthetic testing and Real User Monitoring).



Total Views
Views on SlideShare
Embed Views



5 Embeds 20 5 5 4 4 2



Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

Measuring web performance Measuring web performance Presentation Transcript

  • Measuring Web Performance Patrick Meenan @patmeenan
  • Types of Measurement
  • Measuring Web PerformanceSYNTHETIC TESTING
  • Active Testing• Consistent results – Good for detecting and diagnosing issues that are 100% repeatable and on pages you are monitoring• Lots of detail• Availability monitoring• Not representative of actual end-user performance – Usually tested from data centers – Sometimes co-located with CDN provider equipment
  • Bandwidth/Latency Impact(Fixed 60ms RTT) (Fixed 5Mbps Bandwidth) 5
  • US Broadband Latency WebPagetest DSL WebPagetest Cable WebPagetest FIOS Backbone
  • Actual UsersBackboneTesting 7
  • DSL – Back-End: 17% Backbone – Back-End: 52% 8
  • Mac Traffic Shaping OS X Lion + Xcode 4.1 Cable, DSL, 3G, Edge, WiFi and Custom GUI for dummynet (which has been available for a while)
  • Synthetic Browsers• Know HOW your active testing is done – Some only test the base page – Synthetic browsers usually not reflective of real browser – Real browser testing – Connectivity (backbone, last-mile)• – Synthetic Browser: 447 requests – IE 8: 241 requests
  • Measuring Web PerformanceREAL USER MONITORING (RUM)
  • Real User Monitoring (RUM)• Full coverage on all pages visited by users• Real performance information for end-user experience• No availability monitoring• No competitive reference• Limited detail – … but getting better
  • Navigation Timingwindow.performance.timing IE 9+ Chrome Firefox 9+ Android 4+ Front-End Back-End 13
  • Resource Timing (draft) Timing for every network-loaded resource
  • Back-End Only
  • Access Logs• Overall Response Times - %D (Apache)• Custom variables (app-specific timings)• Logster + graphite = graphs• Lots of data-mining opportunities – Broken links/content (404’s with useful referer information)• Mike Brittain (Etsy) Presentation – and-tools-at-etsy-11159635
  • Measuring Web PerformanceTHE METRICS
  • When is “Done”?Easy answer is onLoad But…
  • When is “Done”?Twitter onLoad (2.4s) Twitter end of activity (8.2s)
  • 2 Pages, Identical Performance …
  • Start Render Identical
  • Load TimeIdentical
  • Last Visual Change Identical
  • Visual “Completeness”
  • Measuring Web PerformanceINTRODUCING…
  • The Speed IndexThe user experience of A was 7.4 times faster than B
  • vs. Twitter …
  • Amazon vs. Twitter Amazon Twitter Speed Index 1501 6014 (+300%) onload 2.4 2.4 Fully Loaded 6.4 8.2 (+28%)
  • Measuring Web PerformanceWHAT’S NEW IN WEBPAGETEST
  • New Waterfall UI Nav Timing – domContentLoaded (Firefox/Chrome) Nav Timing – load event (Firefox/Chrome) Pop-up request details
  • Dependencies (Chrome)Line of code thatTriggered request
  • Response Bodies
  • Dev Tools Timeline (Chrome)
  • Dev Tools Timeline (Chrome)
  • Creating Videos
  • Creating Videos (cont)Customize:- End Point/Times- Specific Run- First/Repeat View- Labels
  • SPOF
  • Custom viewport size Chrome/Firefox
  • EC2 AMIsIE 7 m1.small orIE 8 c1.mediumIE 9, Chrome, Firefox (single image)
  • News/Updates• Twitter: @patmeenan• Google+ WebPagetest• WebPagetest Forums