Someone is standing outside in the rain, deciding where to eat.
They have your website open on a phone with one bar of signal, and they want three things: the menu, whether you are open, and whether they can get a table.
Almost every restaurant website makes at least one of those hard to find.
Restaurant website design fails distinctively. Not through bad taste, usually, but through burying the useful information underneath a full-screen video of the kitchen and a menu that opens as a four-megabyte PDF.
Restaurant Website Design: Menus, Bookings and Speed
The menu is the entire website
Say it plainly: the menu is what people came for. Everything else on the site is secondary.
It should be a web page, not a PDF. A PDF requires a download, opens in a separate viewer, cannot be read comfortably by screen readers, pinches and zooms badly on a phone, and is invisible to search engines trying to work out whether you serve what somebody just searched for.
An HTML menu is lighter, readable at any size, accessible by default and indexable. If your menu changes daily, that is an argument for making it easy to edit rather than an argument for a PDF.
Include dietary information where you can. It is the second most common reason someone is reading the menu before arriving.
Opening times, where they can be seen
Not in an image. Not only in the footer. Not exclusively on your social media.
Put them in text on the page, keep them current, and be explicit about the exceptions people actually wonder about: bank holidays, kitchen closing times, whether you serve food all afternoon.
Search engines will surface this information directly when it is marked up properly, which means a proportion of your visitors never need to load a page at all. That is a good outcome, not a lost visit.
Booking should take one tap
Every step between intent and a reserved table loses someone.
Put the booking action where the decision happens, which is on the menu page as often as the homepage. Offer a phone number alongside the booking widget, because a meaningful share of guests will always prefer to call, and they are frequently booking the larger tables.
Test the booking flow on a mid-range phone on a poor connection. Third-party booking widgets are often the heaviest thing on a hospitality site and the least tested outside an office.
Photography, handled properly
Food photography is the content here rather than decoration, so this is not an argument for fewer images.
It is an argument for serving them at the dimensions they display at, in modern formats, with anything below the fold loaded only when needed. A gallery of twenty dishes exported straight from a camera is several megabytes that could be a few hundred kilobytes with no visible difference.
Autoplay video is the exception worth removing outright. A looping clip of the dining room behind your headline delays everything a guest actually wants and, on a weak connection, prevents the page from loading at all.
Where speed and impact meet
Where performance and environmental impact both apply, treat them as the same lever. Reducing unnecessary data transfer and processing supports a faster experience while lowering estimated digital carbon, though those environmental figures remain modelled rather than directly measured.
For hospitality, the commercial argument is more immediate than the environmental one. Your visitors are frequently outdoors, in a hurry, on variable signal, and deciding between you and somewhere else. A page that takes eight seconds has lost to a competitor whose page took two.
Accessibility matters more here than in most sectors
Guests with dietary requirements, visual impairments or dyslexia are reading your menu carefully, and a PDF or an image-based menu excludes them entirely.
Work towards WCAG 2.1 Level AA. Text menus rather than images, sufficient contrast for reading in daylight, keyboard operation through the booking flow, and descriptive links.
An inaccessible menu turns away a table that had already chosen you.
Our sustainable web design work treats speed, clarity and accessibility as one brief.