Browser Market Share?

I hadn’t looked at my browser marketshare in a while, so I fired up Google Analytics:

Browser marketshare

Rough browser numbers are

Firefox 57.58%
IE 26.07%
Safari 6.48%
Chrome 5.11%
Opera 2.35%
Mozilla 1.44%
SeaMonkey 0.48%
Mozilla Compatible 0.18%
Konqueror 0.13%
Camino 0.04%

OneStat says that they see 0.54% share for Google Chrome. Net Applications provides an hour-by-hour graph, which is nice, but they hardwired it to look for the string “Chrome 0.2” when Chrome is on version 0.3 or 0.4 by now. Just eyeballing the Chrome 0.3 version stats, it looked like about 0.85% market share according to Net Applications. Hey Net Applications folks, any chance you’d be willing to roll up all the Chrome versions into your hourly report?

I hadn’t realized that Internet Explorer usage had dropped so low for my site (~26%). What does your browser marketshare stats look like for the last month or so for your site(s)?

P.S. Stephen Shankland writes about switching to Google Chrome because of the speed, while ExtremeTech also concluded that Chrome is speedy. And if you haven’t seen it, there’s a new version of Chrome ( that adds a couple nice features:

Bookmark manager with import/export.
Use the ‘Customize and control Google Chrome’ (wrench) menu to open the Bookmark manager. You can search bookmarks, create folders, and drag and drop bookmarks to new locations. The Bookmark Manager’s Tools menu lets you export or import bookmarks.

Privacy section in Options.
We grouped together all of the configuration options for features that might send data to another service. Open the wrench menu, click Options, and select the Under the Hood tab.

Personally, I run the dev channel version of Chrome because I like to see what cool features are coming soon. I think the dev channel has averaged weekly updates, which is really nice because you can literally watch plug-in fixes and other improvements arrive every few days. It’s wild to see client software updated that often instead of every few months.

Update, 11/28/2008: Somehow I missed the browser marketshare stats from 60K+ sites. They peg Chrome at 1.55%, with a little bit of 1.6% to 1.7% in the last week or so.

My Five Months With Google Chrome

Om Malik wrote an interesting post about Google Chrome one month after the public launch. While I was reading Om’s post, I realized that I wrote a post for the Google Chrome release that I never published. I’ll include it here, and then let’s meet at the bottom and compare notes. 🙂

Like many Google engineers, I’ve been running Google Chrome for several months. When I sat down with a blank piece of paper to write down why you should try Google Chrome, I ended up with several reasons, including speed, security, stability, and openness. I’ll run through them for you.

Speed. Google Chrome is wicked fast, especially if you use AJAX/JavaScript-heavy web applications such as Gmail. And it’s not just “benchmark fast,” it’s end-to-end fast. Google Chrome puts special emphasis on never making the user wait. Opening a tab is essentially instantaneous, and all the little pauses that would normally interrupt your workflow just don’t happen. Of course, sometimes a remote web server is slow to return data–there’s nothing that a web browser can do about that–but for everything else, the browser speeds along like lightning.

When Gmail came out, it took me months to switch over. Before Gmail, I used mutt and I had all kinds of crazy customizations and wild procmail rules, so it took quite a while for Gmail to convince me to switch. In contrast, it took less than a week for me to switch to Google Chrome. It’s so scary fast that I felt like I was taking smart pills because of all the extra work and email I could blast through.

Security. As the head of Google’s webspam team, I prowl around some pretty hairy places on the internet. Almost every day I encounter hacked pages, malware, porn, and generally scuzzy pages. The security model in Google Chrome is much stronger than most other browsers I’ve used. I’ve surfed through hundreds of seedy back alleys of the Internet over the last several months, and Google Chrome has safely kept me from being infected or affected by the junky web pages I encounter.

Stability. I loved my previous browser (and still do!), but I got used to killing my browser and restarting it daily to prevent memory leaks from hobbling my machine. I’ve run Google Chrome for weeks at a time with bunches of open tabs and it hasn’t crashed on me or bloated up my computer’s memory. I also love that Google has a “ChromeBot” which takes each new browser build and throws (put your pinky finger to your lips) one million webpages at the build as a torture test. That testing virtually guarantees that everyday web pages shouldn’t crash your browser. Google Chrome has been rock solid for me.

Openness. You aren’t locked in to using Google’s search; you can choose to use any major search engine in Google Chrome. Plus, as you click around the web, you don’t send surfing information to Google. Google Chrome is open-source under a BSD license, so you can check that for yourself. The cool bits of Google Chrome, including V8 (a from-the-ground-up JavaScript virtual machine), are open for anyone to take and use.

The comic book. Still not convinced? If you’re a geek, read the 40-page comic book about Google Chrome. It’s genuinely educational about the design choices that Google made. It turns out that a comic is one of the best ways to introduce a large piece of new software:

Ben Goodger talks about the Omnibox

You’ve all heard the acronym “RTFM,” right? It stands for Read The *cough* Fine Manual. The next time someone asks whether Google Chrome uses WebKit or something else, I can say RTFC–Read The Fine Comic. 🙂

Okay, how well does that post hold up after a month?

On speed, I think Chrome really holds up well. Om’s comments are filled with people who got hooked on the speedy and nice Google Chrome browser experience. A couple people who didn’t like it only tried it for a day; I really think you need to give Chrome a few days (maybe a week) to really notice the end-to-end difference.

On security, I was impressed that so few security holes were found, and most of them required the user to take some additional action or involved social engineering. I have seen very few (no?) attacks like “surf to a random page and your browser gets pwned.” That’s really nice to see; I’m sure the Chrome team was anxious to see what would happen when the outside world tried to attack Chrome. Chrome has been quite robust for a web browser that was only recently released into beta. I continue to surf to really dangerous places with no resulting hijacks or malware.

How about stability? I always thought this would be the weakest point of the Chrome launch, and not because of web pages that would crash Chrome, but because it’s hard to test on a wide variety of real-world hardware when you’re trying to keep a product secret before releasing it. And again, I was surprised that so few things broke. The fact that the Chrome team has released four updates to Chrome in four weeks tells me two things: 1) the worst bugs are going to get knocked down pretty quickly and 2) the Chrome team is very serious about iterating to improve the browser.

