A restaurant website needs six things to actually earn its keep: a fast, mobile-friendly menu with no PDFs, built-in online ordering and reservations, real food and interior photography, hours and location visible without digging, basic on-page SEO for your cuisine and town, and load times under a second. Miss any one of these and a hungry visitor comparing you against the place next door will pick whichever site made the decision easier.
I've built restaurant websites and other local business sites for over 20 years, and restaurants are one of the clearest cases where a missing feature costs real money the same night. Someone deciding where to eat isn't browsing leisurely. They're standing in their kitchen or sitting in a parking lot with three tabs open, and the first site that answers their questions wins the reservation or the order.
What Should a Restaurant Website Include?
Here's the full list, and why each piece matters specifically for restaurants rather than small businesses in general.
- A fast, mobile-friendly menu, built as real text on the page, not a scanned PDF someone has to download and pinch-zoom to read.
- Online ordering and reservations, built directly into the site so a diner can order or book a table in a couple of taps.
- Real food and interior photography, since appetite appeal is the single biggest thing that turns a browser into a customer.
- Hours, location, and contact info up front, visible on the homepage without a click, because that's the first thing a hungry visitor checks.
- Basic local SEO, pages and content built around your cuisine and your town, plus a connected Google Business Profile.
- Sub-1-second load times, since dinner-decision searches happen in a narrow window and a slow page gets abandoned before the menu even loads.
A stock template with a food photo dropped on the homepage can check some of these boxes, but rarely all of them well. It's a generic small business site with a restaurant's name on it, and most diners can tell within a few seconds of landing on it.
Why Can't a Restaurant Menu Be a PDF?
Because PDFs are built for printing, not for a phone screen, and nearly all restaurant searches happen on a phone. A diner pulling up your site in line or in the car has to download the file, wait for it to open, then pinch and zoom their way through pages that were never designed to be read on a 6-inch screen. Plenty give up before they find out what you actually serve.
A menu built as real HTML on the page loads instantly, resizes itself to fit any screen, and lets you update a single item without re-exporting and re-uploading a new file every time a price or a dish changes. It's also the only format Google can actually read and index, so a PDF menu is invisible to anyone searching for a specific dish, while a text menu can show up directly in search results.
Why Does Online Ordering Need to Live on Your Own Site?
Because third-party delivery apps like DoorDash and Uber Eats commonly take 15% to 30% of every order, and that commission comes straight out of your margin on every single sale. Online ordering built into your own website costs nothing per order. You pay for the site itself, not a cut of every transaction that happens through it.
There's also a control problem. On a delivery app, you're competing for attention against every other restaurant on the platform, your menu photos and layout look like everyone else's, and the app owns the customer relationship, not you. A reservation or order placed through your own site keeps that customer, and their contact info, with your business. I've covered this tradeoff in more depth in do restaurants still need a website, since it comes up almost every time a restaurant owner asks about dropping their site in favor of social media and delivery apps alone.
What Makes Restaurant Photos Actually Convert?
Real photos of your actual food and space, well-lit, specific to your menu rather than generic stock images of food that isn't yours. Diners decide with their eyes before they ever taste anything, and a blurry phone photo or an obvious stock image undercuts trust the moment someone notices it.
A handful of strong, well-lit photos of your best dishes and your dining room beats a large gallery of mediocre ones. Photos also need to load fast. A gorgeous photo gallery that takes five seconds to render defeats its own purpose, since the visitor gives up scrolling before the images that were supposed to win them over ever finish loading. Every site I build compresses and optimizes photography so galleries stay fast without losing the quality that makes them appetizing.
Should Online Ordering, Delivery Apps, or Both Be on the Menu?
Most restaurants benefit from offering both, but they're not equal in what they cost you. Here's how the two compare:
| Approach | Cost Per Order | Who Owns the Customer |
|---|---|---|
| Your own site's online ordering | $0 commission | You keep the contact and order history |
| DoorDash, Uber Eats, Grubhub | 15% to 30% commission | The platform keeps the relationship |
Delivery apps bring in customers who are browsing inside that app and wouldn't have found you otherwise, so they're still worth having. But every order that comes through your own website instead of a delivery app is pure margin you'd otherwise be giving away. The goal isn't dropping delivery apps, it's making sure your own site is the easier, cheaper option for anyone who already knows your name.
How Fast Should a Restaurant Website Load?
Under a second, as a baseline, not an upgrade. Google's own research found that 53% of mobile visitors abandon a page that takes longer than three seconds to load, and during a dinner-decision search, three seconds might as well be a minute. Page speed also factors directly into Google's Core Web Vitals ranking signals, so a slow restaurant site loses twice: once in search rankings, and again when the hungry visitor bails before your menu finishes loading.
Every site I build hits sub-1-second load times and 95+ PageSpeed scores from day one. If you want to see where your current site stands, run it through my free speed test, it takes under a minute and shows exactly what's slowing you down.
What Should You Do Next?
- Check your menu format. If it's a PDF, that alone is likely costing you mobile visitors who give up before they see what you serve.
- Test your speed. Run the free test and see whether load time is quietly sending hungry visitors to a faster competitor.
- Compare real examples. Browse live client sites in my portfolio to see these features working together on an actual restaurant site.
- Get a free mockup. I'll build a free homepage mockup for your restaurant at no cost, so you can see what a site built around your menu and your town would look like. For real numbers on what a build like this runs, see how much a restaurant website costs, and for full plan details including the $150/month option with $0 down, nothing is hidden behind a sales call.
None of these features are flashy on their own. A fast menu, working online ordering, honest photos, and a page that loads before someone gives up aren't exciting to talk about, but they're what separates a restaurant site that fills tables from one that just sits there looking nice. If you want more on turning that traffic into actual reservations and orders once the features are in place, how to get more restaurant customers from your website picks up where this list leaves off.