Working HTTP/2 prioritization is critical for web performance. Even though most servers, content delivery networks (CDNs), and load balancers technically support HTTP/2 prioritization, it’s effectively broken and has no practical effect. When prioritization is broken, the impact on end-user performance can be dramatic and lead to tens of seconds of delays in rendering the critical content on the page.
Patrick Meenan shares some background on how he initially stumbled on the problem with Cloudflare’s HTTP/2 deployment, the root causes of the issue, and how Cloudflare fixed it. That was just the tip of the iceberg, though, and led to building a test suite that can test for working prioritization. Every deployment he tested was broken. You’ll use the test suite, find known issues, and learn resolutions for various platforms and how you can detect and resolve the issue with your own deployments. Finally, Patrick touches on the state of prioritization support in the browsers and upcoming changes with HTTP/3 and how that will impact the issue (or not).
Patrick Meenan is a software engineer at Facebook, where he’s helping make the web faster. Patrick has been working on web performance in one form or another for the last 25 years. Previously, he worked at Cloudflare and Google to make Chrome and the web faster. Patrick created the popular open source WebPageTest web performance measurement tool, runs the free instance of it at WebPagetest.org, and can frequently be found in the forums helping site owners understand and improve their website performance.
Help us make this conference the best it can be for you. Have questions you'd like this speaker to address? Suggestions for issues that deserve extra attention? Feedback that you'd like to share with the speaker and other attendees?
Join the conversation here (requires login)
©2019, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • firstname.lastname@example.org