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?
kibiz0r@midwest.social 3 days ago
14kB club: “Amateurs!!!”
dev.to/…/why-your-website-should-be-under-14kb-in…
a
14kBpage can load much faster than a15kBpage — maybe612msfaster — while the difference between a15kBand a16kBpage is trivial.This is because of the TCP slow start algorithm. This article will cover what that is, how it works, and why you should care.
sobchak@programming.dev 2 days ago
xthexder@l.sw0.com 2 days ago
In an ideal world, there’s enough CSS/JS inlined in the HTML that the page layout is consistent and usable without secondary requests.
kibiz0r@midwest.social 2 days ago
Those additional requests will reuse the existing connection, so they’ll have more bandwidth at that point.
sobchak@programming.dev 2 days ago
Interesting, didn’t know that’s how modern browsers worked. Guess my understanding was outdated from the HTTP/1 standard.
mlg@lemmy.world 3 days ago
Something something QUIC something something
hamFoilHat@lemmy.world 3 days ago
I actually read the link and they mention QUIC
mlg@lemmy.world 2 days ago
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