Why your restaurant website gets visits but not orders

If your restaurant website gets visits but not orders, guests are leaking out somewhere between landing and paying. The usual leaks are a hidden order button, a menu that’s hard to use on a phone, a slow page, a long checkout, surprise fees, or an order link that sends guests off to another app. Measure each step, find the biggest drop, and fix that one first.

This guide is about turning visits into orders. If you’re still building the basics (hours, address, accessibility, photos), start with our restaurant website must-haves checklist, then come back here.

Is it a traffic problem or an orders problem?

Start with one number: your order rate.

Order rate = online orders ÷ website visits, for the same week.

• Few visits, decent order rate: guests who find you do order. Your problem is being found. See why your restaurant isn’t showing up on Google.
• Lots of visits, low order rate: guests find you but don’t buy. That’s what this guide fixes.

Be fair to your site, though. Many visitors only want your hours, phone number or directions, and they’ll never order online. That’s fine. You’re looking for guests who started an order and gave up.

What does the funnel math look like?

An online order is a series of steps, and some guests drop out at each one. Here’s a made-up example for one week, to show how it works:

Step	Guests	Share who move on
Visit the website	1,000	60% open the menu
Open the menu	600	30% add something to the cart
Add to cart	180	67% start checkout
Start checkout	120	60% finish paying
Order placed	72	Order rate: 7.2%

Now fix just one step. If checkout completion goes from 60% to 75%, the same 120 guests give you 90 orders instead of 72. That’s 18 more orders a week, or 25% more, with zero extra traffic. At a $35 average order, it’s about $630 a week.

Two lessons:

1. Find the biggest drop first. In this example, 70% of menu visitors never add anything. That’s the first place to look.
2. Fixes multiply. A small gain at three steps beats a big push for more traffic.

Can guests see how to order on the first screen?

On a phone, guests should see a clear Order online button without scrolling. One main button, in a color that stands out, with plain words. “Order pickup” beats “Explore our culinary journey.”

Common leaks:

• The button is hidden in a hamburger menu.
• A big photo slideshow pushes everything below the fold.
• There are five buttons of equal size, so none stands out.
• A pop-up for the newsletter covers the screen on arrival.

Keep the order button visible as guests scroll, for example in a sticky bar at the bottom of the phone screen.

Do guests know you’re open and when their food will be ready?

A guest at 4:45 p.m. wants to know two things: are you open, and when can they pick up?

• Show “Open now” or “Opens at 5 p.m.” near the order button, not just a weekly hours table at the bottom.
• Offer pickup times. “Ready in about 20 minutes” or a choice of times (5:30, 5:45, 6:00) removes doubt. Without it, guests call instead, or give up.
• When you’re closed, take orders for later. A guest browsing at 10 p.m. can place tomorrow’s lunch order if you let them pick a time.
• Keep the address and a tap-to-call number one tap away, for guests who want to check before paying.

Is your menu easy to order from?

A menu that’s fine to read can still be hard to order from.

• Text, with prices, on the page. A PDF or image menu can’t be added to a cart. Guests have to remember the dish, find it again in a separate ordering page, and hope the price matches.
• Clear sections (starters, mains, sides, drinks) with a sticky category bar so guests can jump around.
• Photos of your best sellers. You don’t need a photo of every dish. Good photos of your top ten sell those dishes and set expectations.
• Simple choices. If every dish opens a long form of options, guests stall. Ask only what the kitchen needs, like spice level or size.
• Show what goes together. A suggested side or drink at the cart step is helpful, not pushy, if it’s one suggestion and easy to skip.

Is it too slow on a phone?

Google’s Core Web Vitals guidance says the main content should load within 2.5 seconds, and the page should respond to a tap within 200 milliseconds. In 2016 Google reported that 53% of mobile visitors leave a page that takes longer than three seconds to load.

Restaurant ordering pages are often slow because of huge photos, many add-on scripts, chat widgets and video. Test it yourself: open your menu on your phone using mobile data, and count how long until you can tap a dish. Then add something to the cart and check that it responds right away.

How many steps is your checkout?

Baymard Institute’s research puts the average documented online cart abandonment rate at about 70%, across 50 studies. Among shoppers who left during checkout (not just browsing), 18% said the site wanted them to create an account and 17% said checkout was too long or complicated.

For a restaurant, a good phone checkout looks like this:

