A restaurant website usually gets judged on how it looks. That is the wrong test. The right test is whether a hungry person on their phone can find the menu, decide, and order in under a minute — and whether you keep the relationship afterward.
Most sites fail that test in small, fixable ways, and almost none of them are about taste or photography. They are about the few mechanics that decide whether a visit becomes an order.
Speed is the first thing on the menu
A person deciding where dinner comes from is impatient by definition. If the page takes too long to become useful on a phone over a patchy connection, they are gone before your first photograph has loaded — back to the app that opened instantly. Speed is not a vanity metric here; it is the difference between an order and a bounce.
You can measure your own page honestly in a couple of minutes — the free audit on this site reads your live page and tells you plainly what is slow and why, without an email gate. Most restaurant sites lose their first second to things that are quick to fix.
The menu is the product — treat it that way
The single most-visited thing on a restaurant site is the menu, and it is the thing most often done badly: a PDF that pinches and zooms on a phone, or a photo of a printed card that no one can read. The menu should be real, readable text that reflows to the screen, loads instantly, and is always current.
Current matters more than it sounds. A menu that still lists last season’s prices or a dish you stopped serving erodes trust at the exact moment someone is deciding to spend money with you.
Ordering should be the easiest thing on the page
If the goal is orders, ordering cannot be a buried link or a phone number that goes to voicemail at the dinner rush. It should be the obvious next step from the menu — direct, on your own site, with as few taps as you can manage and details that save for next time.
This is the same point the pillar piece makes about commissions: every order that comes through your own site instead of a marketplace is an order with no cut taken out of it, and a customer whose details you get to keep.
Get found, then keep the relationship
A site that converts is also a site that gets found. The basics earn most of the result: an accurate listing, clear location and hours, structured information search engines can read, and a page that works on the phone where almost all of this traffic lives.
Then keep what you earn. A light, honest invitation to join a list — for a genuine reason, not a pop-up that ambushes the menu — turns a one-time order into someone you can reach again without paying a marketplace to do it.
What it costs is mostly what it is built on
The real cost of a restaurant site is rarely the first build. It is the rebuild — the rushed template site that cannot take orders without a plugin that breaks, cannot be made fast, and has to be thrown away in two years. Built once, properly, on foundations you own, a site stops being a recurring expense and starts being an asset.
We are not going to quote you a number on a blog post; what a site costs depends on what it has to do. But we will tell you honestly where the money should and should not go, before any of it is spent.