Restaurant website speed and search, measured on real sites

What counts as a fast restaurant website

Appetier's free website audit uses Google's tools and Google's thresholds. A site passes the speed check when mobile PageSpeed performance is 90 or more. Core Web Vitals is stricter. It passes only when three lab measurements all land inside Google's good range at the same time. We test on a phone profile first. That's where guests look up a menu on the way over.

• Main content shows in under 2.5 seconds.
• Layout shift stays under 0.1, so buttons don't jump under a thumb.
• Blocking time stays under 200 milliseconds, so taps respond.
• The page sets a mobile viewport, so it isn't a shrunken desktop page.

What we measured on five national chains

Appetier's audit report shows national brands beside a restaurant's own score, so we run the same checks on them. The score is the weight of the checks a site passed, divided by the weight of the checks that could run. On September 24, 2026, the results were below. CAVA was left off because fewer than half of its checks could run.

• Chipotle: 70 out of 100.
• Sweetgreen: 66, and 44 for mobile PageSpeed performance.
• Shake Shack: 56.
• Domino's: 47.
• Panera Bread: 47.

Four of the five sites could not be timed

PageSpeed Insights returned no mobile score for Chipotle, Shake Shack, Domino's, or Panera Bread. Their speed and Core Web Vitals checks were left out of both sides of the score, so each was scored on 86 of 100 points. Sweetgreen was scored on all 100. A large brand can afford a fast site. Sweetgreen's 44 shows that a budget doesn't settle speed by itself. For a smaller restaurant, a site Google can't time is worth knowing about.

• A missing score means Google's test couldn't finish on that page.
• Run your own site in PageSpeed Insights before assuming it's fine.
• A score out of 100 means little until you know how many checks ran.
• Ask whoever runs your site to check that Google's test can load the page at all.

Why a PageSpeed score moves between runs

On September 25, 2026, PageSpeed scored our reference storefront anywhere from 77 to 97 within one hour. Nothing on the page changed between runs. Google tests on shared machines over a simulated phone connection. Both vary. That's how one unchanged page swung 20 points in an hour. Our own measurement now starts three runs at once for each site and keeps the median of the three. Do the same before you judge a site, yours or anyone else's.

• Run PageSpeed Insights three times in a row on the mobile tab.
• Write down all three performance scores.
• Keep the middle one, and ignore the best and the worst.
• Compare two sites only on medians taken the same day.

What our own storefront scores, including the check it fails

Our reference is royal.appetier.com, a live storefront rather than a demo. Lighthouse on mobile scored it 97 for performance, 95 for accessibility, and 100 for SEO on September 25, 2026. That run timed the main content at 2.4 seconds, layout shift at 0.007, and blocking time at 98 milliseconds. The audit's own PageSpeed median that day scored 95. That passes the speed check. In the same run, though, the main content took 2.9 seconds to show, over Google's 2.5. So the audit does not credit Appetier with Core Web Vitals, and neither do we here. We'd rather publish the miss than a number we can't repeat.

• Passes: order button on its own domain, menu as HTML, and menu photos.
• Passes: guest signup, mobile speed, and the mobile viewport.
• Passes: restaurant structured data, title, description, main heading, and HTTPS.
• Passes: canonical link, indexable, sitemap, and the city in the title.
• Fails: Core Web Vitals, on main content timing in one run.

Speed is one check, and not the heaviest

The audit weighs 20 checks, and speed is two of them. The heaviest asks one thing: does your order button keep the guest on your own site? A fast page that sends every order elsewhere still hands that search to another site. Google also reads your listing. It compares the hours, phone, and address there with your website, and a mismatch costs points. Our Google Business Profile audit lists ten checks. See restaurant SEO for what Appetier keeps up to date on Google.

• Order button on your own domain: 14 points.
• Mobile speed: 8 points. Core Web Vitals: 6.
• Menu as HTML, restaurant structured data, and guest signup: 7 points each.
• Page indexable by search engines: 6 points.
• Google listing linked to your site, and a complete listing: 6 points each.
• Phone and street number matching the listing: 4 points.

Test your own restaurant website in ten minutes

You don't need a developer for a first pass. Open your homepage on a phone, then run the free tools below from a laptop. Write down what fails, and fix the heaviest items first.

• Run PageSpeed Insights three times on mobile and keep the median.
• Paste your homepage into Google's Rich Results Test and look for a Restaurant result with name, address, and hours.
• Tap your order button and check which website it opens.
• Check that your menu is text on the page, not a PDF or a photo.
• Open yoursite.com/robots.txt and look for a Sitemap line.
• Read your page title and check that it names your city.

Fixes that move the score, heaviest first

Order the fixes by weight, not by how easy they look. A menu PDF is quick to replace and worth more points than trimming a few scripts. Speed work, such as resizing photos and removing third-party tags, usually takes longer.

• Point the order button at ordering on your own domain.
• Replace a PDF or photo menu with a menu written as text.
• Add Restaurant structured data with your name, address, and hours.
• Put an email or rewards signup on the homepage.
• Resize the hero photo for a phone, and remove tags nobody uses.
• Link your Google listing to your website and fill in hours, phone, and price level.

What an Appetier storefront includes

Every Appetier storefront carries the parts search engines read. Each menu item has its own page. A brand gets its own sitemap and the restaurant data Google reads for name, address, and hours. A published change reaches open storefronts within about a minute. Hours and sold-out items update without publishing. See online ordering for the storefront, and restaurant software for how it fits with loyalty and POS sync.

• A page for every menu item.
• A sitemap for every brand.
• Restaurant structured data with name, address, and hours.
• A weekly check that fixes Google listing hours, links, and categories, once Google is connected.

Restaurant website speed FAQs

• What is a good PageSpeed score for a restaurant website?: 90 or more on mobile performance. Appetier's audit passes the speed check at that line, and Google labels scores from 90 up as good.
• Why does my PageSpeed score change every time?: Google tests on shared machines over a simulated phone connection. One storefront we measured moved from 77 to 97 in an hour, so run it three times and keep the median.
• How did national chains score on your audit?: On September 24, 2026, Chipotle scored 70, Sweetgreen 66, Shake Shack 56, and Domino's and Panera Bread 47 each. Sweetgreen's mobile PageSpeed was 44.
• Does speed matter more than the rest of the audit?: No. Speed and Core Web Vitals are 14 of 100 points. The order button is worth the same 14 by itself, when it keeps guests on your own site instead of sending them elsewhere.
• Does Appetier pass Core Web Vitals?: Not in every run. Our storefront timed its main content at 2.4 seconds in one run and 2.9 in another, so we don't claim it.

Next steps

Run the free audit to see your own score beside the same checks on Appetier. It takes about a minute. From the report, you can ask to see your restaurant on Appetier. See restaurant SEO for what Appetier keeps current on Google.