Download to read offline
Uploaded byJeff Costa
Drop Your Website Load Times Down a Waterfall
This document discusses techniques for improving website load times using waterfall diagrams. It begins by explaining what a waterfall diagram is and how to create and read one. It then discusses using waterfall diagrams to analyze fields and advanced options. The document recommends avoiding anti-patterns that can slow load times. Finally, it discusses specific techniques like reducing page weight, minimizing round trips, speeding up browser rendering, and avoiding SSL latency and errors. The overall goal is to extend security and protect against attacks while decreasing load times.
Drop Your Website Load Times Down a Waterfall
- 1. Drop Your WebsiteLoad Times Down A Waterfall @zoompf @cosjef
- 2. (In No Way)Certified Experts Billy Hoffman Founder, CTO @ Zoompf billy@zoompf.com @zoompf Jeff Costa Sales Engineer @ Akamai jecosta@akamai.com @cosjef
- 6. What is aWaterfall? • How to read one? • How to create one? Audience Waterfalls • Fields to use • Advanced options • Video Well-Known Waterfalls • Review Pizza Hut waterfall diagram Wicked Waterfalls • Waterfall anti- patterns • Don’t do these things. Agenda The Plan
- 7. Avoid data theftand downtime by extending the security perimeter outside the data-center and protect from increasing frequency, scale and sophistication of web attacks. Breaking Down A Web Request
- 8. What’s the FrontEnd? Back-end Time to generate and send HTML Front-end Everything that follows
- 9. Important Timers Start RenderOnLoad Event
- 10. Avoid data theftand downtime by extending the security perimeter outside the data-center and protect from increasing frequency, scale and sophistication of web attacks. Problems Latency: every request/response round trip incurs a latency penalty. Payload: page size increasing; last mile bandwidth varies wildly. Rendering: browser rendering and parsing takes time.
- 11.
- 12. Make Fewer RoundTrips
- 13. “The fastest requestis the one you don't have to make.” -Steve Souders “Every HTTP request you make should be well justified, and not taken lightly.” -Jeff Costa
- 14.
- 15. What Happens tothe Waterfall?
- 16.
- 17. Errors Hurt YouTwice
- 19. THANK YOU! Q? @zoompf @cosjef BillyHoffman billy@zoompf.com Jeff Costa costa.jeff@akamai.com
Editor's Notes
- #4 Igauzu Falls - Brazil
- #5 Niagara Falls
- #6 Niagara Falls
- #8 Made up of the socket connection time, the time taken to send the HTTP request, and the time taken to get the first byte of the page. TTFB is everything after the HTTP request - the duration from the user making an HTTP request to the first byte of the page being received by the browser.
- #10 Start Render: point of time when the browser starts to render and display the content - browser has enough info to start drawing the page.OnLoad Event: user perceives page is ready and can begin interacting with itDocument Complete:point of time when the browser finishes loading all content except objects that are triggered by Javascript execution
- #11 Page size is increasing due to images, analytics, ads, social sharing.Delivering static content to the browser consumes >85% of page load time. Staticcontent is the biggest cause of poor performance in modern web applications.
- #12 FEO techniques are designed to reduce page weight without changing visual quality or site functionality. Smaller stuff
- #13 “Less Stuff”
- #15 “Build It Faster”