08-15-2013, 09:27 PM
08-15-2013, 10:26 PM
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.
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.
08-16-2013, 09:12 AM
Thanks Patrick, food for thought! :-)
08-16-2013, 12:47 PM
(08-15-2013 10:26 PM)pmeenan Wrote: [ -> ]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.
+1
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.