3 ms·
> One request per icon as done in the README is extremely wasteful. That depends on the transport, this is one of the things that HTTP/2 (and HTTP/3) aim to fi
by lima 6y ago
> One request per icon as done in the README is extremely wasteful.
That depends on the transport, this is one of the things that HTTP/2 (and HTTP/3) aim to fix by downloading them in parallel in a single connection.
Watch the devtools network tab: http://www.http2demo.io/ http://www.http2demo.io/
- tleb_ 6y agoThere is still a header to send. Talking about SVG that are on average 465 bytes, a 867 bytes header (as sent by GitHub[0]) is not negligible. HTTP compresses headers though, so according to [1] we can expect ~30% header transferred size/actual size ratio which brings header transferred size to ~260 bytes. Still a 56% overhead for the average icon from this collection. [0]: https://camo.githubusercontent.com/d0518022b7a02d405ad5112a0c8aa455cbfe952e/68747470733a2f2f6564656e742e6769746875622e696f2f537570657254696e7949636f6e732f696d616765732f7376672f6769746875622e737667 https://camo.githubusercontent.com/d0518022b7a02d405ad5112a0... [1]: https://blog.cloudflare.com/hpack-the-silent-killer-feature-of-http-2/ https://blog.cloudflare.com/hpack-the-silent-killer-feature-...