Menu, hours, reservations —
in that order.
Standalone restaurants, multi-outlet brands, cloud kitchens. Visitors want three pieces of information; if they’re hunting for them on your site, you’ve already lost.
Restaurant site visitors arrive with a decision already mostly made. They’ve heard about the restaurant from a friend, read about it on Zomato, or seen the place driving by. They’re on the site for a specific check: the menu (to confirm price band), the hours (because they’re trying to plan tomorrow night), or to reserve (because they decided already). Heading-only navigation that hides the menu link under “Experience” or “Discover” is the classic example. The visitor doesn’t want to discover; they want the menu.
What restaurant sites need above the fold on mobile
- Today’s hours, computed from the current date and time. “Mon–Sat: 12–3, 7–11” is wrong; “Open now until 11:00 PM” is right.
- A “Reserve” or “Order” button. One large, one secondary. OpenTable or Resy for reservations, and your own ordering link rather than only a delivery app.
- The location: embedded Google Maps, not a static image of a map. People click through to get directions.
- A phone number, tap-to-call. Many visitors still want to phone, particularly older customers.
Should we publish prices on our menu page or not?
Always, almost without exception. The visitor without price information bounces faster than the visitor with a price they decide is too high. The only sector where hiding prices on the menu page is defensible is ultra-premium fine-dining where the price is implicit in the brand positioning and a number on the page would undercut the experience — but even then, the wine list usually has prices. For everyone else: list the prices, include the small disclaimers about taxes and service charge, move on.
Building for restaurant?
Let's talk specifics.
Tell us what you do. We'll come back with three questions and one honest take.
Replies within a few hours. Prefer WhatsApp? Message us there.