Case study / Website Design
A restaurant site built around bookings, not brochures
A conceptual restaurant build where every screen is judged on one question: can a hungry person on a phone book a table in under thirty seconds?
The brief
Independent restaurants usually inherit a website that treats the menu as a PDF and the booking button as an afterthought. The brief here was to rebuild the experience mobile-first, with menus as real content and a booking path that never leaves the page.
01 / Approach
Structure before styling
We mapped the four things people actually arrive for — menu, opening hours, location, booking — and gave each a permanent home above the fold on mobile.
02 / Approach
Menus as indexable content
Dishes are marked up as real HTML with structured data instead of being locked inside an image or PDF, so search engines and screen readers can both read them.
03 / Approach
Booking without friction
A single persistent action bar follows the visitor down the page, and the enquiry form validates inline so nobody loses a submission to a silent error.
Project facts
- Sector
- Hospitality
- Timeline
- 3 weeks
- Service
- Website Design
What we used
- Static-first rendering
- Structured data
- Inline form validation
- Image optimisation
What changed
- Sub-second first contentful paint on a mid-range Android over 4G
- Menu content indexable rather than trapped in a PDF
- One booking action visible on every screen, desktop and mobile
These are conceptual demonstrations of our approach, not claims about a named client project.
Related work
Want the reasoning behind these decisions? Read the Cartvys resources or see what this kind of work costs.