Warning if HTTP/2 pushed items are not collected |
|||||
Issue descriptionWe currently show a warning in the console if link rel=preload items aren't collected after a couple of seconds. Feels like we should do the same with HTTP/2 pushed items. I guess this is a little more complicated because pushing is per connection, not per page. Ideally the warning would be shown in the console of the page/worker that made the original request. This would help developers identify suboptimal push management, just as they can with link rel=preload.
,
Aug 31
This is becoming more of an issue the more the wisdom about H/2 Push spreads. Please see this [WPT trace](https://www.webpagetest.org/video/compare.php?tests=180829_DW_39345dfbf7f7208689625bfbbe2b663e-r:1-c:0) and the attached screenshot both courtesy of jshannon@ for a more visible example. It would indeed be great if this could be surfaced as a warning.
,
Aug 31
My hypothesis (and concern) is that as H2 push becomes better known and better supported then companies will start implementing it. While I expect (hope) that there are some automated build tools or maybe web server tools to choose the best assets to push and keep those lists up to data (a la Workbox for SW), many companies will do a manual analysis and hardcode the push list. Which could lead to: * Suboptimal setups. The screenshot is for an AMP page; the server is pushing > 250kb of libraries and CSS which may be optimal for some of their pages, but won't be requested by their AMP pages. * Outdated setups. It's only a matter of time before someone forgets to update these manually hardcoded lists. Best case, the server will just push a bunch of 404s.
,
Aug 31
,
Sep 3
,
Dec 4
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by tsteiner@google.com
, Aug 31