FavIcons and 404 Errors

By  on  

As you probably already know, adding a favorite icon to your website is a great way to add subtle branding to your website. It's an easy, one-time update to your website that you never need to think about once it's done.

Lets say you don't care about the favicon or don't have a logo to use as a favicon. Since each browser looks for a "favicon.ico" file when no favicon is assigned, your server may throw off 404 errors on every site visit. What a bunch of wasted bandwidth and server strain!

The solution is to use a blank favicon file. It's tiny in size, prevents the useless 404 error, and decreases load on the server. Don't have a blank favicon file? I do. Click here to download it.

Recent Features

  • By
    JavaScript Promise API

    While synchronous code is easier to follow and debug, async is generally better for performance and flexibility. Why "hold up the show" when you can trigger numerous requests at once and then handle them when each is ready?  Promises are becoming a big part of the JavaScript world...

  • By
    Responsive and Infinitely Scalable JS Animations

    Back in late 2012 it was not easy to find open source projects using requestAnimationFrame() - this is the hook that allows Javascript code to synchronize with a web browser's native paint loop. Animations using this method can run at 60 fps and deliver fantastic...

Incredible Demos

  • By
    HTML5 Datalist

    One of the most used JavaScript widgets over the past decade has been the text box autocomplete widget.  Every JavaScript framework has their own autocomplete widget and many of them have become quite advanced.  Much like the placeholder attribute's introduction to markup, a frequently used...

  • By
    9 Mind-Blowing WebGL Demos

    As much as developers now loathe Flash, we're still playing a bit of catch up to natively duplicate the animation capabilities that Adobe's old technology provided us.  Of course we have canvas, an awesome technology, one which I highlighted 9 mind-blowing demos.  Another technology available...


  1. I think that’s interesting for development, if you want to remove the error form your logs but don’t want to make an icon at that moment. But I’d highly recommend to replace it with a real icon for the live version. favicons are really useful for bookmarks. Not only it help the visitor to find you site easily once he has associated it with the icon, but also, if it is catchy enough, it will get his attention in the middle of other bookmarks and he will be more likely to click your link when, you know, randomly browsing at work. Anyway your other article about favicon clearly says it, it’s not much work and definitely worth it. So my conclusion : if you bother adding a favicon, add a real one.

  2. Yeah, Olivier has a point regard the bookmarks. I’ve probably got a couple of hundred bookmarks in my browser (yeah, I should’ve sorted it and added many of them to Digg/Delicious), but the favicon helps be very much with navigating through my bookmarks. And just like you mentioned, favicons make your site stand out a little more when you navigate around a website.
    Overall I think you’ve come up with a good idea that I’ve never thought about, but I think it would be easier to just add a real favicon. A website’s logo works very well (most sites do have a logo anyways).

  3. I don’t think the 404 error message takes more bandwidth than the blank favicon file…

  4. @amos

    Im not sure about the size but for sure it will be faster with the blank favicon.

  5. @amos
    it is a 404 error page has: 289 B
    the transparent favicon hast: 22 B so should be 13 times faster !

  6. Good one, especially useful for sites that have custom 404’s like WordPress, which not only wastes bandwidth but processing power.

  7. Nice tip Adam surely a blank favicon would be beneficial specially after the Google Panda update.

    I was curious to know if the process of looking for a particular a page and on not finding it returns a 404 page will result in use of some other bandwidth and resources other that the weight of the 404 page which @alelo pointed out is 289B?

    @Adam you have a nice protfolio picture – I’m dying to habe one as well. Can you refer a service which does this?

    Keep up the good work.


  8. This is an interesting point Adam, thanks for raising it. I often use word press for clients and even from an aesthetic point of view this is a good idea as it will remove the CMS favicon or browser icon and swap it for – well – nothing.

    Thanks for sharing you revalation with us. I’ll pop back and see you soon :)

  9. Lucas Rolff

    Not serving a favicon, first of all returns a 404, which will be logged (which is longer than a normal get request to the favicon) bytes saved in your log!

    Also, returning a 404 is ‘expensive’ for a webserver – let’s say you have 4 files that doesn’t exist, if you have 2 million visitors a day, that extra load you add to the server, is more than you think, a lot more handling on the server is going on, but also load time on the website actually will be higher, because returning a 404 usually takes more time, than serving the request itself.

  10. Seedan Furpot

    Broken download link

  11. Sahil Mepani

    @seedan you need to right click on link to download the favicon.

Wrap your code in <pre class="{language}"></pre> tags, link to a GitHub gist, JSFiddle fiddle, or CodePen pen to embed!