Key takeaways
- A restaurant website has five jobs: show the menu, confirm you are open, show where you are, take the booking or order, and capture events and catering leads.
- Build for phones first; 16% of US adults are smartphone-only internet users, so your site may be a guest's only way to check you out[1].
- Put booking and direct ordering on the home page; 47% of full-service operators say they make no profit on third-party delivery orders[2].
- Accessibility is part of the job: DOJ lists barriers such as poor color contrast, missing alt text, uncaptioned video and inaccessible forms[3].
- Test speed against Google's Web Vitals thresholds and fix the slowest page first, usually the home page photo or the menu[4].
The five jobs a restaurant website must do
Guests rarely browse a restaurant website for fun. They arrive with a question: what is on the menu, are you open now, where exactly are you, can I book for Friday, can I order pickup, do you do private parties? A good site answers each question within a tap or two on a phone. Everything else, from the story of the founders to the photo gallery, is secondary.
- Show the menu, in text, with prices.
- Confirm hours, including kitchen close and holiday changes.
- Show the location, parking and entrance.
- Take the booking or the order directly.
- Capture private event, catering and large-party inquiries.
Build for the phone first
Pew Research Center reports that 91% of US adults own a smartphone and 16% are smartphone-only internet users without home broadband[1]. Many guests will only ever see your site on a small screen, often on a cellular connection. Design and test every page on a phone before looking at it on a laptop.
- Booking, ordering, menu and call buttons visible without scrolling on the home page.
- Tap targets large enough for a thumb, with space between them.
- Text at a readable size without zooming; no menus set in tiny script fonts.
- No pop-ups that cover the screen on arrival, especially newsletter boxes that hide the menu button.
The menu: HTML, current and complete
The menu is the most visited page on most restaurant sites. Publish it as an HTML page with dish names, short descriptions, dietary labels and prices. A PDF can sit alongside it for printing, but it should not be the only version: PDFs are hard to read on phones, often go out of date, and are harder for assistive technology to read than well-built pages. Keep separate sections or pages for lunch, dinner, brunch, drinks and kids if you have them, and update the page on the same day as the printed menu.
Hours and location
- Hours in text in the header or footer of every page, matching your Google profile exactly.
- Kitchen close time and any separate takeout or delivery hours.
- A short notice on the home page for holiday hours or temporary closures, removed when it expires.
- Address with a link to directions, notes on parking, transit and which entrance to use.
- A photo of the entrance from the street for hard-to-find locations.
Booking that works at any hour
Many reservations are made when you are closed. A Cornell study cited OpenTable's estimate that 25% of online reservations are made between 10:00 pm and 10:00 am[5]. Yet in a 2012 Cornell study, only 9% of restaurants that took online reservations offered booking access on their home page[6]. A visible “Book a table” button on the home page and the menu page is one of the simplest improvements a restaurant can make.
Some guests still want to talk to someone, so keep the phone number next to the booking button. If you take large parties or events differently, say so: “Parties of 8 or more, please use our events form or call.”
Direct ordering
Delivery apps bring reach but cost margin. In a May 2026 National Restaurant Association survey, 47% of full-service and 43% of limited-service operators said they do not make a profit on third-party delivery orders[2], and two in three restaurants reported paying platforms average fees of 15% to 29.9% of the transaction[2]. Your website is the main place to offer an alternative.
Source: National Restaurant Association, 2026[2]
Show the data
| Item | Value |
|---|---|
| Full-service operators | 47% |
| Limited-service operators | 43% |
- An “Order pickup” button that goes straight to your own ordering system, on the home page and menu page.
- Clear pickup instructions: where to go, parking, how long orders usually take.
- The same menu, prices and item availability as in the restaurant, updated together.
- A short line explaining why direct ordering helps the restaurant, if you choose to say so.
Events, catering and gift cards
Private dining and catering inquiries are among the most valuable leads a restaurant receives, and they often come through the website. Give them their own page with photos of the space, capacity, sample menus or packages, and a short form asking for the date, guest count, budget range and contact details. Respond within one business day. Add a gift card page that is easy to find before holidays, with digital delivery for last-minute buyers.
Accessibility is a must-have, not an extra
Restaurants and bars are public accommodations under Title III of the ADA[7], and the Department of Justice's guidance says the ADA's requirements apply to all the goods and services that public accommodations offer, including those on the web. DOJ lists common website barriers: poor color contrast, missing alt text on images, videos without captions, navigation that only works with a mouse and inaccessible online forms, and points to the Web Content Accessibility Guidelines as helpful technical guidance[3].
- Text with strong contrast against its background, including on photos.
- Alt text on meaningful images, such as dish photos and the entrance.
- Captions on any video.
- Every button, menu link and form usable with a keyboard alone.
- Booking and order forms with labeled fields and clear error messages.
Speed: the thresholds to test against
| Measure | What it means | Good threshold |
|---|---|---|
| Largest Contentful Paint (LCP) | How quickly the main content, often the hero photo, appears | Within 2.5 seconds |
| Interaction to Next Paint (INP) | How quickly the page responds to taps, such as opening the menu | 200 milliseconds or less |
| Cumulative Layout Shift (CLS) | How much the page jumps around while loading | 0.1 or less |
Google's Web Vitals guidance sets these thresholds and recommends measuring them at the 75th percentile of page loads, separately for mobile and desktop[4]. The usual culprits on restaurant sites are oversized hero photos, autoplaying background video, heavy menu plugins and third-party widgets loaded on every page.
Launch and quarterly QA
Phone test
On a mid-range phone with cellular data, open the home page and time how long it takes to find the menu, hours, booking and ordering.
Click every button
Book a test table, place a test order, submit the events form and check that each lands in the right inbox or system.
Compare details
Check name, address, phone, hours and menu against your Google profile and the main directories.
Accessibility pass
Tab through the site with a keyboard, check contrast and alt text, and try the forms with a screen reader.
Speed check
Run the main pages through a Core Web Vitals tool and fix the worst one first.
Example (fictional): a taqueria rebuilds its site around five buttons on the home page: Menu, Order pickup, Book, Hours and directions, and Catering. The old site's PDF menu becomes an HTML page and a 4 MB hero video becomes a compressed photo. After the change, the owner sees more direct pickup orders compared with the same months last year and fewer calls asking whether the restaurant is open.
What to leave off
Restaurant sites often grow features that make them slower and harder to use without helping guests. Before adding anything, ask whether it answers one of the five jobs. If not, it probably belongs on social media or nowhere.
- Autoplaying background video or music. It slows the page and annoys guests in public places.
- Full-screen pop-ups on arrival. If you want email sign-ups, use a small banner or a line near the footer.
- Menus available only as PDFs, images or embedded social posts.
- Splash pages or intro animations that delay the home page.
- Outdated event pages and expired specials. Remove them or move them to an archive.
- Stock photos of food you do not serve.
Who updates the site, and how fast
A website is only as good as its last update. Decide who can change the menu, hours and notices, and make sure that person can do it from a phone in a few minutes without calling a developer. Agree response times: hours and closures the same day, menu changes on launch day, events at least two weeks before they happen. Keep the logins for the domain, hosting and site builder in the restaurant's name, so a change of agency or manager never locks you out of your own site.
Frequently asked questions
What should be on a restaurant website?
An HTML menu with prices, hours, location and parking, a booking button, direct ordering, an events and catering page with a form, gift cards, and contact details, all easy to use on a phone.
Should a restaurant menu be a PDF?
Not only a PDF. Publish an HTML menu page that reads well on phones and is easy to update, and offer a PDF as an extra for printing if you like.
Does a restaurant website need to be ADA accessible?
Restaurants are public accommodations under ADA Title III[7], and DOJ guidance says ADA requirements apply to services offered on the web, pointing to WCAG as helpful guidance[3].
How fast should a restaurant website be?
Aim for Google's good thresholds: Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint of 200 ms or less and Cumulative Layout Shift of 0.1 or less[4].
References
Pew Research Center (2026). Americans’ Use of Mobile Devices in 2026 (Fact Sheet) (opens in a new tab) ↑
National Restaurant Association (2026). National Restaurant Association comments to the FTC on the Food Delivery Fees ANPRM (Project No. P267101) (opens in a new tab) ↑
US Department of Justice, Civil Rights Division (ADA.gov) (2022). Guidance on Web Accessibility and the ADA (opens in a new tab) ↑
web.dev (Google) (2026). Web Vitals (opens in a new tab) ↑
Cornell University Center for Hospitality Research (Sheryl E. Kimes) (2009). How Restaurant Customers View Online Reservations (Cornell Hospitality Report Vol. 9, No. 5) (opens in a new tab) ↑
Cornell University Center for Hospitality Research (Kimes and Kies) (2012). The Role of Multi-Restaurant Reservation Sites in Restaurant Distribution Management (Cornell Hospitality Report, 2012) (opens in a new tab) ↑
US Department of Justice (ADA.gov) (2026). ADA Title III Regulations primer (opens in a new tab) ↑