The four questions a visitor is answering
Almost every arrival on a venue website is someone on a phone, deciding between you and one or two alternatives. They are answering four questions, in this order:
- What is this place? Answered by one photograph and one line of copy.
- Is it right for tonight? Answered by menus, prices and what's on.
- Can I actually get in? Answered by a live booking step.
- Where is it and when does it open? Answered by hours, address and access.
A site converts when all four are reachable in seconds. Most venue sites lose bookings by burying question three or making question two a download.
The booking journey
- A visible booking action on every screen. Not only in the header at the top of the homepage — anywhere the visitor happens to be scrolling.
- One tap to the booking system. Whatever platform you use, the handover should be immediate and should look like the same business.
- No dead ends. If a session is unavailable, offer the next one rather than an error.
- Walk-ins told they're welcome. Plenty of guests want reassurance, not a reservation.
- Phone number tappable. Large parties and awkward requests still convert better by voice.
Menus that do their job
Menus are the most-visited pages on almost every venue site. Publish them as real web pages with real prices, structured so they can be updated the day the kitchen changes them. Include dietary and allergen guidance clearly. Avoid PDFs: they're slow, hard to read on a phone and poorly understood by search engines and AI assistants alike.
Events, offers and what's on
Give every event and offer its own page with a date, a price and a booking action. That page is what you link from social and email, and it's what shows up when someone searches the event name. A single "what's on" image with the details baked into the artwork can't do any of that.
Plan those pages alongside the trading calendar — see building a 90-day marketing calendar.
Speed and mobile behaviour
- Compress and correctly size photography — hero images are usually the heaviest thing.
- Load the hero image first and defer everything below the fold.
- Keep fonts to what the brand needs; every extra weight costs render time.
- Test at phone width first and at the bottom of a poor mobile signal, not on office wifi.
- Make tap targets big enough for a thumb, with real spacing between them.
Local search and AI answers
A growing share of "where shall we eat" questions gets answered by a search summary or an AI assistant before anyone reaches your homepage. What helps in both cases is the same: plain, accurate text on the page for hours, address, cuisine, price range, booking options and access; structured data describing the venue; and consistency with your listings elsewhere.
The pre-launch checklist
- Booking action visible on every screen at phone width.
- Menus as web pages, current prices, allergens covered.
- Each event and offer on its own bookable page.
- Hours, address, parking and access findable in one tap.
- Hero image compressed and prioritised; page usable fast on mobile data.
- Unique title and description per page.
- Structured data for the venue and its menus.
- Contact form and phone number both tested end to end.
- Someone in the business able to update menus and events without a developer.
Frequently asked questions
How many pages does a venue website need?
Usually fewer than operators expect. Home, menus, book, events or offers, about and contact covers most single sites. Extra pages are worth adding when they answer a real question people search for, such as private hire or Sunday lunch.
Should the menu be a PDF?
No. PDFs are slow on a phone, awkward to read and largely invisible to search. Publish menus as web pages you can update, and keep a downloadable version only if the venue genuinely needs one.
Does site speed really affect bookings?
Yes. Every extra second before a page is usable loses visitors who are choosing between two venues on a phone. Speed and Core Web Vitals are treated as part of the build, not a later fix.