Favicon with javascript to spare a http-request

This sounds wise:



Are there any objections against doing this?

Not sure it’s worth the effort. The favicon is usually a low-priority resource that browsers load lazily after the onload and you’d be moving those bytes into some shared javascript code that is loaded earlier.

It’s a cool hack but I don’t think I’d recommend doing it on a production site unless you had a compelling need to.

Thanks Patrick, food for thought! :slight_smile:


Without even considering the overhead of jQuery suspect it has a slightly negative impact.

Still need a favicon.ico on disk as many crawlers and other tools expect it to be there.