4 ms·
More or less: yes. It's the combination of both removing those excess bytes. If you transmit 10 static files per page request, and have 256bytes of cookies yo
by symkat 16y ago
More or less: yes. It's the combination of both removing those excess bytes.
If you transmit 10 static files per page request, and have 256bytes of cookies you're sending 2560 bytes of cookies, or 2KiB per page load. That's on the end user's upload bandwidth too, which is typically dramatically less than their download.
The lessening of the connection limit also allows more entities to load at the same time, the combined effect is a good increase in speed. Two tweaks for the price of 1. =)
- asuth 16y agoIt doesn't quite work like that. TCP works in packets, so 256 bytes of cookies does not necessarily translate into an extra packet sent over the network. So if you have 10 static files per page, you might push a few of them over to an extra packet, but not all of them. It's something worth doing, but it's not the biggest win you can get.
- mattmanser 16y agoThe piece is called 'cookieless domains'. Not 'using static domains for increased connections'. If the actual speed increase is from something totally unrelated to the piece's conclusion then this is really misleading. The static domain trick has been around donkeys.