Four Things, In This Order
Someone is standing on a street with a phone, deciding where to eat in the next twenty minutes. They want the menu, whether you are open, where you are, and how to book or order. That is the entire job of a restaurant website. Most restaurant sites answer those four questions somewhere, but slowly, behind an intro animation, under a hamburger menu, or inside a PDF. Fixing the order in which those four things appear does more for bookings than any redesign of the atmosphere.
The First Screen, on a Phone
- What kind of food and where you are, in one line. "Neapolitan pizza in the old town" beats a full-screen video of a chef's hands
- Today's opening hours, as words. Not a weekly table the guest has to parse — "Open until 23:00 today"
- A tappable phone number. On mobile it should dial, not select text
- Menu and Book as two visible buttons, above the fold, always
- The address with a working map link that opens the guest's own maps app
The Menu Mistake That Costs the Most
A menu as a downloadable PDF is the single most damaging thing on a restaurant website. It downloads slowly on mobile data, opens in a separate viewer, requires pinch-zooming to read, and search engines cannot use its contents to match anyone looking for what you serve. Put the menu on the page as real text and images. Group it by course, show prices, mark what is vegetarian or allergen-relevant, and make it something you can update yourself in two minutes when a price changes. A menu that is out of date is worse than no menu — the guest arrives expecting one price and meets another.
If a hungry person on mobile data cannot read your menu in ten seconds, you have not lost a page view. You have lost a table.
Photography Is the One Thing Worth Paying For
In this industry, the photos are the product page. Guests decide with their eyes, and the difference between phone snapshots under fluorescent light and one proper session is measurable in bookings. Shoot the food you actually serve on the plates you actually use, plus the room with people in it. Empty rooms photograph as cold. And keep the files under control — an unoptimised gallery is the number one reason restaurant sites are slow, which brings you straight back to the guest who left.
Booking and Ordering Without Friction
- Booking should take name, phone, time, party size. Nothing else. Every extra field loses people
- Confirm instantly on screen, and again by message. Silence after a booking form makes guests call anyway, or book elsewhere
- If you take orders, let delivery times and zones be something you control, because they change by season and by night
- Show honestly what is and is not available now. A form that accepts an order you cannot fulfil costs you the guest permanently
- Test the whole flow yourself once a month, from a phone, and confirm the notification actually arrives
On a food delivery project I built, the part that mattered most was not the catalogue or the payment integration — it was letting the owner reshape delivery windows themselves as the season changed. Restaurant logic changes weekly, and a site that requires a developer for that is a site that quietly goes out of date.
Being Found in the First Place
- Your map listing does more work than your website for discovery. Keep hours, photos and phone number identical across both
- Add structured data for your restaurant, menu and opening hours so search engines can show them directly
- Name the cuisine and the neighbourhood in your page titles — that is what people search
- Answer the practical questions on the site: parking, high chairs, dogs, large groups, dietary options. These are searched constantly and almost never answered
- Keep holiday and seasonal hours current. Wrong hours during a holiday costs a full service
What to Remove
Cut the intro animation, the autoplaying music, the full-screen video that loads before anything readable, and the long story about the founder's journey on the homepage. None of it survives contact with a hungry person on a slow connection. The founder's story is worth telling — on its own page, for the guest who already decided and now wants to like you. It is not a first screen.
Conclusion
Do this test on your own site: open it on your phone, on mobile data, standing outside. Time how long it takes to read a main course price and tap to call. If it is over fifteen seconds, that is your entire brief. Atmosphere matters in a restaurant website — but it is what you do after the four practical questions are answered instantly, not instead of them.