TheReturnOfPEB@reddthat.com to Technology@lemmy.worldEnglish · 7 个月前The 512KB Club is a collection of performance-focused web pages from across the Internet. To qualify your website must both be actually useful and under 512KB in size.512kb.clubexternal-linkmessage-square38linkfedilinkarrow-up1526arrow-down15
arrow-up1521arrow-down1external-linkThe 512KB Club is a collection of performance-focused web pages from across the Internet. To qualify your website must both be actually useful and under 512KB in size.512kb.clubTheReturnOfPEB@reddthat.com to Technology@lemmy.worldEnglish · 7 个月前message-square38linkfedilink
minus-squaresobchak@programming.devlinkfedilinkEnglisharrow-up4·7 个月前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?
minus-squarexthexder@l.sw0.comlinkfedilinkEnglisharrow-up5·7 个月前In an ideal world, there’s enough CSS/JS inlined in the HTML that the page layout is consistent and usable without secondary requests.
minus-squarekibiz0r@midwest.sociallinkfedilinkEnglisharrow-up3·7 个月前Those additional requests will reuse the existing connection, so they’ll have more bandwidth at that point.
minus-squaresobchak@programming.devlinkfedilinkEnglisharrow-up2·7 个月前Interesting, didn’t know that’s how modern browsers worked. Guess my understanding was outdated from the HTTP/1 standard.
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.