The Daily Parker

Politics, Weather, Photography, and the Dog

Why do restaurant websites suck?

Slate's Farhad Manjoo examines the phenomenon:

The rest of the Web long ago did away with auto-playing music, Flash buttons and menus, and elaborate intro pages, but restaurant sites seem stuck in 1999. The problem is getting worse in the age of the mobile Web—Flash doesn't work on Apple's devices, and while some of these sites do load on non-Apple smartphones, they take forever to do so, and their finicky navigation makes them impossible to use.

When you visit many terrible restaurant websites in succession, it becomes obvious that they're not bad because of neglect or lack of funds—these food purveyors appear to have spent a great deal of money and time to uglify their pages. Indeed, there seems to be an inverse relationship between a restaurant's food and its site. The swankier the place, the worse the page. Chez Panisse, Alice Waters' Berkeley temple of simple, carefully sourced local cuisine, starts with a pointless, grainy five-second clip of what looks like a scene from a Fellini movie. Alinea, the Chicago molecular gastronomy joint, presents you with a series of menu buttons that aren't labeled; you've got to mouse over each one to find out what you're about to click on.

Not all is lost. I spoke to a few restaurateurs who've created great, easy to use, elegant sites, and they all said they were motivated by one thing: They were missing out on traffic from mobile devices. The steakhouse chain Morton's, for instance, has a mobile site that uses your GPS location to get you information on the restaurant closest to you. The site loads up quickly, and lets you make a reservation in a matter of seconds. "We wanted to keep the bells and whistles at a minimum," Roger Drake, the company's head of marketing, told me.

Not only did I agree with Manjoo wholeheartedly, but I also started thinking about steak...

Comments are closed