4 ms·

I'm sure you know but you could inline the favicon with a data: uri scheme if you wanted to go completely self-contained <link href="data:image/x-icon;base64,i

• samatman 5y ago
  I for one 'knew' this but had forgotten, as is so easy with this kind of trivia. These little pro tips are a big part of what keep me coming back to the site, and there's always someone who didn't know. The disclaimer is of course polite, I'm just saying thanks.
  • pests 5y ago
    I originally added that phase for polite reasons too, hope I didn't come off as preachy or egotistical. I always fret about teaching topics like these lest I come off as a know-it-all.
• sdfhbdf 5y ago
  I'm pretty sure browsers are gonna request /favicon.ico anyway.
  • pests 5y ago
    Browsers gotta browse. They can request but you don't have to respond.
  • abathur 5y ago
    It vexes me (though, not as much as the apple variants). The date the last ~active browser stops requesting favicon.ico if one was already inlined would make a good betting pool.
    • pests 5y ago
      Eh, its probably never going to happen. I'm sure less than 1% of sites would serve a favicon via data uri not to mention racing the favicon along with the domain on first visits speeds up the process. Favicons are already transferred a lot. Back in the day having notifications / unread counts in the favicon itself was very common. It would show up in the tab bar and also the bookmark icon so it was a quick micro-communication channel with a website before all the modern things.