[01:13:00] HTTP/2 Server Push is dead: https://developer.chrome.com/blog/removing-push/ [01:13:20] but TIL about Early Hints: https://developer.chrome.com/blog/early-hints/ [12:11:02] ori: I think if it as a workaround for the app shell conundrum. There's a notion that service workers or early flushing should be easy, flush your headers and appshell, then think about the rest and flush that. The issue is that this assumes you have no headers, status codes, or html head items that vary by page or for errors. Eg no meta tags, canonical URL, 404, 500 etc [12:11:58] This way you get to send an early repo se with some preload headers for the common case. Even if you predict wrongly, the browser will just not using the wastes preload resources same as preload already is harmless functionally [12:12:19] s/repo se/response/ [12:14:08] I'm a bit skeptical how much it saves. Some of the succes stories smell suspicious to me and i would guess they benefit mainly due to fixing unrelated problems at the same time. Presumably it is just a net-waste on subsequent page views [12:14:42] And for cdn served responses, first and secondary, also net-waste [12:15:08] For the first view of a cdn miss, it would definitely help. [12:16:57] ... assuming you're not coming from Google SERP or www portal and have disabled address bar preloading [12:17:39]