Online booking

Your restaurant website: what guests look for in the first ten seconds

Your restaurant website should answer, in ten seconds and on a phone, the six questions every guest asks: where are you, when are you open, what is on the menu, how much is it, how do I book and how do I reach you. Everything else comes after. A simple, fast, up-to-date site brings more bookings than a beautiful but slow one where the opening hours are hard to find. Here is what to show straight away, what you can drop, and the legal pages to check.

The gonnabook.it team6 min read

The first ten seconds

Most visitors reach your site on a phone, often from Google Maps or social media, with a specific question. They do not read: they look. What they must find without scrolling, or nearly:

What visitors look for, and where to put it
InformationWhere to put itWhy
The booking buttonTop of every page, always visibleIt is the action that matters
Opening hoursTop of the home page, with closures“Are they open tonight?”
Address and directionsBelow the hours, with a map link“How do I get there?”
Menu and pricesA direct link from the home page“Will I like it, can I afford it?”
Phone numberTappable on mobileFor those who prefer to call
One or two photosThe room and a dishThe feel of the place at a glance

If any one of these is missing or hidden, visitors head back to Google, and often to another restaurant.

The booking button, everywhere

The “Book a table” button should sit at the top of every page, in a contrasting colour, and open the booking straight away. Not a contact form, not an email address: a real booking, with day, time and party size.

Our guide to adding a booking widget to your website explains how to add it, whatever tool your site was built with.

Current hours, closures included

Wrong hours cost more than no hours: a guest who finds the door locked does not come back. Show:

  • opening days and times, service by service;
  • last arrival or last orders;
  • one-off closures and holidays, with the reopening date.

Update them at the same time as your Google profile, so both say the same thing.

The menu, as text

A “Menu” link from the home page, to a text page with prices. Not a 5 MB PDF or a blurry photo of the blackboard. Our article on your menu and prices online covers the format that works, daily specials included.

Drawing of a browser window with a large booking button, next to a phone and a location pin.
A visible button, an address, a phone number: the essentials fit on a phone screen.

Speed on mobile

A site that takes five seconds to appear on a phone loses some visitors before they even see your name. The usual causes are easy to fix:

  • heavy photos: a 6 MB photo straight off the camera, when 200 KB is plenty on screen;
  • an autoplay video at the top of the page;
  • add-ons piled up over time: an Instagram feed, a map, a chat window, decorative fonts.

Google offers a free tool, PageSpeed Insights, which measures a page’s speed on mobile and lists the priority fixes. Test your home page and your menu page.

Real photos, and not too many

Two or three good photos beat a gallery of fifty:

  • the room, during service, with good light;
  • two signature dishes, close up, in daylight;
  • the front, so guests recognise you in the street.

Avoid stock photos: guests spot them, and they say the opposite of what you mean. To get them right without a photographer, see our article on restaurant photos that make people book.

For search engines and assistants

Useful information written as text also serves search engines and the AI assistants that recommend restaurants. Your restaurant’s name, town and type of food in the home page title, address and hours as text, the menu as text: that is the base. Our article on getting your restaurant recommended by AI goes further, structured data included.

What you can drop

Many restaurant sites carry things that slow them down for no benefit:

  • a splash page to click through before entering the site;
  • music that starts on its own;
  • a long history of the house on the home page: it belongs on its own page;
  • a contact form instead of a real booking;
  • a news section whose latest post is two years old.

Adding booking without being a web designer

You did not build your site yourself? Not a problem: the booking button takes a few minutes for whoever looks after it.

With gonnabook.it, you say which tool your site was built with, Wix, WordPress or something else, and the step-by-step guide appears; if someone else runs your site, you send them an email with everything they need, and they do not need an account.

Frequently asked questions about restaurant websites

What should a restaurant website include?

The essentials are six things visible on the home page on a phone: a booking button, opening hours with closures, the address with a map link, the menu as text with prices, a tappable phone number and two or three photos of the room and the food. Add any legal pages your local rules require on a separate page.

Does a restaurant need a website if it has a Google profile?

A Google profile is enough for many guests to find your hours and address, but a website is still useful: you control the menu, the photos and the booking button, without depending on a platform’s display choices. A simple, fast site of one or two pages is often all you need.

How fast should a restaurant website load on mobile?

As fast as possible: every extra second loses visitors who are standing in the street deciding where to eat. Measure your home and menu pages with Google’s free PageSpeed Insights tool, then start with the usual culprits: oversized photos, autoplay videos and add-ons such as embedded feeds or chat windows.

Sources

· All articles

Read next
Zero commission

Your online bookings, for €69 excl. VAT a month.

A widget in your colours on your website, Google listing and social pages, with no commission per cover. Try it free for 30 days.

Free 30-day trial

No credit card · no commitment · €69 excl. VAT per month afterwards