FavIcons and 404 Errors
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.
![CSS Animations Between Media Queries]()
CSS animations are right up there with sliced bread. CSS animations are efficient because they can be hardware accelerated, they require no JavaScript overhead, and they are composed of very little CSS code. Quite often we add CSS transforms to elements via CSS during...
![fetch API]()
One of the worst kept secrets about AJAX on the web is that the underlying API for it, XMLHttpRequest, wasn't really made for what we've been using it for. We've done well to create elegant APIs around XHR but we know we can do better. Our effort to...
![Morphing Elements Using MooTools and CSS]()
Morphing an element between CSS classes is another great trick the MooTools JavaScript library enables you to do. Morphing isn't the most practical use of MooTools, but it's still a trick at your disposal.
Step 1: The XHTML
The block of content that will change is...
![:valid, :invalid, and :required CSS Pseudo Classes]()
Let's be honest, form validation with JavaScript can be a real bitch. On a real basic level, however, it's not that bad. HTML5 has jumped in to some extent, providing a few attributes to allow us to mark fields as required or only valid if matching...
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.
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).
I don’t think the 404 error message takes more bandwidth than the blank favicon file…
@amos
Im not sure about the size but for sure it will be faster with the blank favicon.
@amos
it is a 404 error page has: 289 B
the transparent favicon hast: 22 B so should be 13 times faster !
Good one, especially useful for sites that have custom 404’s like WordPress, which not only wastes bandwidth but processing power.
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.
Cheers.
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 :)
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.
Broken download link
@seedan you need to right click on link to download the favicon.