It is 6:40 on a Friday night. Someone three blocks away is hungry, holding a phone, and trying to decide where dinner is coming from. They search for your restaurant, tap through to your website, and start looking for three things: whether you are open, what you serve, and how to order.
If they find all three in under a minute, you probably get the order. If the hours say you closed an hour ago, or the menu is a blurry PDF that takes forever to open, or the “Order Online” button leads to a page that no longer works, they go back to the search results and pick the next place. They do not call to ask. They do not leave a note. They just leave.
That is the quiet problem with restaurant websites. The failures rarely look dramatic from your side of the counter, because the kitchen is busy and the tickets are still printing. What you never see are the orders that almost happened. Before the next rush, whether that is a big game weekend, a holiday, a local festival, or just the regular Friday dinner crowd, it is worth fixing the handful of things that decide whether a hungry visitor becomes a paying customer.
Your hours have to match everywhere a customer looks
Hours sound like the easiest thing on the whole website. They are also the thing restaurants get wrong most often, because hours change more than anything else about the business.
You shorten lunch service for the winter. You close on Mondays for a season. The kitchen stops taking online orders thirty minutes before the dining room closes. You close early on Christmas Eve and open late on New Year’s Day. Each of those changes makes perfect sense inside the restaurant, and each one creates a chance for the website to say something different from what is actually happening.
The customer does not care which version is the official one. If your website says you are open until 10 and the door is locked at 9, that is a broken promise, and it is one they remember the next time they are deciding where to eat. The reverse costs you just as much. If an old holiday closure is still posted on your homepage, people who would happily have ordered assume you are closed and never check.
The tricky part is that your website is only one of the places your hours live. Your Google Business Profile shows hours right in the search results, often before anyone clicks through to your site. Google gives restaurants tools for handling this properly. You can set special hours for holidays and events so your regular schedule stays intact, and Google’s own guidance recommends confirming your hours for official holidays even when they are unchanged, so customers know the listing is accurate. The same help page explains that businesses with separate delivery and takeout hours can list those as additional hours instead of cramming everything into one schedule.
That matters for restaurants in particular, because “open” can mean three different things. The dining room might run until 10, takeout until 9:30, and delivery through a third-party app until 9. If your website lists only one set of hours, somebody is going to be disappointed.
So the first fix is simple to describe and surprisingly hard to keep up with: pick one source of truth for your hours, and make sure the website, the Google listing, and every ordering platform all say the same thing. Put your hours where a phone user sees them without scrolling, usually near the top of the homepage and again in the footer. If online ordering has its own cutoff time, say so plainly next to the order button.
A menu people can actually read on a phone
For a lot of restaurants, the menu page is the most visited page on the entire site. It is also the page most likely to be a PDF.
It is easy to see how that happens. The designer who made your printed menu hands you a file, someone uploads it, and now the website has a menu. On a desktop computer it might even look fine. On a phone, which is where most of your hungry visitors are, it usually means waiting for a large file to download, then pinching and zooming around a page designed for paper while trying to find the price of a burrito.
The usability researchers at Nielsen Norman Group have been studying this for more than twenty years, and their conclusion is blunt: PDFs are still unfit for reading online. They are slow to load, sized for paper instead of screens, and hard to navigate on mobile. In one of their studies, a cafeteria menu stored as a PDF took almost three minutes to download, and the frustrated participant said that by that point they really did not care what was for lunch. Your customers feel exactly the same way, except they have other restaurants to choose from.
A menu built as a regular web page solves most of this. The text is readable at phone size without zooming. Sections like appetizers, entrees, and drinks can be jumped to quickly. Prices, dietary notes, and spice levels can sit right next to each item. And when a dish changes, updating a line of text is far easier than redesigning and re-uploading a whole file.
There is a search benefit too. Google uses the mobile version of a site’s content for indexing and ranking, which means what your site shows on a phone is what Google primarily looks at. A menu that lives as readable text on a mobile-friendly page gives Google something to understand when someone nearby searches for the dishes you actually serve. A menu locked inside an image or a clunky file gives it much less to work with.
Accuracy matters as much as format. Before a busy stretch, read your website menu line by line against what the kitchen is actually cooking. Seasonal items that ended in August, prices that went up in the spring, and the dish you stopped making because a supplier changed all create the same bad moment: a customer decides what they want, goes to order it, and finds out it does not exist. If you offer a paper-style PDF for people who want to print it, keep it as an extra, with the real menu living on the page itself.
The path from “I’m hungry” to “order placed”
Hours and menu get someone interested. The order path is where the money actually changes hands, and it is the part of a restaurant website most likely to be quietly broken.
Start with the button itself. On a phone, a visitor should see a clear way to order without hunting for it. That usually means an “Order Online” or “Order Pickup” button near the top of the homepage and on the menu page, with wording that matches what happens next. If you offer pickup through your own system and delivery through an app, say that clearly so people are not guessing which button does what.
Then follow the link, which is where problems tend to hide. Restaurants switch ordering platforms more often than most businesses switch anything. You moved from one online ordering tool to another last year, but the old link is still in the footer. Your delivery partner changed its URL structure, and now the button on your catering page goes to an error. Your point-of-sale company launched a new ordering page, and the website still points at the old one. None of this sends you an alert. The only sign is a slow trickle of customers who give up.
Speed plays a bigger role here than most owners realize. A hungry person on a cellular connection has very little patience for a page that loads in pieces. Google’s web.dev team has collected research on why speed matters for real businesses, including the finding that the BBC lost an additional 10% of users for every extra second its site took to load. A restaurant homepage weighed down by a giant autoplay video, a dozen oversized photos, and a pile of plugins can easily cost you those seconds, and on a Friday night those seconds turn into lost tickets.
A few other details make a noticeable difference on mobile:
- Make your phone number tappable so people can call with one touch instead of copying digits.
- Link your address to a map so someone picking up can get directions without retyping anything.
- Keep popups to a minimum; an email signup box that covers the order button is working against you.
- If you charge service fees or have a minimum for delivery, say so before checkout rather than surprising people at the last step.
Run the test your customers are running
The most useful thing you can do this week takes about ten minutes. Pick up your own phone, turn off Wi-Fi so you are on a normal cellular connection, and search for your restaurant the way a stranger would. Then try to place an order.
Notice how long the homepage takes to show something useful. Check whether the hours you see in Google match the hours on your site. Open the menu and see whether you can read it without zooming. Tap every order button you can find, including the ones in the footer and on secondary pages, and make sure each one lands somewhere that actually works. If you have a catering page or a gift card page, try those too.
Most owners who do this find at least one thing they did not know was broken. That is good news, because it is far better to find it on a Wednesday afternoon than to have a few dozen customers find it for you during the dinner rush.
Why these fixes keep coming undone
Here is the frustrating part. You can fix every one of these issues today and still find half of them broken again in six months.
Restaurants change constantly. Menus rotate with the seasons and with supplier prices. Hours shift with staffing and the calendar. Ordering platforms come and go. Each change needs to be reflected on the website, and in most restaurants, nobody’s job description includes “keep the website accurate.” The owner is running the business, the manager is running the floor, and the person who built the site either moved on or charges for every small edit, so updates wait until someone has time. During a busy season, nobody has time.
Behind the visible issues are the technical ones you may never see directly. The plugins that run your site need updates. The security certificate that puts the padlock in the browser has to renew on schedule. The hosting needs to stay fast when traffic spikes, which is exactly when a slow or crashing site hurts most. A site that nobody is responsible for tends to drift, one small problem at a time, until the Friday night when a customer runs into all of them at once.
This is the real reason restaurant websites fall behind. Each fix on its own is quick. What restaurants lack is someone who owns the website and keeps it matched to the restaurant, week after week, without the owner having to remember to ask.
Keep your website ready for the next rush
Before your next busy stretch, focus on the three questions every hungry visitor is asking. Are you open? What can I get? How do I order it? If your website answers all three clearly and quickly on a phone, you will win orders you are currently losing without ever knowing it.
A NorthMac managed website takes that ongoing work off your plate. Your site is built, hosted, updated, secured, monitored, and supported for one monthly price, and when your hours change for a holiday, the menu gets a new special, or you switch ordering platforms, you send a request and we make the update. Unlimited update requests are handled one at a time by a team that already knows how your site is put together, so your website keeps pace with your restaurant all year.
You can see everything that is included, and when you are ready for your website to be handled, start your managed website for $47. That gets your build underway now, well before the next online order rush.