Openness is an interesting one. I think the EULA issue caused a short-term goodwill hit. Google corrected the terms in about a day, but it still provided material for the people who dislike the fundamental notion of the Chrome browser. I have to admit that I was surprised that people objected to the “Suggest” feature when you’re typing into the address bar, but it’s good that Google reacted quickly on that one as well. I had a conversation with Danny Sullivan where he urged Google employees to try to look at Google as if they were outside the company and didn’t work for Google. It’s excellent advice and definitely provides a helpful perspective. Ultimately, I think that the open-source nature of Google Chrome’s code should reassure most people and win over fans with time.

And the comic book? I still think it’s a cool way to explain a lot of complex design decisions. 🙂

I’ve been watching the Chrome team work, and I believe that they’re going to earn the respect and loyalty of a lot of surfers over time. Their ability to execute reminds me of how the Google Reader team won me over a couple years ago. If you’re running Windows and haven’t taken it for a spin, if you try Chrome for 5-6 days, I think you’ll like it too.

Where to submit Chrome feedback?

The best place to submit Chrome feedback is at

Not here (I’m going to disable comments on this post) and not over at Search Engine Roundtable. I still see a comment a day or so trickling in over there, probably because the post ranks highly for “Chrome feedback.”

Just to repeat, if you want a Chrome person to see your feedback, the best place to leave comments is at

Shiny Chrome bits, plus a fresh tip

A few neat Chrome things that I’ve seen recently:

CrossOver ported the open-source Chromium browser over to Mac and Linux using Wine. Bear in mind that this is more of a proof-of-concept and not the official version, but you can still download the binaries and play with it.

If you like the look and feel of Chrome but can’t leave your Firefox 3 extensions behind, someone made a Chrome lookalike extension so that Firefox looks like Chrome.

Or if you want to go the other direction, you can make Chrome look like Firefox3:

Chrome with a Firefox 3 theme

Lots of different places, including ChromeSpot, talk about how to do other themes, from “Galaxy” to the Boston Red Sox.

Currently Chrome doesn’t have support for extensions such as Greasemonkey that lets users do client-side modifications of web pages. But Kazuho Oku has written a neat way to get Greasemonkey-like functionality out of Chrome. Oku calls it Greasemetal. How does it work, when Chrome doesn’t support extensions yet? I’ll let the author tell you:

1. setup a local web server that sends userscripts to Google Chrome
2. launch Google Chrome specifying the browser to connect its AutomationProxy (an interprocess communication channel of the web browser implemented for automated UI tests) to Greasemetal
3. periodically execute JavaScript in each browser tab that inserts

(hat tip to Mashable on Greasemetal)

As you might imagine, all of this stuff might break in various weird and wild ways, but that’s part of the fun of tinkering. If you want to play it safer, you can read great Chrome tips from Lifehacker, Google OS, or Google Blogoscoped.

And since you’ve read all the way to the bottom, let me mention a tip that I haven’t seen widely mentioned. In Chrome, Control-V will paste from your clipboard and preserve formatting. If you use Control-Shift-V, only the text will be pasted.

Let me show you what I mean. There’s a site called Sphinn that lets you comment on search news, but the comment box allows rich formatting. In this image, I’ve highlighted a comment about Chrome and pasted the whole thing into the comment box with Control-V:

Paste of rich clipboard

Now if I only wanted to paste the raw text that I highlighted, here’s what happens when I use Control-Shift-V:

Paste of just clipboard text

This can be handy for some programs such as Google Docs that let you paste rich objects like images and formatting–but sometimes you want to paste only the text.

Google Chrome user agent

It’s easy to find out what Google Chrome’s user-agent is. Using the same trick as I did with the iPhone, I searched for phpinfo HTTP_USER_AGENT in Google Chrome. Click on one of the results and search for HTTP_USER_AGENT on the page. Here’s the image that I see:

Google Chrome useragent

My exact user-agent is

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/525.13 (KHTML, like Gecko) Chrome/0.A.B.C Safari/525.13

So “” is the current version, but that will change over time. I wouldn’t be surprised if the “525.13” value for WebKit changed too.

Update: atul points out in the comments that using “about:” or “about:version” in the address bar works well too.

Update: Someone pointed out Google’s official documentation about the Chrome user agent as well.