Greg Miller wrote: > Jonas Sicking wrote: > >> It would be really interesting to get some hard numbers on this. Just >> looking at the current logs will not really say anything since very few >> people browse with a mozilla with this pref turned on. So we need to >> come up >> with some way to approximate the number of 404s per (for example) >> month in >> the event of a browser with, say, 30% marketshare using the current >> configuration. > > > 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. 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 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. So it should actually be: 1/(6*visited pages per server*resources per page) To fill in some numbers pulled from the air: 1/(6*10*10) So that accounts to 1/6000 resource requests. If you can come up with some numbers to fill in the above guesses then you'd get closer to the actual figure. 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). ian.
