We overclock favicon.ico - this is how?

In the next presentation, Yahoo! about client performance , a question was raised about favicon.ico . They carried out some interesting facts about this phenomenon and gave a couple of tips. I will quote their recommendations:

• www.example.org/favicon.ico
• Necessary evil:
  • The browser will request it
  • Better not to respond with a 404 error
  • Cookies will be sent.
  • Cannot be in CDN
  • Disturbed in the sequence of loading resources
• Reduce it (<= 1 Kb)
• It's never good to use animated icons.
• Set the Expires header
• Tools: imagemagick , png2ico , favicon.ru
• Study Material: Looking for Yahoo! favicon.ico takes 9% of all page views ( for webo.in is 7% )

')
Since favicon.ico not an ordinary picture when a site is loaded (it, first, it is requested almost once by the browser when visiting the site, and secondly, it is loaded, ignoring the usual order of loading), then in addition to the existing information I wanted to conduct a series of additional studies and combine all that is known to progressive humanity on this topic. However, in the course of studying the material, it turned out that the problem is not at all as transparent as initially thought. The .ico format appeared in a new, very beneficial light for use on the web.

read further on webo.in →