Featured · client work
Lunarlink Solutions, Toronto
See it live
Drop your URL and I’ll send back a short reply with what’s holding it back, and how to fix it.
Look out for a reply from hello@umberdesignstudio.com within two business days.
The menu is the most-wanted page on any restaurant website, and most restaurants serve it as a file built for a kitchen printer. Here is what that costs, and what a menu page should be instead.
Watch anyone decide where to eat. They are on a phone, often standing on a sidewalk or lying on a couch, and they want two things from your website: the menu and a reason. Whether they get a table is mostly decided right there.
On most restaurant sites, tapping "Menu" downloads a PDF. It opens slowly, sideways to the screen it is on, in eight-point type designed for a kitchen printer. The customer pinches, zooms, drags, gives up, and checks the next place on the list. You paid for the visit, the design, and the domain, and lost the table to a file format.
The menu PDF survives because it is easy for the restaurant. It is the same file that goes to the printer, so it always matches. That convenience has a price, and it is paid nightly.
Three things, and the first two are invisible.
It costs you search traffic. People search for dishes: "birria tacos downtown", "gluten free pasta near me", "best butter chicken in Surrey". Google is far better at reading a real page than a designed PDF, and a scanned or image-based menu is completely unreadable. A restaurant whose dishes exist only inside a PDF is not in those results. The restaurant with a proper menu page is, for every dish it serves.
It costs you the AI answer. A growing slice of "where should we eat" is asked to ChatGPT or Perplexity, and assistants recommending restaurants can only repeat what they can read. Dishes locked in a PDF do not make the answer.
And it costs you the customer standing on the sidewalk, which is the expensive one. Every extra tap and every pinch-zoom sheds a percentage of people who were, seconds earlier, planning to eat at your restaurant.
A real menu page is just a page: sections for the courses, dish names as text, descriptions, dietary markers, prices as text. It loads instantly, wraps to fit the phone it is on, and can be read aloud by a screen reader, which the PDF cannot.
It also does things paper cannot. The dinner menu can note that it changes seasonally. The dish your regulars rave about can carry its photo. Ninety-second updates when a dish changes, no designer, no re-export, no "menu may not reflect current offerings" disclaimer.
The objection is always drift: "the website menu will get stale because the print menu is the real one". That is a workflow problem, not an argument for the PDF. When updating the site menu is genuinely easy, it stays current. When it requires exporting and uploading a file, it does not. Build the easy path and the drift disappears.
The menu is what they came for. The site's other job is the reason and the door.
The reason is mostly photography. Real plates, your actual room, shot warm and recent. Stock food photography on a restaurant site is like stock food in a restaurant; people can tell. Pair it with the two sentences of what you are: the style, the neighbourhood, the thing you are known for.
The door is the action button: reserve, order, or call, visible without scrolling, on every page. If you take reservations, the booking widget should open in place, not route through "email us". If you do takeout, the order link goes to your own ordering page first, not straight to a commission app. Hours and address live in the header or footer of every page as text, not only in an image of your storefront.
Most of your customers meet you on your Google Business Profile before your website. The two have to agree: hours, phone, address, menu link, all identical, with the profile's menu link pointing at your menu page rather than a PDF upload from 2023. Mark the site up with structured data for a restaurant, so machines get your hours, cuisine, and price range without guessing. When the profile, the site, and the menu all tell one story, you look current everywhere the customer checks. The mechanics are the same local-search plumbing we covered in why your business isn't showing up on Google.
Open your site on your phone tonight, on mobile data, and try to do what a customer does: find the menu, read it, find tonight's hours, book or order. Count the taps and the pinches. Then do the same on the site of the busiest place in your neighbourhood.
If that test stings, the restaurants page covers how we build restaurant sites where the menu is a page, the door is obvious, and the whole thing matches what Google says. We keep local notes for Vancouver and Montréal as well. Or send us your URL and we will run the full audit, free, written, and yours to keep either way.
Keep reading
Jul 17, 2026
5 min
Jul 17, 2026 · 5 min
Med spa clients research harder than almost any other local customer. Most med spa websites are built like salon brochures and lose them in the first minute. Here is what the ones that book actually do.
Apr 17, 2026
6 min
Apr 17, 2026 · 6 min
Most dental websites lead with a stock photo of a model smiling at a dentist. Here is what actually moves new-patient bookings on a Canadian dental site, with the four homepage changes we make on every rebuild.
Apr 3, 2026
8 min
Apr 3, 2026 · 8 min
The exact checklist we use to audit a small-business website's lead-generation performance in five business days. Eleven questions, plain English, the same ones a working site has to answer in 2026.
