Damn I was actually gonna add more context to my original comment about how QUIC is an overrated in place UDP upgrade for HTTP, but I didn’t wanna open my mouth because I haven’t read the QUIC spec.
Thank you for this lol
spoiler
Sliding windows are for losers, spam packets at gigabit rates or go home /s
Is it just the HTML that should be under 14kb? I think script, CSS, and image (except embedded SVGs) are separate requests? So these should individually be under 14kb to get the benefit?
14kB club: “Amateurs!!!”
https://dev.to/shadowfaxrodeo/why-your-website-should-be-under-14kb-in-size-398n
Something something QUIC something something
I actually read the link and they mention QUIC
Damn I was actually gonna add more context to my original comment about how QUIC is an overrated in place UDP upgrade for HTTP, but I didn’t wanna open my mouth because I haven’t read the QUIC spec.
Thank you for this lol
spoiler
Sliding windows are for losers, spam packets at gigabit rates or go home /s
Is it just the HTML that should be under 14kb? I think script, CSS, and image (except embedded SVGs) are separate requests? So these should individually be under 14kb to get the benefit?
In an ideal world, there’s enough CSS/JS inlined in the HTML that the page layout is consistent and usable without secondary requests.
Those additional requests will reuse the existing connection, so they’ll have more bandwidth at that point.
Interesting, didn’t know that’s how modern browsers worked. Guess my understanding was outdated from the HTTP/1 standard.