Restaurant website examples: what a hungry guest looks for first
A guest who opens a restaurant website on a phone usually wants four things: what's on the menu and what it costs, whether you're open tonight, where you are, and how to get a table. I opened six independent restaurant websites on a phone-sized screen to see how fast each one answers. Below is what I found, one federal rule on reviews, and sample lines you can adapt.
How I checked six restaurant websites
I searched "restaurant" plus a city in six states: Louisiana, Maine, New Mexico, Kentucky, Minnesota and South Carolina. From each search I took the first site run by a local, independent restaurant. Travel guides, review sites, booking platforms and chain locations were skipped. In Louisville I also skipped three restaurant sites that came up earlier in the results, because each of those restaurants is part of a hotel. Partway through, one search engine asked me to prove I was human. I did not try to get past it and used another search engine instead.
Each site was opened in a window of 390 by 844 pixels, the size of a common phone, with a mobile browser signature. I only scrolled and read. No forms filled out, no pop-ups closed, no buttons pressed. To read a menu, I opened the menu page at the address given in the home page code. Where I say a number dials when tapped, I found the phone link in the page code. The restaurants stay unnamed, and the notes are about the websites, not about the food.
What the six sites showed on a phone
| Restaurant in | Phone on the first screen | Menu | Hours and address on the home page |
|---|---|---|---|
| Louisiana | No; a tap-to-call number in the contact block lower down | Its own page, dishes and prices as text | Address on the first screen; hours for each day lower down |
| Maine | No; a tap-to-call number near the bottom | Three PDF files: dinner, drinks, dessert | "Serving dinner nightly" at the top, no closing time; address near the bottom |
| New Mexico | No; a tap-to-call number in the hours block, just below | Its own page, dishes and prices as text | Address, days and lunch and dinner hours near the top |
| Kentucky | No; the number is plain text in the footer, not a link | Six menus offered as PDF downloads | Hours for each day and the address in the footer |
| Minnesota | No; a cookie banner covers the bottom of the screen; a tap-to-call number further down the page | Food, kids and drinks menus as PDF files | "Open daily" with hours, and the address |
| South Carolina | No; I found no phone number in the home page text or code | A "Print PDF Menu" link; the menus page names six menus but shows no prices as text | "lunch Monday through Saturday, brunch on Sundays, and dinner nightly", no times; the street address only inside the history text |
| Restaurant in | Booking a table | Ordering online | Allergen notes | Reviews on the home page |
|---|---|---|---|---|
| Louisiana | "We do not take reservations", with the party size they can seat | "Place your order" on the first screen; the order page loads an outside ordering service | None on the menu page | Links to its Yelp and Google pages and a "Leave a review" link |
| Maine | An OpenTable booking box on the home page | None | Menus are PDF files | None |
| New Mexico | Dinner by phone; lunch is walk-in only | A takeout menu; the cart on the site sells gift cards and gift packs | (GF) and (V) marks next to dishes | None |
| Kentucky | OpenTable links | "Order Online" goes to the ordering page of the restaurant's point-of-sale system (Heartland) | Menus are PDF files | Two quotes, each with a first name, last initial and "Google review" or "Facebook review" |
| Minnesota | Its own booking page, which first showed a "confirm you're human" check | "Online ordering is temporarily unavailable" on the first screen | A section on gluten-free and vegan dishes, plus a raw or undercooked food notice | One quote in capitals with no name; a note about 2021 voting |
| South Carolina | A Resy link | None | Menus are PDF files | None; press mentions of the chef instead |
All six sites were opened on October 3, 2026, at 390 × 844 pixels. PDF menus were not opened; the allergen column covers only text on the web pages.
The tally: none of the six showed a phone number on the first screen. Four had a tap-to-call link somewhere on the home page, one showed the number as plain text, and one had no number at all. Two of six put the menu with prices on a web page as text; the other four sent guests to PDF files. Four gave full business hours on the home page. Four let guests book a table online, one took bookings by phone, and one said plainly that it does not take bookings. Two put guest reviews on the home page, and only one of them said who wrote them.
What a guest needs in the first ten seconds
A menu they can read on a phone
Four of six menus were PDF files. On a phone, a PDF usually opens in a separate viewer, the guest pinches to zoom, and the dishes and prices are not part of the web page itself. The New Mexico and Louisiana sites did it the easy way: a menu page with each dish, a short description and the price as plain text. The New Mexico page also marks gluten-free and vegetarian dishes right next to the name. If a printed PDF is useful to you, keep it as an extra link under the text menu, not instead of it. More on this in my guide to putting a menu on your website.
A number they can tap
None of the six put a phone number on the first screen. That matters most for the New Mexico restaurant, where dinner is booked by phone: the number is there, just below the first screen, and it dials when tapped. On the Kentucky site the number sits in the footer as plain text, so a guest has to copy it. The South Carolina home page has no phone number at all. A tappable number is a link in the page code that looks like <a href="tel:+1[your number]">.
Open tonight, and where
The New Mexico site answers this best: address, open days, lunch and dinner hours and how to book, all in one block near the top. The Maine site says "Serving dinner nightly" at the top, which helps, but I found no closing time. The South Carolina site describes its hours in a sentence without times, and its street address appears only inside the history of the building. Hours belong in plain text near the top, next to the address and a map link.
Notices that stay up too long
The Minnesota site shows "Online ordering is temporarily unavailable" in red on the first screen, and further down there is a note asking guests to vote in a 2021 contest. A notice is a good idea when something changes. Give it an end date and take it down when it has done its job.
Booking and ordering through other services
Most of the six use an outside service for tables or orders, and that's normal. Three take bookings through OpenTable or Resy, one through its own page. The Louisiana site handled it in the clearest way of all: it says up front that it does not take reservations and how big a party it can seat. A guest with a group of ten knows what to do before calling.
On ordering, the Louisiana order page loads an outside ordering service inside the restaurant's own site, and the Kentucky "Order Online" button leads to the ordering page of its point-of-sale system. I found no links to delivery apps on the six home pages. If you do use one, say on your site which one, and whether the prices there match the menu.
The Minnesota booking and ordering pages first showed a "confirm you're human" check. My test browser did not pass it, so I could not see what comes next. Bot checks protect a site, but every extra screen before a booking is one more place where a guest on a slow phone can give up.
Allergens, photos and reviews
Only two sites said anything about allergens or diets in text on the web page. The Minnesota menu page explains which pastas are vegan or gluten-free, which ones contain egg, and asks guests to talk to their server. Writing it that way is honest: it is information from the restaurant, not a promise that a dish is safe for every allergy. A short line such as "Tell your server about any allergy" is worth adding even if your menu has no marks.
Photos were the strongest part of the sample. All six home pages had large photos, from 5 to 18 each, and the Maine home page has a gallery of 16 pictures. Use your own photos of your room and your dishes; a guest can tell when a plate is from a stock library.
Two of six home pages showed guest reviews. The Kentucky site shows two short quotes, each with a first name, last initial and where it was posted. The Minnesota site puts one quote in large capitals near the top with no name or source. The Louisiana site doesn't quote anyone, but links to its Yelp and Google pages and asks guests to leave a review.
Reviews fall under the FTC's rule on consumer reviews and testimonials. 16 CFR § 465.2(a) makes it a violation for a business to "write, create, or sell a consumer review, consumer testimonial, or celebrity testimonial" that materially misrepresents who the reviewer is or what their experience was. § 465.4 covers rewards: a business may not give "compensation or other incentives" for reviews that express a particular sentiment, positive or negative. A free dessert for a five-star review falls on the wrong side of that line. On the sites I build, I publish only real reviews with a name and a source. This is not legal advice.
Sample lines you can adapt
These are templates. Replace everything in square brackets with what is true for your restaurant, and delete a line if it isn't.
| Where | Sample line |
|---|---|
| First line | [Kind of food] in [neighborhood], [City]. Open [days], [hours]. Call [phone number] or book a table. |
| Booking | We take reservations for [lunch or dinner]. Walk-ins welcome at the bar. Groups over [number]: please call. |
| No booking | We don't take reservations. We can seat parties of up to [number]. |
| Ordering | Order pickup here on our site. Delivery through [service], where prices may differ. |
| Allergens | (GF) gluten-free, (V) vegetarian. Our kitchen handles [nuts, shellfish]. Please tell your server about any allergy. |
| Review | "[Guest's own words]" [First name and initial], on [platform]. |
How I build a restaurant website
A one-page restaurant site is $50. A multi-page site with a menu page, hours and location, booking, photos and an about page is $75 - $150. You get the fixed price within fifteen minutes. The 24 hours start with my email confirming that I have everything: the agreed scope, your logo, text, photos and contact details.
The menu goes on the page as text with prices, so it reads on a phone and you can update a dish without a new PDF. Hours, address and a tap-to-call number sit near the top, and the booking button goes to the service you already use. I publish only what is true of your restaurant, reviews included. You pay after you have seen the finished site working. If you don't like the finished site, tell me before you accept it and you owe nothing.
Want to know how your current site does on a phone? The free website check runs 17 checks in about ten seconds, tap-to-call among them.
What a website for a cafe or restaurant from me includes →
See what a website needs by industry: for cafés and bakeries.
A restaurant website for a fixed price
You get the exact fixed price within fifteen minutes, before any work starts.
This guide is not legal advice. Check the rules for your state and city before the site goes live.