6 ms·

> The import feature of CSS results in additional, serial requests, which are very not good. I'm not sure about that. HTTP2 server push seems to fix this: htt

• abdusco 5y ago
  Server push is deprecated. - https://groups.google.com/a/chromium.org/g/blink-dev/c/K3rYLvmQUBY/m/vOWBKZGoAQAJ?pli=1 https://groups.google.com/a/chromium.org/g/blink-dev/c/K3rYL... - https://evertpot.com/http-2-push-is-dead/ https://evertpot.com/http-2-push-is-dead/
• la_fayette 5y ago
  The networking overhead of serial requests would be reduced by multiplexing in Http2, i.e., multiple http requests/responses can reuse the same tcp connection in parallel...
  • bawolff 5y ago
    I dont think that helps much in this case (or not any more than http/1.1 keep-alive did).
    • la_fayette 5y ago
      Multiplexing is completely different from keep-alive. With http2 a web browser requires one tcp connection per website as communication is in parallel, approaches like conncatenating several css files into one have no use with http2 anymore! Http1 keep-alive allows reusing the same tcp connection for sequential requests/responses only.
      • bawolff 5y ago
        Oh i know, i just don't think it helps in this situation, as waiting on the tcp connection is not the hold up in this situation.
• bawolff 5y ago
  I dont think server push is a thing anymore, but preload hints (<link rel=preload) might work just as well for this usecase.