RESTAURANTS · CAFES
A restaurant site that answers the question people are asking
Why a restaurant template usually falls short
What goes wrong with a generic site
- 01
The menu is a file, not a page
A PDF that has to be pinched and zoomed, and that nobody can update without going back to whoever made it. Search engines read none of it. - 02
Prices go stale
When changing a price means asking somebody, it does not get changed. The site ends up quoting last year, and customers notice at the table. - 03
Hours are wrong on holidays
A single line of opening hours cannot express a weekly closing day or a festival schedule, so people arrive at a closed door and do not come back. - 04
Bookings go nowhere
A contact form that lands in an inbox nobody watches, when the request needed to reach the person holding the reservations book within minutes. - 05
One page for every branch
Three locations sharing one address block means no branch is findable by its own area, and customers cannot tell which one is nearest.
How the site should move somebody from a search to a table
What a restaurant site needs
- 01
The menu, with prices, on a phone
Not a PDF to pinch and zoom. A page that scrolls, with prices you can change when your costs do. - 02
Map, hours and phone number
One tap opens Maps or dials. Nobody copies an address out of a paragraph. - 03
A booking or pre-order button
Wired to LINE or email, so a request arrives while the customer is still deciding. - 04
Food photography that loads
Pictures decide it, and heavy pictures lose the visitor before they appear. Sized properly.