Also, not related to the commute times, but the crime rates look strange. At least, it's showing Arlington, VA as almost completely red (very high crime). Maybe the data is right, but that would be surprising for one of the richer, more yuppified areas of the US.
If you are going to measure the distance and use that as a basis -- just report the distance. Otherwise, the estimates based on time will just flip the bozo bit in your customers.
P.S. Hi from Bedford, MA. :)
EDIT: The only time it has taken 30 minutes was when I had to wait on two trains.
And i'm not trying to give them a hard time, really. It's a neat visualization. But for me, practically, I couldn't use this to tell actual commute times, and I think that's apparent based on the other comments on here. You want my opinion? They should crowdsource taxi drivers. Who else would have a better idea what the traffic's like at any given time of day?
DC actually seemed like it went the opposite way as it usually takes an hour and a half to get from VA through the beltway into DC while the map showed only an hour for as far out as Dale City. A half hour (or more) from Petworth into Downtown during rush hour is fair, since DC has probably the slowest crappiest drivers in the nation.
Updated theory: these commute times might not be based on actual driver data, it's probably a very rough estimation based on distance, travel time, speed limit, and population. It needs to be weighted based on the curve of traffic based on time and the way locals drive. Boca commuting will probably be slower than Miami commuting on average, unless you're on the highway in which case you're totally screwed in Miami. Not to mention anywhere there's an on-ramp with lots of flow you're going to make a choke point, so times would increase a lot, unless you started after that exit.
tl;dr Traffic is hard.