The emergence and embrace of HTTP/2 in recent years has given us a new set of tools to optimize the delivery of our web pages. One notable addition was server push—the ability to proactively send assets to a browser without waiting for them to be requested.
Server push promises to put an end to the performance optimization hacks we’ve developed to overcome HTTP/1’s inefficiencies, such as inlining and resource bundling. However, is this new mechanism really the silver bullet we all thought it was? Is it time to abandon our build systems and stop bundling our assets entirely? Or are lack of server support and browser inconsistencies holding us back? Lastly, what are new specifications such as cache digests, origin frame, and the 103 status code doing to improve the situation?
Using new research and real-world examples, Patrick Hamann leads a deep dive into server push, exploring current and future best practices for loading assets in the browser. This will ultimately allow us to make better decisions when loading our web pages and lead to faster, more resilient experiences for our users.
Patrick Hamann is a web performance engineer at Fastly, where, among other things, he is helping to build a faster web for all. Previously, he helped architect some of the world’s largest media websites, including the Guardian and the Financial Times. When not speaking or ranting about performance, he enjoys spending his time discovering new food and craft beer.
©2018, 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