Skip to main content

Conversion Rate Optimisation (CRO) for Restaurants

Conversion work for restaurants is measured in seconds, because a hungry visitor who cannot find the booking button simply picks another place.

The reservation form needs only an hour and how many people are coming, and the page for parties states a price per head so organisers need not ask.

See the full Conversion Optimisation service·See what we offer restaurants

Restaurant manager improving table bookings and the guest experience in an upscale dining room

Online challenges for restaurants

The biggest losses come when guests hesitate at a key booking step and the page answers too late or too vaguely.

Every occasion needs its own message, or the wrong guests come

Lunch, dinner, events and delivery each need different wording.

  • Pages, posts and adverts that treat every occasion the same draw guests who do not fit.
  • A message aimed at one occasion brings better-matched bookings and a better mix of lunch, dinner and delivery.

Party pages that never say what the day might cost

Without a rough price per guest or an example menu, someone organising a celebration has no idea whether to ask.

  • A reservation form that asks for more than the date, the time and the number of people loses diners on a phone.
  • Visitors deciding where to eat right now leave the moment the menu or the booking button is hard to find.

Conversion Optimisation approach for restaurants

For restaurants, we aim the tests at the booking path, the points where people get stuck comparing options or packages, and the moments on a phone that decide the booking.

The seconds between hunger and another restaurant

Whoever visits a restaurant's site is usually deciding right now and leaves the moment something cannot be found.

  • We check on a phone how many taps separate a guest from the menu with prices, today's hours and a way to reserve, and remove what stands in between: a welcome film, a newsletter window, a menu to download.
  • The buttons for reserving and calling are pinned to the bottom of the screen while the guest reads the menu.

A reservation form that asks only what the room needs

Every extra field in the form means lost tables, most of all on a phone, in the street.

  • The date, the hour, the number of people, a name and a phone number are enough. Allergies and the occasion are optional, and no account is needed.
  • When the chosen hour is taken, the form suggests the nearest free times and the waiting list in place of a bare refusal, and the confirmation comes by text at once.

The party page and the doubt about price

People planning a party hesitate because they cannot judge what the day will cost, and so they do not ask at all.

  • Right beside the enquiry button we place a price per person for a stated level, what it covers and photos of the room laid for a celebration.
  • Traffic on a restaurant's site swings with the weather and the holidays, so each change is judged on similar days, and with small numbers we say how far the result can be trusted.

Conversion Optimisation process for restaurants

01

Where visitors stop

We look at where visitors leave and read the questions people ask by phone and email before they decide.

02

Doubts answered

We answer the main doubt next to the button and shorten the form or the booking path. For restaurants, the booking form keeps to the date, the hour and the party size, and the page about private parties answers the doubt about price.

03

One change at a time

We change one thing at a time, because a small site has too few visits for quick tests.

04

Judging the result

We judge a change by the enquiries that follow, and undo it if it brings more enquiries of the wrong kind.

Restaurant service with menu choices, table bookings and delivery planning

How we measure results for restaurants

We count finished table bookings and party enquiries per page, and compare a change with the same days of the week before it.

Questions about Conversion Optimisation for restaurants

Plain answers about Conversion Optimisation, written for restaurants.

On a phone: with the way from the first screen to a confirmed table, and with the same way for an enquiry about a party.

  • We time it, count the taps and note the places where a guest would have to guess.
  • Data from the reservation tool then shows at which step people really give up, and that step is changed first.

Sometimes because they found what they were looking for and simply came, and no report will show that good result.

  • Often, though, the menu is a file that loads slowly, has no prices or ends with no way to reserve.
  • We put a reserve button under every part of the menu and see whether more visits end in a reservation.

Stay with you wherever the tool allows it.

  • Every move to another address loses some of the guests, and on a portal your restaurant stands next to its competitors.
  • An embedded reservation window keeps the guest on the page and lets the whole path be measured.
  • If the portal is the only possibility, the button should at least open your profile there directly.

That means the page promised too much or said too little.

  • Next to the form we add the minimum number of guests, the price per person and the periods that are already taken.
  • Fewer enquiries may come after that, but more of them can be answered with an offer, and that is the number we follow.

General questions about Conversion Optimisation, the same for every trade, are in our FAQ.

FAQ: Conversion Optimisation

Need a growth plan for restaurants?

Share your goals and constraints. We will turn them into a practical Conversion Optimisation plan for restaurants.