Benefits from Cookie-Free Domains
That’s what Yahoo! YSlow says:
In a short example, lets say you’ve a web page with 10 background images used by its CSS file. Here’s a good practice to combine them in one or even use base64 for them, but that’s another talk. So in that scenario you’ll send all the cookies you’ve on the site with this images, but actually they don’t profit at all from this. The question is why you should send all this data with no need? Won’t you benefit from sending it with no cookies.
As it sound logical I read some articles recently describing that the benefit from putting the static content on a non-cookie domain doesn’t pays back. OK it may be strange, however every 40 ms or whatever of page load is important, aren’t they?
Setup a Cookie Free Domain
The problem is that if you’d like to setup a cookie free domain the things are becoming a bit harder. You’ve two options:
- Move all your static content on a different domain, where no cookies are set.
- Move your static content on a different sub domain and set all the cookies to the www subdomain. (Here’s a bit tricky).
All this indeed a bit tricky! So let me proceed with the next topic.
Benefits from CDN
A CDN or Content Delivery Network is a term become famous with the growing web. Now big sites have servers in almost every continent and perhaps country. CDN is an abstraction of all this. The good thing is that there’s supposed to be stored static content. Think about the YouTube’s video files. Another good thing is that this domains are cookie free by default. The thing is …
Why don’t You Combine Them?
- Read The Anchor Part of The URL … with PHP
- How to Overcome Zend_Cache_Frontend_Page’s Problem with Cookies
- Read Remote File Content-Type with Zend_Http_Client
- Scroll an IFRAME Content to a Predefined Position