Website for restaurants: 9 must-have features
We analysed 40 hospitality websites in the UK and Poland. Most looked decent. Most also had empty tables on a Friday evening. The features below are the difference between a site that fills seats and one that just exists.
1. Online reservations (actually integrated, not a phone number)
A "book a table" button that opens a phone number is not a booking system. 68% of diners under 40 prefer to book online. If they cannot, they book elsewhere. Use ResDiary, OpenTable or a simple form that sends a confirmed email.
2. Menu as a web page, not a PDF
PDFs do not render well on mobile, cannot be indexed by Google, and kill page speed. Put your menu in HTML. Update it without touching a developer. Google can read it. Customers can find "vegan options near me" and land on your menu page.
3. Hero photo that shows actual food
Stock photos of generic pasta. Restaurant clients love them. Customers hate them. Real food photos, professionally shot, convert 3× better than stock. If budget is tight: smartphone + natural light + a food stylist for one afternoon.
4. Opening hours in schema.org
Google displays opening hours directly in search results and Google Maps. They come from schema.org LocalBusiness markup in your HTML. Without it, Google guesses — and guesses wrong. "Closed" in search results when you are open is a conversion killer.
5. Google Maps embed + link to Google Maps directions
Not just a static image. An actual interactive embed plus a "Get directions" button that opens Google Maps. On mobile, this launches the Maps app directly. Friction removed.
6. Allergen information
UK food businesses are legally required to declare 14 major allergens. Having them clearly on your website (not just on a laminated card) reduces phone calls and improves trust with customers who need to know before they commit to a booking.
7. A page for private events and group bookings
A dedicated page for "Christmas parties", "private hire" or "corporate events" with a specific enquiry form generates high-value bookings year-round. Most restaurant sites bury this in the contact page or do not have it at all.
8. Speed: under 2 seconds on mobile
People decide where to eat based on a Google search, often in the street. Your page needs to load in under 2 seconds on a 4G connection. Test it now with PageSpeed Insights. If you are below 50 on mobile, you are losing bookings daily.
9. Social proof above the fold
Five stars from Google, a TripAdvisor badge, a pull quote from a real customer. Not buried in the footer — on the homepage, visible before the fold on mobile. Restaurants are a trust business. The moment someone lands on your site, they are looking for reasons to book. Give them one immediately.