Slashdot Mirror
Accurate Browser Statistics?
zyl0x asks: "A co-worker of mine has been made responsible for a large web application for our software product, and he was having a hard time deciding what functionality to implement, and whether or not to sacrifice functionality for a larger user base. With Walmart's harsh stand on browser compatibility, we got to thinking, exactly how many users would we be alienating by using some IE-only functionality on our website? We tried crawling the internet to get some current, accurate browser usage statistics, but we could only find stats for specific websites. I thought I'd try sending Google a request, since we imagine they'd have the lowest-common-denominator in terms of types of users, but I received an email from their press department telling me that they 'don't make that kind of information available.' Where can one get a current, accurate, and un-biased measurement of browser usage? Is it even possible?"
Browser marketshare varies widely according to audience. And by audience I mean not just people's interests, but their geographic location. Opera is used more in Europe than North America. Firefox is used more by visitors to techie sites than by visitors to entertainment sites. I've got one site where Firefox accounts for 20% of visitors, second to IE at 70%, and another where Firefox is #1 at 44% and IE is #2 at 40%.
Firefox, the second-most-used browser, seems to have a marketshare of 10-20% depending on where you look. So you'll probably be blocking at least 10% of potential users, if not more, by restricting your site to IE users only. And that percentage continues to grow.
Keep in mind also that IE is only available on Windows (not counting emulation, which is of limited use). The Mac version has been discontinued. Unless you want to block all Mac users, you'd better provide at least Safari or Firefox compatibility.
Also, any site that already restricts browser access is going to have skewed results, because the potential audience using other browsers has either cloaked their browser to look like the supported one, or has gone somewhere else.
Since you say this is a new application, you'll want to get statistics from a similar product that works cross-platform.
Unless you are Google, don't worry about what Google's browser stats are. Instead, look at the browser stats of your OWN web site. Those are your customers.
I''ll mostly refrain from talking about the monumental stupidity of using IE-only functionality because I know the Slashdot crowd will be (justifiably) beating your head in over that momentarily. Good luck with that.
Is 1% of your expected revenue greater than the implementation costs of supporting multiple browser platforms?
For almost every site out there, the answer to this question is "Yes". If you are in that situation, it would pay for you to use technology that would work on all browsers, or have a browser specific page with equivalent functionality for non-IE browsers. You often see Slashdot comments in these types of threads that say the "extra 5% of the market is too small for the company to care about". Sure, 5% seems small, but the costs of developing cross-platform support for web applications is usually so low that you're throwing away free profit by ignoring even the least-used browsers.
There are other arguments too... Many IE specific features are annoying even if you are an IE user, Using technology that isn't standardized across the industry make maintenance more difficult across platform versions, etc... But really it comes down to the money.
Take it from a site that hosts 6000+ webcomics, so you get a good sense of what's being used out there.
On average from CG, from the top of my head (not accurate!!!):
* Firefox/IE are major contenders -- ether one or the other flops back and forth the lead.
* Safari rounds out the third
* Konqueror, Opera, Netscape 4, and web spiders scrape out the distant rest.
What I would do is follow Google Mail's lead: Make a javascript version and a non-js version, and if there's a browser not on the tested whilelist, go non-js.
--
# Canmephians for a better Linux Kernel
$Stalag99{"URL"}="http://stalag99.net";
*you know: Rock and Roll all night, Party everyday! (yes, I couldn't resist)
blah blah blah
Hey, if you want to block millions of potential visitors, that's your prerogative. Personally, I'd like to keep the doors open for them.
I've always felt that online retailers who neglect the mac Web share are really making a big mistake. Say they are 5% of Web users. Which 5% are they? Well, they are the ones with disposable income who can afford to shell out more for a computer. That means you've eliminated the 40% of Windows users who are pirating it in a country that does not enforce copyright law well. When it comes to potential customers, unless you're selling a product that only works on Windows you are actually cutting out more like 10-15% of your potential customers, and it is one of the most affluent chunks of that total market. It seems like a pretty poor idea to me.
If you're even willing to entertain the idea, then why not take it to the next level? Instead of having an interactive ActiveX-heavy website, just have a website that contains one file, a MS Windows-only executable, for your "audience" to download and execute as administrator. Then you won't have to worry about "giving up functionality" at all.
(BTW, you're never going to find the statistics that you want. Having MSIE be in the user-agent header, is practically part of the defacto http standard now. Why? Exactly because of the kind of abuse that you're contemplating. 10 years after the last copy of MSIE has been erased, it will still have 90% marketshare, at least according to the server logs.)
As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
I manage dozens of websites reaching multiple demographics (i.e., business, home users, education, medical, engineering, agri-business, sporting goods). Our sites see roughly 1,000,000 unique visitors each week.
Removing bots out of the stats, on average, I see:
If your site is geared towards highly technical people, expect to see double the FireFox & Linux traffic. If the site is geared towards the average home user, you might only be pissing off 10-12% of your potential customer base by having IE only components. I can't imagine many businesses surviving very long by pisssing off 1 out of every 9 customers ... oh, wait, Microsoft ... forget I said that.
For a snapshot of the web population at large, check this site:
http://marketshare.hitslink.com/
Their stats are updated regularly, they've got a reasonable level of detail, and lots of pretty graphs.
However, as others have pointed out, you need to be worrying about your particular audience more than anything else. A site like the one I've just given isn't all that useful unless you've got a really huge web site. So here's a three step plan for YOUR web site:
1) At first, design it to work smoothly with as many browsers as you possibly can.
2) Build up a profile on the types of users who visit your site. There are lots of programs that can help you do this. Google Analytics does a decent job, and it's free of charge. Another one is Mint, which some people swear by (it costs $30 USD). There are lots of others out there, of varying quality and abilities. Take your pick.
3) Once you've got a profile built up, tune your web site to suit the abilities of the browsers that most of YOUR particular users favor. You might discover that only 0.002% of your visitors are using Safari, meaning perfect compatibility with Safari is not a major concern for you. Or you might discover that the Opera users of the world swarm your web site like ants swarm spilled sugar, in which case Opera becomes a priority for you.
Lather, rinse, repeat.
Here's the percentages for the site I work on. I can't reveal specific numbers, but we get many millions of unique visitors per day. As many other posters have mentioned, the answer of what to support greatly depends on who your audience is and what you're trying to achieve. Our audience is over 99% from the US, and represents a more average (read: less tech savvy) cross section of internet users, specifically, those that would buy shoes and apparel online. Your potential customer profile is likely much different, but here's the top 10 browsers/platform combonations we saw last week:
44.93% - Internet Explorer 6.0 Windows XP
26.48% - Internet Explorer 7.0 Windows XP
5.26% - Firefox 2.0 Windows XP
4.90% - Firefox 1.5 Windows XP
3.98% - Internet Explorer 6.0 Windows 2000
2.29% - Safari 419 Macintosh PPC
1.82% - Safari 419 Macintosh Intel
1.39% - Internet Explorer 6.0 Windows 98
0.92% - Safari 312 Macintosh PPC
0.52% - Firefox 1.0 Windows XP
We do our best to support normal operation on all of these platforms (and several others) because at our volume alienating even a fraction of a percent costs real money. And also in our case it's not hard to make things work cross browser because we use simple HTML and minimal javascript.
You ask what you lose by adding some IE only features. The equally important question is what you gain. Are the IE only features you're considering going to increase the value of your application enough to make up for what is lost in potential users? Maybe it is, maybe it isn't. In general I think people overestimate how much fancy features are going to improve usefulness, so be honest with yourself there. Good luck figuring out where to draw the line.
Cheers.