What a restaurant website needs, and what it does not
Almost everyone arriving at a restaurant website wants one of five things, and a site that answers those quickly beats a more impressive one that hides them.
What do people actually look for on a restaurant website?
The menu, the opening hours, where you are, how to book, and how much it costs. Nearly every visit is one of those five.
They should all be reachable without scrolling past a full-screen video. The video is for people who already decided to come.
What is not worth paying for?
Full screen autoplay video, elaborate scroll animation, a separate mobile site, and anything that delays the menu. They add load time and remove nothing from the list above.
Speed is a hospitality feature, not a technical one. People check restaurant sites outdoors on patchy signal, and a site that takes six seconds loses them to whoever loads in two.
Does a restaurant need online booking on its own site?
If you take bookings at all, yes, and it should handle the party sizes you actually get. A widget that stops at six when you seat twelve sends your best enquiries to the phone nobody can answer.
If this is your trade
Restaurants and hospitality →