this post was submitted on 06 Nov 2025
483 points (98.8% liked)
Technology
76672 readers
2365 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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 /sIs 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.