Live data from Hacker News

Why are restaurant websites so awful? Because of restaurant culture.

slate.com

61–70 of 134 posts

Re: Why are restaurant websites so awful? Because of restaurant culture.

#61

Earlier quoted context omitted.

So, the question is, how do we show the restaurant owners that having a better website will increase their revenue?

Why are you so sure it will? Can you give me use cases or examples where a restaurant owner stands to make money from his site anywhere other than booking reservations possibly?

Couple off the top of my head:

1) If you have live acts performing at your establishment Friday-Sunday, the website can raise awareness.

2) Specialty products / menu items.

3) Paraphernalia / SWAG from the restaurant.

4) Take out -- order online, pick up in store.

5) If you sell things like coffee beans, web presence increases the number of eyeballs on your product.

At the end of the day, restaurants are about putting bodies in chairs and serving them food. Thus, the focus of a good website should be increasing traffic into the restaurant.

One way I could see functionality between restaurant and website would be linking time-to-wait dynamically with the website. So if I go to a restaurant's website, I could see # of people waiting and average time to wait for the evening. This does go back to putting bodies in seats, but it would better link web presence with what actually happens in the restaurant.

Re: Why are restaurant websites so awful? Because of restaurant culture.

#62
post #29
post #13

> 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. I noticed medium sized bands tended to have the same godawful outdated website style, especially European metal bands. No idea if it is still like that -- I just started avoiding any such "official" pages.

professional (especially wedding) photographers are also common culprits.

Some professional photographers say they use Flash because they want to protect their images from being stolen... despite the fact that you can screencap them?

Re: Why are restaurant websites so awful? Because of restaurant culture.

#63

Earlier quoted context omitted.

So, the question is, how do we show the restaurant owners that having a better website will increase their revenue?

Why are you so sure it will? Can you give me use cases or examples where a restaurant owner stands to make money from his site anywhere other than booking reservations possibly?

If nothing else, I think reputation is a key part of that. I know I'll look at a non-chain's restaurant's website first and if it's terrible, I seriously might not go. Especially if it's not mobile-compatible.

Re: Why are restaurant websites so awful? Because of restaurant culture.

#64

Fashion web sites, including the sites for the large brands, are just as bad as restaurant web sites. Which is even more embarrassing for an industry that's so inherently visual. Even fairly successful fashion labels will have terrible, flash-based sites with autoplay music and (often) out-of-date content, because it's too expensive or too much trouble to update the site (which probably was built lacking any kind of…

Actually, they are making changes. createthe has been transforming some high end brands towards HTML5.

Thing about fashion is that it's more about brand than usability. They get a lot of their sales from their boutiques, net-a-porter, or other 3rd parties.

Re: Why are restaurant websites so awful? Because of restaurant culture.

#65
These words make me close tab for the site I'm looking at right away: "Click to launch site". I came to your website... shouldn't it have launched already? Oh it's not a website - it's a multimedia presentation? Great. That's not what I came to your "website" for. No thanks.

(Though I have to admit, there was a time when I actively looked for those sites. I made some good money going to restaurants and other small businesses around town offering to convert their sites from un-editable flash to a simple, skin-able CMS I had whipped up. They were always skeptical until I said "never pay for changing text or prices on your site again". After that, they were my customer and no longer the customer of the wannabe-techno-hipster that sold them the original contract for site and "updates".)

Re: Why are restaurant websites so awful? Because of restaurant culture.

#67

Earlier quoted context omitted.

So, the question is, how do we show the restaurant owners that having a better website will increase their revenue?

Why are you so sure it will? Can you give me use cases or examples where a restaurant owner stands to make money from his site anywhere other than booking reservations possibly?

When I take my company out (~20-40 people depending on who's around), I need to first know whether the restaurant sells any food I can eat. If you make it hard for me to know that, I'm going to assume you don't and suggest we go either somewhere I know or some place that makes it easier for me to figure out.

Re: Why are restaurant websites so awful? Because of restaurant culture.

#68

Earlier quoted context omitted.

So, the question is, how do we show the restaurant owners that having a better website will increase their revenue?

Metrics and feedback. Here's a simple idea: create a separate google voice number for the business and put that on the website, then forward it to the existing biz line. That way you can track which business comes from the web site. Similarly, try implementing web-only specials and promotions (even if only superficially different) so you can track the effectiveness of the web site.

> create a separate google voice number for the business and put that on the website, then forward it to the existing biz line

Good idea; just make sure to check that Google Voice allows that kind of commercial use before hanging a business off it.

Re: Why are restaurant websites so awful? Because of restaurant culture.

#69

My next startup is targeting this problem. I'm pitching it as "About.me for restaurants" ... a single-page, instant setup site that has location/hours/menu/contact info. I'm planning on posting it to HN for review in a few days. If anyone wants a peak now, drop me an email.

Don't pitch it as "about.me for restaurants". I had no idea what about.me is and I'm in the startup community, read HN, TechCrunch, etc... The people you're selling to will have no idea what you're talking about. What about "Facebook for restaurants"?

I only use that analogy for startup folks and investors. Facebook definitely doesn't fit.

And, for the record, Tech Crunch has mentioned about.me tons of times: http://techcrunch.com/search/about.me

Re: Why are restaurant websites so awful? Because of restaurant culture.

#70
post #2

As someone who has built a fair few restaurant sites, there are lots of reasons. If a web design agency builds a site that doesn't work on the iPhone or iPad, which are both now considered critical to restaurant marketing, they get to charge extra for creating an iOS specific version, or an app, or whatever. If you create one site that works great on everything, you make less money. Restaurants are also sometimes run…

I have about 120 paying restaurant customers, and I couldn't agree more about the PDF menu. You could give them the slickest, easiest interface in the world, and they'll never use it. They don't have time. The PDF menu already looks good, they already put a ton of time into it to get it exactly right, and they don't want to duplicate that effort. Restaurant menus are meticulously laid out and a lot of effort is put into their creation. It would take a lot more time, and a whole lot more money than 95% of restauranteurs would be willing to put into it to create HTML menus. It would be very difficult to generate a menu creation tool that would please even a small percentage of restaurant owners, since they all want wildly different things, and are almost universally very picky about their menu.

There is exactly one reason why most restaurants have bad websites, and that is money. The average price they're willing to pay for a website is $500-1800. It's rare to hear of one paying over $2,500. It's not necessarily that they're cheap, it's that they have no money, or think they don't need it at all, so only want the bare minimum. The good restaurants don't need a website, they have a two hour wait every time it isn't raining, and the restaurants that do need a good website have no money.

Most people grossly overestimate the profitability and ease of running a restaurant. I estimate that as many as 40% of restaurants are run unprofitably in perpetuity because the economics of the location are impossible. The owner purchases the restaurant, runs it for two or three years, runs out of money, sells it to the new owner who runs it unprofitably for two or three years, runs out of money, and the cycle repeats. You probably sit in restaurants like this regularly and think, "This place must be a goldmine, it's always packed." It isn't, it's a money pit and the next guy that buys it is going to discover that as well. If you are thinking of starting a restaurant to make money, I suggest you purchase the land and build a building that can house a restaurant, then lease the space to someone else, it's the only reliable way.

Running a restaurant is also a lot more difficult than most people think, and many owners amplify the difficulty by having little or no business management experience or training. They got into it thinking it would be easy, and thought they could handle it because they've been eating in restaurants forever. Take order, cook food, serve food, simple stuff, right? Restaurant employees are always stealing from the restaurant, especially the bartenders. Customers can be very, very difficult. The staff will be flaky. There will be problems, constantly and forever. It's not easy.

Post reply on HN