Key takeaways
- Most guests see your site on a phone; 16% of US adults have no home broadband at all[1].
- Aim for the Core Web Vitals "good" marks: LCP within 2.5 s, INP of 200 ms or less, CLS of 0.1 or less[2].
- Test on a mid-range phone over cellular data, not on the office Wi-Fi laptop.
- The usual culprits are huge photos, PDF menus, pop-ups, sliders and stacked third-party scripts.
Why phone speed is a restaurant problem
A restaurant website has three jobs: show the menu, show the hours and location, and get the guest to book or order. Almost all of that traffic arrives on phones, often on cellular data, often while the guest is standing on a sidewalk deciding between you and the place next door. Ninety-one percent of US adults own a smartphone[3], and 16 percent are smartphone-only internet users with no home broadband[1]. For those guests, the mobile site is the only version of your website.
Ownership is high across ages: 97 percent among adults aged 18 to 49 and 79 percent among those 65 and older[4]. So the "our guests are older and use computers" argument rarely holds up, and the regulars who call to ask about hours are often the ones who could not find them on a slow page.
Source: Pew Research Center, 2026[4]
Show the data
| Item | Value |
|---|---|
| Ages 18–49 | 97% |
| Ages 65 and older | 79% |
Speed matters even more for off-premises guests. Ninety-four percent of consumers say speed is critical when ordering off-premises[5]. A guest who waits eight seconds for your menu to load has already opened a delivery app.
The targets: Core Web Vitals in plain English
Google's Core Web Vitals are the most widely used yardstick for page experience. They measure what a guest feels, not just how many bytes a page has, and they are measured at the 75th percentile of page loads, split by mobile and desktop[2]. That means the slowest quarter of your visitors matter, which on a restaurant site is usually people on older phones and weak signals.
| Metric | What it measures | Good target | Typical restaurant cause when it fails |
|---|---|---|---|
| Largest Contentful Paint (LCP) | How long until the main content, usually the hero photo, appears | 2.5 seconds or less[2] | A full-size camera photo or video as the hero image |
| Interaction to Next Paint (INP) | How quickly the page responds when a guest taps | 200 milliseconds or less[2] | Heavy menu widgets, chat bubbles and stacked tracking scripts |
| Cumulative Layout Shift (CLS) | How much the page jumps around while loading | 0.1 or less[2] | Pop-ups, cookie banners and images without set sizes pushing the menu down |
You do not need to become a developer to use these numbers. Free tools such as PageSpeed Insights show the three metrics for your home page and menu page, using real visitor data when your site has enough traffic and a lab test when it does not. Write down the numbers before you change anything, so you can prove the fixes worked.
Test like a guest, not like a web designer
Use a real mid-range phone
Borrow the oldest phone on the team. Flagship phones on office Wi-Fi hide most problems.
Turn Wi-Fi off
Load the site on cellular data, ideally standing outside the restaurant, where your guests actually are.
Time three tasks
From typing your name in a search to seeing: the menu, today's hours, and the booking or ordering button. Write down each time.
Watch for jumps and blockers
Note every pop-up, cookie banner, newsletter box or chat bubble that covers the menu, and every time the page shifts while you try to tap.
Check the menu itself
Can you read it without pinching and zooming? Can you search it? Does it show prices and dietary notes?
Repeat after each change
Use the same phone, place and tasks so you can compare fairly.
A useful rule of thumb: if any of the three tasks takes longer than a guest would wait in line to ask a host, fix that task first.
Images: the biggest and easiest win
On most restaurant sites the hero photo is the single heaviest thing on the page. A photo straight from a camera or a phone can be several megabytes, while a well-compressed image the width of a phone screen is a small fraction of that and looks the same to the guest.
- Resize photos to the largest size they are shown at. A hero image rarely needs to be wider than a large desktop screen, and phones should get a smaller version made for their width.
- Export in a modern format such as WebP or AVIF, with JPEG as the fallback if your platform needs it.
- Set width and height on every image so the page reserves space and does not jump.
- Lazy-load photos below the first screen so they only download when a guest scrolls.
- Replace autoplay background video with a single still photo on phones.
- Limit galleries on the home page to a handful of images and move the rest to a gallery page.
If your site builder has an image optimization setting, turn it on and re-upload the five biggest photos. It is often a ten-minute fix with the largest effect on LCP.
Remove the add-ons that hide your menu
Restaurant sites collect add-ons over the years: a pop-up for the newsletter, a slider, an embedded social feed, two or three tracking pixels, a review widget, a chat bubble, a font from one service and icons from another. Each one adds scripts that compete for the phone's attention, and together they make taps feel slow.
- List every add-on, script and embed on the home and menu pages. Your web person or the site builder's settings can show them.
- Mark who uses each one and what it is for. Tracking pixels from an agency you no longer use are common.
- Remove anything nobody can name a use for.
- Replace embedded social feeds with a link to your profile and one or two static photos.
- Delay non-essential scripts, such as chat or reviews widgets, until after the page has loaded or until the guest scrolls.
- Replace pop-ups that cover the menu with a small banner at the bottom, or remove them on phones.
The PDF menu deserves its own line. A PDF forces the guest to download a file, zoom and scroll sideways, and it is invisible to many search features. A plain text menu on a web page loads faster, reads better on a phone and is easy to update when you 86 an item. Keep a PDF only as a printable extra.
Put the booking and ordering buttons where thumbs are
Speed is wasted if the guest cannot find the next step. A 2012 Cornell study found that only 9 percent of restaurants that took online reservations offered reservation access on their home page[6]. The study is old, but plenty of sites still bury the booking link in a menu. Put a "Book a table" or "Order pickup" button on the first screen of every page, and a "Call" button that opens the phone dialer.
Mobile ordering is mainstream: 57 percent of adults have recently used it[7]. If your ordering link goes to a third-party page, test that page too, because the guest will blame your restaurant if it is slow.
Readable is part of fast
A page that loads quickly but is hard to read still slows the guest down. Check these on the same phone test:
- Body text large enough to read without zooming, with strong contrast against the background, not pale gray on beige.
- Buttons big enough for a thumb and spaced so guests do not tap the wrong one.
- Address, phone number and hours as real text, not inside an image, so phones can tap to call or open maps.
- Holiday hours and closures at the top of the home page when they apply, not in a social post.
- Alt text on menu and food photos, which helps guests using screen readers and costs nothing in speed.
Example: fixing a slow bistro site in an afternoon
Example: a fictional bistro's home page takes about seven seconds to show the hero image on a three-year-old phone over cellular data, and the menu is a PDF behind a newsletter pop-up. The manager re-exports the hero photo at phone and desktop sizes, removes an unused tracking pixel and an embedded social feed, turns the pop-up off on phones and moves the menu to a text page.
Example: on the same phone and street corner, the hero image now appears in under three seconds, the menu is one tap from the home page, and the booking button sits on the first screen. The manager records the before and after numbers in the same sheet used for the curb and listing checks, and repeats the test every quarter or after any redesign.
Frequently asked questions
How fast should a restaurant website load on a phone?
Aim for the main content to appear within 2.5 seconds (Largest Contentful Paint), measured at the 75th percentile of mobile visits[2].
Is a PDF menu bad for my website?
On phones, usually. A text menu on a web page loads faster, is easier to read and is easier to keep up to date. Offer the PDF only as a printable extra.
What slows restaurant websites down the most?
Oversized photos and video, pop-ups and banners that shift the page, and too many third-party scripts such as old tracking pixels, social feeds and widgets.
How do I test my site speed for free?
Use PageSpeed Insights for Core Web Vitals, and time three tasks on a real mid-range phone over cellular data: menu, hours and booking.
References
Pew Research Center (2026). Americans’ Use of Mobile Devices in 2026 (Fact Sheet) (opens in a new tab) ↑
Google (web.dev) (2024). Web Vitals (opens in a new tab) ↑
Pew Research Center (2026). Americans’ Use of Mobile Devices in 2026 (Fact Sheet) (opens in a new tab) ↑
Pew Research Center (2026). Americans’ Use of Mobile Devices in 2026 (Fact Sheet) (opens in a new tab) ↑
National Restaurant Association (2025). From Trend to Transformation: Off-Premises Dining Now Essential for Restaurant Consumers, Operators (opens in a new tab) ↑
Cornell University Center for Hospitality Research (Kimes and Kies) (2012). The Role of Multi-Restaurant Reservation Sites in Restaurant Distribution Management (Cornell Hospitality Report, 2012) (opens in a new tab) ↑
National Restaurant Association (2025). From Trend to Transformation: Off-Premises Dining Now Essential for Restaurant Consumers, Operators (opens in a new tab) ↑