Ian Davey wrote: > Greg Miller wrote: >> Last I heard, the industry averages were supposed to be something like >> 3:1 pageviews-to-users ratio and 50% repeat visitors. So the number of >> favicon 404s would be approximately 1/6 of the total number of pageviews. > > > That would only be true if every site consisted of just a single page, > which is clearly untrue. From what I've read so far, the current > implementation requests the favicon once for each domain.
Erm, no. It would be *untrue* if each site consisted of a single page. > > So you're number above needs to be divided by the average number of > pages visited by a single user on a server. You also need to take into Already did that. That's what the 3:1 figure was for. > account the average number of images/stylesheets/javascript appearing in > external files. As this should be based on resources requested, not > pageviews as that is misleading. I thought I was quite clear about the fact that this was only a matter of pageviews. I don't know of any good web-wide stats for requests or bandwidth, and I suspect no useful stats could be determined since things vary too widely. > You should probably also take into account the % of /favicon.ico > associated with domains, as those wouldn't appear as 404s (i.e. Netscape > Enterprise Server seems to come with one as default). From a bandwidth perspective, those are even worse than 404s. As I mentioned before, averages are no consolation to the people getting hit with worst-case scenarios.
