Restaurant Website Design: What Your Site Needs to Fill Tables

Good restaurant website design does one job: it gets a hungry person from "where should we eat?" to a table booking, an order, or a phone call in under a minute, on a phone. That means the menu, hours, address, and a booking or ordering button are visible straight away, the menu is real text rather than a PDF, and the pages load fast on mobile data. Beautiful photos help, but only after those basics work.

Most guides to restaurant website design are galleries of pretty examples. This one is the practical version: the ten things every restaurant site needs, how direct online ordering compares with delivery-app commissions, and the three ways to get a site built, with what each really costs as of October 2026.

What does a restaurant website need? The short checklist

If you only read one section, read this. A restaurant website that fills tables has:

1. The menu as text on a web page, with prices, kept up to date.
2. Hours, address, and phone number on every page, matching your Google Business Profile exactly.
3. A reservation button (if you take bookings) that opens your booking tool in one tap.
4. An online ordering link for pickup or delivery, ideally your own.
5. Real photos of your food, room, and team, compressed so they load quickly.
6. Allergen and dietary information that guests can find before they arrive.
7. Fast mobile pages: most visitors are on a phone, often outside, on mobile data.
8. Accessibility: readable text, labelled buttons and forms, and keyboard-friendly booking and ordering.
9. Pages for extra revenue: private events, catering, and gift cards, each with a simple enquiry form.
10. The basics of local search: a clear page title with your cuisine and neighbourhood, and structured data that tells Google your hours and address.

The rest of this article goes through each one, because the details are where most restaurant sites lose customers.

The menu: real text, not a PDF

The menu is the most visited part of almost any restaurant website, and the most common place sites fail. A PDF menu has to download, opens in a separate viewer, is hard to read on a small screen, and is usually a version or two out of date. Search engines also read it less reliably than a normal page, so dishes people search for ("birria tacos near me") are less likely to lead to you.

Put the menu on an HTML page instead:

• Group it the way guests order (starters, mains, sides, drinks), with prices.
• Mark dietary options (vegetarian, vegan, gluten-free) with a short legend.
• Keep lunch, dinner, brunch, and drinks menus on separate pages or tabs, with the hours each one is served.
• Make it easy for you to edit. If changing a price means emailing a developer, the menu will drift out of date.

Allergen and dietary information

In the US, the FDA recognises nine major food allergens: milk, eggs, fish, crustacean shellfish, tree nuts, peanuts, wheat, soybeans, and sesame. Labelling rules for packaged food don't map neatly onto restaurant menus, so check your state and local rules with your own advisers, but guests with allergies plan their visit online. A short allergen guide on the menu page (or allergen icons next to each dish), plus a line inviting guests to tell staff about allergies, saves your servers time and earns trust.

Hours, location, and Google: keep them identical

Many people never reach your website: they see your Google Business Profile, which can show your hours, menu, photos, and links to order or reserve. Your website and that profile should say exactly the same thing. When the website says you close at 10 and Google says 9, someone gets turned away at the door and leaves a review about it.

Practical rules:

• Put hours, address, and phone in the footer of every page, as text (not inside an image).
• Add holiday hours to both the website and Google before each holiday.
• Make the phone number tap-to-call and the address open in maps.
• Add local business structured data (the restaurant type) so search engines read your hours, address, and cuisine correctly.

Reservations and ordering: one tap from the home page

The two buttons that make money, "Book a table" and "Order online", belong at the top of the home page and in the menu bar on every page. On a phone, they should stay visible as the visitor scrolls.

For reservations, most restaurants link or embed a booking tool (OpenTable, Resy, Tock, or the booking feature of their point-of-sale system) rather than building their own. That's usually the right call. Google's restaurant tools also let guests reserve or join a waitlist from your profile through supported partners. If your bookings work differently (set menus with deposits, private dining with approvals, classes), our guide to online booking systems for small businesses covers when a ready-made tool is enough.

Direct online ordering vs delivery apps

This is where restaurant website design affects your margins directly. Delivery marketplaces bring new customers, but they charge a commission on every order. If regulars who already know you order through the app, you pay that commission on customers you would have had anyway.

Published rates, as of October 2026:

Channel	What the restaurant pays	Source
DoorDash marketplace, delivery	15% (Basic), 25% (Plus) or 30% (Premier) of the subtotal	DoorDash pricing
DoorDash marketplace, pickup	6%	DoorDash pricing
Uber Eats marketplace, delivery	20% (Lite, raised from 15% in March 2026), 25% (Plus), 30% (Premium)	Food On Demand, April 2026
Ordering on your own site via DoorDash's Online Ordering	No commission; a payment processing fee per order	DoorDash pricing

On a $35 delivery order, a 25% commission is $8.75 and a 30% commission is $10.50. The same order placed on your own website pays only card processing; at a common US rate of 2.9% + $0.30 (what Wix charges for US sales, for example), that is about $1.32 (delivery itself, if you offer it, is a separate cost). Across a few hundred orders a month, that difference adds up to thousands of dollars.

A sensible approach for most restaurants:

