Any website needs a cookie-less domain. This (sub)domain is typically called “static”. It is used to serve Javascript, CSS, images and other static content. The reason for static content to be on a cookie-less domain is that it makes the content load faster. This argument may be counter intuitive, since cookies are small and you would not expect them to have a significant impact. But let me try to explain.
Why cookies slow you down
Cookies are uploaded with every request on a domain, although they are only read on dynamic web pages (for instance by PHP). And most visitors have asymmetric connections (like DSL) with at least a 1:10 up:down ratio. Also, uploads are often not compressed while downloads are. This is why, in terms of latency, reducing 500 bytes on upload is equivalent to reducing tens of kilobytes of download size. As Google states:
The best way to cut down on client request time is to reduce the number of bytes uploaded as request header data. So, minimize request size and serve static content from a cookieless domain. – developers.google.com
Alert: For Control Panel Help & Tutorials, click here: Panel Tutorials
