Šime Vidas DM’d me the other day about this thread from subzey on Twitter. My HTML for favicons was like this:
<!-- Warning! Typo! --> <link rel="icon" href="/favicon.ico" size="any"> <link rel="icon" href="/favicon.svg" type="image/svg+xml">
size is a typo there, and should be
sizes. Like this:
<!-- Correct --> <link rel="icon" href="/favicon.ico" sizes="any"> <link rel="icon" href="/favicon.svg" type="image/svg+xml">
And with that, Chrome no longer double downloaded both icons, and instead uses the SVG alone (as it should). Just something to watch out for. My ICO file is 5.8kb, so now that’s 5.8kb saved on every single uncached page load, which feels non-trivial to me.
Šime noted this in Web Platform News #42:
SVG favicons are supported in all modern browsers except Safari. If your website declares both an ICO (fallback) and SVG icon, make sure to add the sizes=any attribute to the ICO <link> to prevent Chrome from downloading and using the ICO icon instead of the SVG icon (see Chrome bug 1162276 for more info). CSS-Tricks is an example of a website that has the optimal icon markup in its <head> (three <link> elements, one each for favicon.ico, favicon.svg, and apple-touch-icon.png).
That note about CSS-Tricks is a bit generous in that it’s only correct because my incorrectness was pointed out ahead of time. I think the root of my typo was Andrey’s article, but that’s been fixed. Andrey’s article is still likely the best reference for the most practical favicon markup.
Lately I’ve been using Real Favicon Generator and I saw that the for
<link rel="icon">they use a png icon instead of an svg; I guess it’s for compatibility with browsers?