Vote 2020 graphic
Everything you need to know about and expect during
the most important election of our lifetimes

Why Do Restaurant Websites Suck?

Illustration for article titled Why Do Restaurant Websites Suck?

Slate's Farhad Manjoo did a piece recently taking restaurant websites to task for being so awful most of the time. Flash-heavy and obsessed with entertaining instead of informing, they're often murder on the eyes. But why? Probably because designers get paid so well to do it.


While there are some choice exceptions out there, the impotent whiz-bangery of a lot of these sites—the sweeping slideshows, endless ambient music, and chef bios you never read—is likely a calculated cash grab on the part of site designers. Firms like 160over90 tend to prey on the sensibilities of older, less-web-savvy restauranteurs who want their brand to scream "PASSION," and get paid big bucks for more labor-intensive albeit useless flash sites.

But you don't go to a restaurant site to read about passion. I know a few where you could... No. You go to find a meal. Something services like Yelp and MenuPages are more than happy to provide. Meanwhile, restaurants lose more money in the process. Designers HAVE to know this. Surely they eat. They know what a pain these pages can be. But making a fatter paycheck probably outweighs being useful to consumers. [Slate]


Image Credit: CREATISTA/Shutterstock

Share This Story

Get our newsletter



I don't understand why even the greediest designer can't both design a bloated, shitty, cash-grabbing website AND build in easy access to location info, menus, hours, specials, and contact info. I mean, fucking hell, it's perfectly possible to go nuts in designing the layout of the menu—embed flash animations of each menu item, I don't care, just let me find out where you are, how to call you, and what I can eat there.

And a quick scroll down shows that the relevant Oatmeal comic has already made an appearance on this page, so I'll restrain myself.