Picture the person looking at your website. They are on their phone, probably around half six, probably hungry, and probably looking at three other places at the same time. You get a few seconds. Here is what those seconds need to cover.
What kind of food, and where
It sounds obvious. Plenty of restaurant sites open with a moody photo and a slogan and leave you guessing whether it is tapas or a steakhouse. Say what you serve and which part of town you are in, right at the top.
A menu they can read without zooming
Not a PDF. A PDF menu on a phone means pinching, scrolling sideways and giving up. Put the menu on the page as text, with prices, and keep it current. Nothing annoys a customer like a dish that came off the menu months ago.
One button to book or order
Whatever system you use, the button should be visible without scrolling and work in two taps. If booking means phoning during service or sending a DM, you lose everyone who makes plans at 11pm.
Opening hours and how to get there
Today’s hours, clearly. A map link. Parking or transport if it helps. People check this just before they leave the house.
Photos of your actual food
Real dishes, the real room, real people. Stock photos of food are easy to spot, and they make people wonder what the real thing looks like.
What can wait further down
How the business started, the chef’s background, private dining, gift vouchers. All worth having. None of it matters in the first few seconds.
A quick test
Hand your phone to someone who has never eaten with you. Open your website. Ask them what you serve, whether you are open tonight and how they would book. If any answer takes more than a few seconds, that is the first thing to fix.
More on how we help restaurants, or send us your site for a free roast.