1. Guest checkout. Name, phone and email. No password.
2. Pickup or delivery, and a time, chosen in one tap.
3. Pay in one step, with a phone wallet or a saved card where your payment setup supports it.
4. A clear confirmation on screen and by email or text, with the pickup time and address.

Count the taps from “add to cart” to “order placed” on your own phone. Every screen you remove is fewer guests lost.

Are surprise fees showing up at the end?

This is the biggest single reason in Baymard’s data: 40% of shoppers who abandoned checkout said extra costs like shipping, tax or fees felt too high. For restaurants that means service fees, packaging fees, card fees and delivery charges that first appear on the last screen.

• Show fees early, on the menu or cart, not only at payment.
• Show the total with tax before the guest taps Pay.
• Check your local rules. Some states and cities have rules about how restaurants must show fees. See our restaurant fee laws page.

A guest who sees a $3 fee upfront usually accepts it. A guest who discovers it at the end often feels tricked and leaves.

Does your order button send guests to someone else’s app?

Many restaurant sites link “Order online” straight to a delivery app. That adds a hop, a new page to load and sometimes a login. App pages also show other restaurants, promotions and “you might also like” listings, so some guests order from someone else.

Many guests are happy to order direct. NCR Voyix’s 2025 Customer Experience Report, as covered by Restaurant Dive, found 58% of US consumers favor ordering delivery through a restaurant’s own app or website, mostly for convenience. Give them a way to do it without leaving your site. If you also list on apps, keep your own ordering as the first and biggest button. Our guide to delivery app fees shows what each app order costs you.

Do guests trust you enough to pay?

Paying a restaurant they found five minutes ago is a small leap of faith. Reduce the doubt:

• Show your rating and a few recent reviews near the menu or order button. BrightLocal’s 2026 survey found 74% of consumers only consider reviews from the last three months, and 68% want at least four stars. See how to get more Google reviews.
• Use a secure checkout (https, a familiar payment form) and show which cards and wallets you accept.
• Show real photos of your food and storefront, so the guest knows they’re in the right place.
• Be clear about pickup: where to go, where to park, what to say at the counter.

How do you track orders on your website?

You can’t fix what you can’t see. Set up tracking once, then check it weekly.

In Google Analytics 4, Google’s recommended events for online sales include:

Event	What it tells you
view_item	A guest opened a dish
add_to_cart	A guest added a dish
begin_checkout	A guest started checkout
purchase	A guest paid

Mark purchase as a key event. Many ordering systems can send these for you; ask your provider. If yours can’t, you can at least compare website visits with orders from your POS.

Every week, write down:

• Website visits
• Menu views
• Carts started
• Orders placed
• Order rate (orders ÷ visits)
• Average order value

Compare the same week to the week before and the same week last month. When you change something, change one thing at a time, so you know what worked.

Which fix should you try first?

Match the biggest drop in your numbers to the most likely cause:

Where most guests drop off	Check first	Then check
Visit, but never open the menu	Order button not on the first screen	Pop-ups, slow home page
Open the menu, add nothing	Menu hard to use on a phone, no prices, slow photos	Closed with no “order for later” option
Add to cart, never start checkout	Surprise minimums or fees in the cart	No pickup time shown
Start checkout, never pay	Forced account, long form, few ways to pay	Fees added on the last screen, errors
Pay, but never order again	No confirmation or follow-up	No reason to come back, like rewards

Most restaurants find one or two of these are responsible for most of the lost orders.

A one-hour test you can run today

1. Order from your own site on your phone, on mobile data, as a new guest.
2. Time it from opening the site to the confirmation screen.
3. Count the taps and screens. Write down every time you hesitated.
4. Note every surprise: a fee, a forced login, a missing pickup time, a slow page.
5. Ask two friends to do the same and watch without helping. Where they pause is where real guests leave.
6. Fix the worst problem this week, then measure for two weeks.

How WhatsTable helps

WhatsTable gives you a restaurant website with online ordering on your own site, pickup times guests choose in a tap, and a short phone checkout, including Apple Pay on iPhone for Clover restaurants. After each order, guests get a confirmation, and later a review request and rewards points that bring them back. It works with Clover, Toast, Square or WhatsTable’s own POS, and costs $0 a month, plus 5–10% of the sales that come through WhatsTable. See online ordering.