7 Restaurant Website Mistakes That Cost You Orders

Most restaurant websites lose orders the same seven ways: a PDF menu nobody can read on a phone, no clear path to order, wrong hours, slow pages, invisible-to-Google structure, buried contact info, and total dependence on delivery apps. I've rebuilt restaurant sites that had most of these problems at once — when I rebuilt Walrus Subs' site, fixing this category of problem drove a 35% increase in online orders. Here are all seven mistakes, and how to fix each one.

1. Your menu is a PDF

This is the most common mistake and the most expensive one. The menu is the single most-wanted thing on a restaurant website — and a PDF is the worst possible way to deliver it.

On a phone, a PDF menu means a slow download, then pinch-zooming around a document designed for print. Half your visitors give up before the appetizers. And the damage goes deeper than annoyance: search engines can't meaningfully rank PDF content. When someone nearby searches "italian sub near me," a restaurant whose menu is real HTML can have that page show up. Yours can't — your menu is a sealed envelope as far as Google is concerned.

The fix: build the menu as an actual web page. HTML text, organized by section, readable at a glance on any screen. When I built Walrus Subs' site, the interactive on-page menu was the centerpiece decision — instant to load, indexable, no zooming.

A common objection: "but the menu changes, and the PDF comes straight from our print designer." That's exactly backwards. An HTML menu is easier to keep current — change a price in one place instead of re-exporting, re-uploading, and hoping nobody cached the old file. If your menu changes often, that's an argument for HTML, not against it.

2. There's no obvious way to order

Plenty of restaurant sites are digital brochures: pretty photos, a paragraph about the family history, and... no clear next step. The visitor is hungry right now. If they have to hunt for how to order — is it a phone call? a third-party link? do I just show up? — a meaningful share of them will bail to a competitor who made it obvious.

The fix: one primary call to action, visible without scrolling, on every page. "Order online," "Call to order," whatever your actual ordering path is — make it a button, make it big, make it tappable with a thumb. If you take orders by phone, the number should be a tap-to-call link, not text someone has to copy into their dialer.

3. Your hours are wrong (somewhere)

Nothing torches goodwill like driving to a restaurant the website said was open. Hours rot silently: the site says one thing, Google Business Profile says another, the Facebook page says a third. Holiday hours make it worse.

The fix: treat your hours as data with a single source of truth. Pick one place that's always right, update it religiously, and make every other listing match. On the site itself, put hours in the footer of every page — not just buried on a contact page. And when you change them, change them everywhere the same day. This costs nothing but discipline, which is exactly why it's a competitive advantage.

4. The site is slow on phones

Restaurant website traffic is overwhelmingly mobile — people searching from the couch, the car, the office at 11:45am. Yet most restaurant sites are built and tested on a designer's desktop, then shipped with 4MB hero photos of sandwiches. On a mid-range phone over cellular, those pages take long enough to load that a chunk of visitors leave before seeing anything. Slow pages don't feel slow to you, because you've never visited your own site hungry on 4G.

The fix: compress and resize every image (modern formats like WebP, sized for screens, not for print), skip heavyweight themes and plugins, and test the site on a real phone over cellular data — not on office Wi-Fi. Run it through PageSpeed Insights and take the mobile score seriously. This is also a reason to keep restaurant sites technically simple; fast and boring beats fancy and slow every time.

5. No local schema markup

This one is invisible, which is why almost everyone skips it. Schema markup is structured data in your site's code that tells search engines, unambiguously: this is a restaurant, here's the exact address, the hours, the phone, the menu URL, the cuisine. It's how you help Google show rich, accurate results for your business instead of guessing.

Your competitors are mostly missing it too — which makes it cheap differentiation. It doesn't change anything a human sees on your site; it changes how machines understand you, and machines are the gatekeepers between hungry searchers and your door.

The fix: add Restaurant schema (JSON-LD) with your name, address, phone, geo coordinates, opening hours, and menu link, and keep it in sync with your Google Business Profile. It's an hour of work for a developer who knows what they're doing.

6. Location and contact info are buried

"Where are you?" is the second question after "what do you have?" — and on too many sites the answer hides on a contact page, as plain text, with no map. Every extra tap between a hungry person and directions loses a percentage of them.

The fix: address in the footer of every page, an embedded Google Map (one tap to directions), and a tap-to-call phone number. On the Walrus Subs build, Google Maps integration was front and center for exactly this reason — directions one tap away, no hunting.

7. Your only web presence is delivery apps and Facebook

Some restaurants skip the website entirely: "we're on DoorDash and we have a Facebook page." That works, until you look at the economics. Delivery platforms charge commissions commonly in the 15–30% range per order, control the customer relationship, and list you right next to your competitors. Facebook shows your posts to a fraction of your followers and looks like Facebook, not like you.

Renting your entire web presence means someone else sets the terms, forever.

The fix: the apps and socials are fine as channels — keep them. But your own site should be the hub: the place with the full-margin ordering path, the canonical menu and hours, and the Google ranking that you own. Even a small site changes the math; over a year, shifting a modest slice of commission-based orders to direct ones can pay for the website several times over.

How do you check your own site for these mistakes?

You can audit yourself in ten minutes, tonight, with your own phone:

1. Put the phone on cellular data (turn off Wi-Fi — this matters).
2. Search your restaurant's name and tap through to your site. Time how long until you can read something.
3. Try to find the menu. Count the taps. Note whether you had to pinch-zoom.
4. Pretend you want to order. Is the next step obvious within three seconds?
5. Check the hours on the site against your Google listing and your door.
6. Tap the address. Did a map open? Tap the phone number. Did it dial?

Then hand the phone to someone who's never seen your site and watch them try to order. Don't coach. Where they hesitate is where your customers leave.

What fixing this actually costs

Here's the part that surprises restaurant owners: none of this requires an expensive build. A site that fixes all seven mistakes — HTML menu, clear ordering path, accurate hours, fast mobile pages, schema, visible location, owned by you — is a small, focused project. I build starter sites for $899 and full business sites from $2,500; I've broken down the full market math, including DIY builders and agencies, in how much a small business website costs in 2026.

Measure that against the other side of the ledger: every week, some number of hungry people find your site, can't read the menu or figure out how to order, and eat somewhere else. You never see those lost orders — they don't leave a complaint, they just leave.

Get an honest read on your site

If you run a restaurant and want to know which of these seven mistakes your current site is making, send me the URL. I'll look at it and tell you straight what's costing you orders and what it would take to fix — and you can see how I approach restaurant web design before you do.