ABCs of Webpagetest ( WPT )
Download as PPTX, PDF0 likes206 views
The document introduces WebPageTest (WPT), a tool for analyzing web page performance through visual progression, with a focus on practical usage rather than features. The talk emphasizes the importance of scripting for authenticated analysis and comparing page performance using tools like filmstrip view and asset waterfall. Key concepts include unique test runs, URL parameter passing, and the need for privacy and security when storing test results on the server.
ABCs of Webpagetest ( WPT )
- 1. ABCsofWebpagetest(WPT) By Oliver Tse January 10, 2016
- 8. Bytheendofthistalk,you’ll Perform authenticated analysis Compare performance with any page Create initial, repeat and subsequent views
- 17. Youneedscripting
- 32. Anatomyof“FilmstripView” 1.Filmstrip 2.Asset waterfall 3.CPU - “Browser Main Thread” 4.Visual progress 5.Bar charts
- 34. Filmstrip
- 35. AssetWaterfall
- 37. Visualprogress
- 38. Timings
- 39. requests
- 40. Weight
- 43. Keyconcepts 1.Each run is unique 2.URL parameter passing 3.Scripting
- 45. Atypicaltest 1.Run number 2.Initial view 3.Repeat view 4.“Steps” 5.Custom label
- 50. Demo Initial Repeat View Comparison Oz Initial Oz Repeat Neptune Initial Neptune Repeat Facebook Initial Facebook Repeat
- 56. SubsequentViews
- 57. “Beaware…” Runs/tests are always stored on the server Always make your tests private Always check “Script includes sensitive data” Always invalidate your cookie session ( logoff )
- 59. ThankYou!
Editor's Notes
- #5: This includes videos
- #8: Be an effective WPT user
- #20: setCookie and navigate
- #21: Much of what you do is setting cookies
- #22: setCookie and navigate
- #24: Commands must be tab delimited!
- #25: Sniff for cookies in the base document request; all the interesting things require authentication
- #26: Look at request headers. Find cookie.
- #28: For FB, cookies act, fr, lu, s and xs change upon logout.
- #29: Cut and paste the script. Run it!
- #30: Click on “Filmstrip View”
- #31: Filmstrip is important. It’s where you do most of your analysis.
- #33: Bar charts includes timings, requests and weights
- #34: Create a new slide with FB!!
- #35: Visually Complete - The first time when the page becomes 100% visually complete Last Change - Time of the last visual change on the page Document Complete - The time from the start of navigation until the onload event was fired ( “as measured by WebPagetest, not Navigation Timing” ) Fully Loaded - The time from the start of navigation until network activity finished after the onload event
- #36: Assets. Network.
- #37: Browser Main Thread and Page is Interactive only shows for Chrome
- #38: How the page is visually progressing through time.
- #39: Speed index - Average time at which visible parts of the page are displayed in milliseconds and is dependent on view port size Time to title ( T2T ) - Time ( ms ) from the start of the operation until the browser tab title changes
- #40: Number of requests by asset type
- #41: Page weight categorized by asset type
- #42: Compare!
- #43: Compare!
- #44: #2 is the manipulation of the URL
- #45: The ID is unique
- #49: To compare two tests, concatenate the IDs along with run number, initial view and custom label.
- #51: Demonstrate Concatenate IDs Relabel Video/speed comparisons
- #52: Demonstrate clickAndWait scripting Hit all pillars