What every restaurant website needs (and what to skip)

A hungry person checking your restaurant on their phone wants four things, fast: what you serve, whether they can get a table, what the room feels like, and where you are. A restaurant website that nails those four beats a beautiful one that buries them. Here’s what actually earns its place — and what to leave off.

A menu that’s always current — not a PDF

The single most-visited page on any restaurant site is the menu, and the single most common mistake is hiding it in a PDF that’s six months old. A PDF is slow to load, awkward on a phone, and a hassle to change — so it never gets changed.

Your menu should be a real part of the page: readable on mobile, grouped into sections, with prices and a dietary tag (V, GF) where it helps. Most importantly, you should be able to change a dish or a price in seconds, so the site always matches the kitchen. If updating your menu requires emailing a developer, it’ll quietly drift out of date — and nothing erodes trust like a price that’s wrong at the table.

Table bookings, without the per-cover fee

If people can book a table the moment they decide, you capture bookings you’d otherwise lose to the restaurant down the road. A simple booking form — date, time, party size, a note — that confirms by email is enough for most places, and it keeps you off third-party platforms that take a slice of every cover.

You don’t need a complicated reservations system on day one. You need a clear “Book a table” button that works on a phone at 11pm.

Real photos of the room and the plates

People eat with their eyes, and they decide where to go by feeling the place before they arrive. A handful of well-lit, real photos — the dining room, a few signature dishes, the bar — does more than any amount of clever copy. Avoid generic stock food shots; diners can spot them, and they quietly say “this could be anywhere.” If you can’t get a photographer, daylight and a clean phone camera go a long way.

The practical facts, where people look for them

Half of restaurant searches are really logistics: Are you open? Where are you? Can I park? Put your opening hours, address, a map link and a phone number somewhere obvious — ideally near the top and again in the footer. A few honest guest reviews near the booking button help close the decision.

And make sure search can find you: a fast, mobile-friendly site with proper structured data gives “pasta near me” a chance of landing on your door rather than an aggregator’s.

What to skip

• A splash/intro animation. It delays the menu. Cut it.
• Autoplaying loud video. A muted background loop is fine; sound that ambushes someone in a quiet office is not.
• A ten-page site. Home, menu, and a contact/booking section cover it. Add a story or events page only if you’ll keep it up.
• A login or app. Almost no local restaurant needs one. Don’t make people sign in to read a menu.

The short version

Get the menu, the booking, the photos and the facts right, on a page that’s fast on a phone, and you have a restaurant website that does its job. Everything else is garnish.

Plot is built for exactly this — describe your restaurant and you get a designed site with an editable menu, table bookings, a gallery and your hours, ready to make yours. See a full example on the Fiorella demo, read more about Plot for restaurants, or start building free and have yours live this afternoon.