Website for Restaurants: UK Costs, Pages and Bookings
A restaurant website that works in the UK needs a clear menu, online bookings or reservations, your address and hours, strong mobile speed, and photos that look like the food you actually serve. Skip the fluff homepage and put the next booking or order one tap away. I build these for small hospitality businesses in Kent and beyond, and the trade-offs below are the ones that actually move covers.
What pages a restaurant site actually needs
Most independent restaurants do not need a 20-page brochure. They need a handful of pages that load fast on a phone outside the door or on the train home.
- Home: one strong photo, cuisine type, location, tonight's hours, and a booking button above the fold.
- Menu: current dishes with prices, allergens, and dietary flags. Update it yourself or have it managed; stale menus lose trust fast.
- Book a table: either an embedded system or a simple form that emails the floor. Include party size, date, time and any notes.
- Find us: map, parking, nearest station, and a Google Maps link. Phone number as a tap-to-call link.
- About or story: short, specific, no corporate waffle. Who cooks, where ingredients come from if that is a selling point.
- Private dining or events if you offer them: capacity, sample menus, enquiry form.
Optional extras that earn their keep: a simple lunch vs dinner split, a Christmas or set-menu landing page in season, and a careers page if you hire regularly. Do not bury the phone number in a footer only.
Bookings, menus and the tools that work
UK diners expect to book without ringing. Common options:
- OpenTable, ResDiary or similar: commission or monthly fee, diary sync, reminders. Fine if volume is high.
- A lightweight booking widget or form that goes to your inbox or WhatsApp. Cheaper, more control, you still confirm by phone or email.
- Direct phone and email as backup. Always show the number.
Menus need structured data so Google can show dishes in search. Keep prices in pounds, list the 14 allergens clearly (UK law), and note vegan, vegetarian and gluten-free options. A PDF menu is a last resort; it is slow on mobile and unreadable for screen readers. HTML menus you can edit in five minutes win.
If you do takeaway or delivery, link to your own ordering or a trusted partner, but do not let a third-party app own the only conversion path. Your site should still capture the booking or enquiry.
Speed, mobile and looking credible
Over 70 percent of restaurant searches happen on phones. If the first photo takes four seconds, they bounce to the next listing. Aim for under 2.5 seconds on a mid-range Android, compressed images (WebP), and no auto-playing video. Core Web Vitals matter for Google and for the person standing in the rain.
Photos: real plates from your kitchen, not stock. Shoot in natural light, crop tightly, keep file sizes under 200 KB each after compression. A gallery of 8-12 strong shots beats 40 mediocre ones. Include the dining room so people know the vibe: casual, white tablecloth, garden, whatever you actually are.
Trust signals that cost little: Food Hygiene Rating displayed, awards if genuine, a short press quote with a link, and a professional email such as bookings@yourrestaurant.co.uk rather than a free Gmail.
Local search and getting found
Google Business Profile does more for a restaurant than most ads. Keep hours, photos, menu link and booking URL identical on the profile and the site. Ask for reviews after a good service (never fake them). NAP (name, address, phone) must match everywhere: site, Google, directories.
On-page: the town or area in the title and a short paragraph, cuisine plus neighbourhood, and schema markup for Restaurant (address, geo, opening hours, menu, price range). That helps sitelinks and knowledge panels. Do not stuff keywords; write like a human who wants a table tonight.
UK costs: one-off vs pay monthly
Typical independent restaurant sites in the UK land in these bands (2026 market, excluding fancy custom booking engines):
| Type | Typical range | What you get |
|---|---|---|
| Template / builder DIY | £0-£400 setup + £15-£40/month | You do the work. Fine if you have time and design sense. Weak on bookings and speed unless you fight it. |
| Freelance or small studio one-off | £1,800-£6,000 | Custom look, menu, booking, mobile, basic SEO. You then pay hosting £10-£30/month and updates separately. |
| Agency full custom | £8,000-£25,000+ | Brand, photography, complex integrations. Overkill for most 40-cover rooms. |
| Pay-monthly plans | Setup fee then £50-£150/month typical in the market | Hosting, updates, security and management included. Suits businesses that cannot drop thousands upfront. |
I offer both a one-off website build and pay-monthly plans (setup then a monthly fee covering hosting, updates and ongoing management). Exact figures are on arlowebstudio.com because they change with scope. Pay monthly is often the practical route when cash is tight before a refurb or a quiet January.
Hidden extras to budget: professional photography £300-£800, a proper booking system £20-£80/month, copywriting if you hate writing, and SSL plus email (usually included in decent hosting). Domain is about £10-£15 a year.
What to brief and the build order
- Write down cuisine, covers, unique selling point in one sentence, and the one action you want (book, order, enquire).
- Collect current menu as a spreadsheet, allergen list, opening hours including bank holidays, and 10-15 photos.
- Decide booking method: widget, form, or phone-first.
- Choose one-off or monthly based on cashflow, not hype.
- Agree pages, mobile mockups, and a two-week content freeze so the menu does not change mid-build.
- Launch with Google Business, Search Console, and a 301 from any old site. Test the booking flow on a real phone.
After launch, update the menu the day it changes. A site that still lists last winter's specials looks abandoned. If you cannot do it yourself, that is exactly what a managed monthly plan is for.
Trade-offs I see every month
Pretty but slow loses to simple and fast. A huge hero video looks expensive and kills mobile data. Too many plugins for reviews, pop-ups and chat widgets slow the page and annoy people who just want a table. Instagram embeds are nice but do not replace a real menu.
If you already have a site that is five years old, a redesign is often cheaper than patching a crumbling theme. Redirects matter so Google does not drop you. Keep the same domain if you can.
For most small restaurants the winning combination is: honest photos, current HTML menu with allergens, one-tap booking, under 2.5s load, matching Google profile, and a way to change the specials without calling a developer every time.
Frequently asked questions
Do I need online bookings or is a phone number enough?
A visible phone number is essential. Online booking or a simple form converts extra covers, especially for tourists and people booking after 9pm. Start with a form if volume is low; add a diary system when no-shows or double-bookings become a problem.
How often should the menu be updated on the site?
The same day it changes in the kitchen. Allergens and prices must match what you serve. A managed plan or an easy editor means you are not waiting on a developer for a £3 price tweak.
Will a cheap website builder work for a restaurant?
It can, if you are willing to spend evenings on design, speed and booking setup. Most owners underestimate the time. A proper build or a monthly managed site usually costs less in lost covers than a slow, outdated DIY page.
What about takeaway and delivery on the website?
Link clearly if you offer it, but keep table bookings as the primary action if that is your model. Do not let a third-party app be the only way to order; your own site should still capture the customer.
How important is the Food Hygiene Rating on the site?
Display it. Diners look. It is a free trust signal and matches what they already see on Google. Pair it with real photos and consistent opening hours.