• Stay on the apps for discovery if they bring you new customers.
• Make your own ordering the easiest option for regulars: a big "Order online" button on your site, on your Google profile, on receipts, and on the bag.
• Keep the menu and prices in one place if you can, so the website, ordering, and apps don't drift apart.

One warning about free ordering widgets: free tools can be discontinued or change their terms, leaving restaurants to move menus and customer lists elsewhere at short notice. Whatever you use, make sure you can export your menu and customer data.

Photos, speed, and mobile design

Food photos sell, but huge, uncompressed images are also the main reason restaurant sites load slowly. A few rules:

• Use your own photos of real dishes and your real room. Stock photos of someone else's pasta don't build appetite or trust.
• Compress images and serve them at the size they're displayed.
• Avoid autoplay background videos on mobile; they eat data and push the menu down the page.
• Check your pages against Google's Core Web Vitals, which measure loading speed, responsiveness, and layout stability.

Design for the thumb: big buttons, short pages, and the menu reachable in one tap from anywhere.

Accessibility is part of restaurant website design

The US Department of Justice's guidance on web accessibility (March 2022) says the ADA applies to the websites of businesses open to the public and lists food and drink establishments among its examples. Its suggested practices include text alternatives for images, accessible online forms, keyboard navigation, and captions on videos.

For a restaurant site, that means: a text menu (another reason to drop the PDF), descriptive alt text on photos, enough colour contrast to read prices, labelled fields in booking and ordering forms, and buttons that work without a mouse. It's also simply good service: a guest using a screen reader should be able to read your menu and book a table like anyone else. This is general information, not legal advice.

Three ways to get a restaurant website

There are three common routes, and the right one depends on how much you want to do yourself and how much your site needs to do.

	Website builder template	Restaurant website platform	Custom site, built for you
Examples	Wix, Squarespace	Popmenu, BentoBox, or your POS's website tool	An agency, a freelancer, or a subscription service
Typical cost (as of October 2026)	Squarespace Core $17/month billed yearly (pricing); Wix Core, its entry plan that takes payments, $29/month billed yearly (Website Builder Expert)	Popmenu reported at $179 to $499/month (Sauce); BentoBox quotes on request	Varies widely: a one-off project fee, or a monthly subscription
Who builds and updates it	You	You, with restaurant-specific tools	The developer, with you editing content
Strengths	Cheap, fast to start, many restaurant website design templates	Menus, ordering, and marketing designed for restaurants	Fits exactly how you take bookings, orders, and events; you can own it
Watch out for	Your time; slow pages if you overload the template; add-on apps	Monthly cost per location; leaving means moving everything	Choosing a reliable builder; who maintains it after launch

A website builder suits a simple restaurant website: one location, a menu, hours, and links to an existing booking and ordering tool. Budget an afternoon a month to keep the menu current.

A restaurant platform suits restaurants that want menus, ordering, and email marketing in one package and don't mind a higher monthly bill that grows with locations.

A custom site pays off when your restaurant doesn't fit a template: several locations with different menus, catering orders with lead times, private dining enquiries that need approvals, or your own ordering connected to your POS. A WordPress restaurant website is one common way to build it; a site built in custom code is another.

What the best restaurant websites have in common

Look through any list of restaurant website examples and the ones that work share the same traits, whatever their style:

• You can tell what kind of place it is in two seconds: cuisine, price range, and neighbourhood above the fold.
• The menu is one tap away and readable on a phone.
• Booking and ordering are obvious and never more than a click from any page.
• Hours and address are impossible to miss and match Google.
• The photos are theirs: real dishes, real rooms, real people.
• They are fast. The best restaurant website design is usually simpler than you expect.

Having your restaurant website built for you

If you'd rather not build and maintain the site yourself, Buildly designs, builds, hosts, and maintains custom websites on a monthly subscription. You send a free brief, get a written scope and price, and approve each stage (scope, wireframes, design, build, launch). The written scope recommends the technology (for example WordPress, or custom code), and you can ask for one you prefer.

• A restaurant website with a menu and a booking or enquiry page fits the Essential plan: $35/month launch price (regular $60; subscribers keep $35 for as long as they stay subscribed), a $100 setup fee, the initial build at no extra charge, 2 change requests per year, shared hosting, and ownership of the source code and database after 12 months.
• A restaurant site with online ordering and payments is a bigger build that fits the Business plan, from the price on our pricing page. Standard integrations, such as a payment provider, are $20 each, once.

Tell us in your brief how you update the menu and take bookings and orders, and the scope will spell out how it works. See business websites for what's included, or online stores if ordering is the main job. When you're ready, send a brief.

Common restaurant website mistakes to avoid

• A PDF menu, or a menu that's three price rises out of date.
• Different hours on the website, Google, and the delivery apps.
• Booking and ordering buttons hidden in the footer.
• Splash pages, pop-ups, and autoplay music before the menu.
• Photos so large the page takes ages to load on mobile data.
• No way to enquire about private events or catering, so that revenue goes elsewhere.
• Nobody responsible for updates after launch. Our guide to website maintenance costs explains what ongoing care usually involves.

Get the basics right and restaurant website design stops being about looks and starts being about covers and orders: a clear menu, accurate hours, one-tap booking and ordering, and pages that load fast on a phone.