Restaurant · Spec rebuild
A restaurant site people can actually use at the table
A great local restaurant with a website that hides the menu and breaks on a phone. Here’s how I’d rebuild it so the two things a hungry person wants — the menu and the hours — are one tap away.
View the live demo →Before
The problems that hold back a family-owned Kamloops restaurant.
- ✕The menu is a PDF that downloads and pinch-zooms — unreadable on the phone where most people check it.
- ✕Hours and address are out of date or buried, so people don’t know if it’s open right now.
- ✕Heavy, full-screen food photos that take seconds to load on mobile data — the visitor leaves before they resolve.
- ✕No tap-to-call, no map link, no reservation button — every next step is friction.
- ✕Nothing for Google to read about the food or the location, so it loses to the chains on “restaurants near me.”
After
What the rebuild changes.
Menu first
The menu is real, readable text on the page — no PDF, no zoom — and loads instantly on a phone.
Open now, at a glance
Hours, address, a one-tap map link, and a call/reserve button sit right at the top. The visitor knows in two seconds whether to come in.
Fast, even with photos
Food photography sized and lazy-loaded so it looks good without stalling the page on mobile data.
Found locally
Real text about the food and the neighbourhood, structured for Google — so it shows up for “brunch in Kamloops,” not just its own name.
This is a spec rebuild — an unsolicited concept, anonymized, built to show how I work. It wasn’t a paid client engagement, and no real business is named or shown.