3 ms·
The details are interesting but "adds overhead at a critical time in the loading of your page" ... this seems pretty unlikely to have any noticeable processing
by nebulous1 8y ago
The details are interesting but "adds overhead at a critical time in the loading of your page" ... this seems pretty unlikely to have any noticeable processing overhead. Doing things better is generally good, but this all seems very low impact.
- __jal 8y agoDepends on where you measure it. A client on a decent connection will never notice. If you're serving billions of hits, 20 bytes in a header is something you will definitely notice on your bandwidth bill.
- tgsovlerkhgsel 8y agoMore importantly, an extra header may push you into needing another packet, which creates extra potential for packet loss.
- dijit 8y agoThat's a very weak argument to make though when regarding the modern web; sites are routinely sending me multiple megabytes of content; optimising 20 bytes isn't going to make even the smallest dent if you're trying to pack your site down.
- __jal 8y agoI'm sorry, but that's simply not reflective of reality. There's a reason Yahoo wrote yslow. 20 bytes times billions of requests is absolutely an optimization target; in fact, this is a really easy and low-hanging one at that. Sure, there's also a ton of garbage sites shoving piles of garbage around, but the existence of fast food doesn't mean nice restaurants don't exist.