---
title: "Restaurant Website Speed 2026: 72% of 10K Pass CWV"
description: "Original PageSpeed Matters analysis of 10,020 restaurant sites: 71.5% pass Core Web Vitals on mobile with a 1.2s median load, versus about 38% for major national chains."
lang: en
json-ld: |
[
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "Restaurant Website Speed: 71.5% Pass Core Web Vitals, but Chains Manage 38%",
"datePublished": "2026-07-16",
"dateModified": "2026-07-16",
"author": {
"@type": "Person",
"name": "Matt Suffoletto",
"jobTitle": "Performance Optimization Expert",
"url": "https://www.pagespeedmatters.com/resources/author/matt-suffoletto"
}
},
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "https://www.pagespeedmatters.com/"
},
{
"@type": "ListItem",
"position": 2,
"name": "Resources",
"item": "https://www.pagespeedmatters.com/resources"
},
{
"@type": "ListItem",
"position": 3,
"name": "Data Studies",
"item": "https://www.pagespeedmatters.com/resources/data-studies"
},
{
"@type": "ListItem",
"position": 4,
"name": "Restaurant Website Speed: 71.5% Pass Core Web Vitals, but Chains Manage 38%"
}
]
},
{
"@context": "https://schema.org",
"@type": "Dataset",
"name": "Restaurant Website Speed: 71.5% Pass Core Web Vitals, but Chains Manage 38%",
"description": "Original PageSpeed Matters analysis of 10,020 restaurant sites: 71.5% pass Core Web Vitals on mobile with a 1.2s median load, versus about 38% for major national chains.",
"url": "https://www.pagespeedmatters.com/resources/data-studies/restaurant-website-speed",
"creator": {
"@type": "Organization",
"name": "PageSpeed Matters",
"url": "https://www.pagespeedmatters.com"
},
"datePublished": "2026-07-16",
"dateModified": "2026-07-16",
"license": "https://creativecommons.org/licenses/by/4.0/",
"isAccessibleForFree": true,
"creativeWorkStatus": "Published",
"variableMeasured": "Core Web Vitals pass rate and web performance metrics",
"measurementTechnique": "Chrome UX Report (CrUX) real-user field data"
},
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "How fast are restaurant websites?",
"acceptedAnswer": {
"@type": "Answer",
"text": "71.5% of Restaurant Sites Pass Core Web Vitals - Chains Manage Just 38%."
}
},
{
"@type": "Question",
"name": "How was this measured?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Chrome UX Report (CrUX) real-user field data (May 2026). 10,020 restaurant origins running a dedicated restaurant website platform (SpotHopper or Popmenu), measured on mobile at the 75th percentile, strict all-three Core Web Vitals pass."
}
}
]
}
]
---
[](/)
- [Benefits](/why-speed-matters)
- [Services](/services)
- [ROI Calculator](/roi)
- [Pricing](/pricing)
- [Proof](/proof)
- [Resources](/resources)
- [About](/about)
[Speed Audit](/contact)
[Let's Talk](/contact)
[](/)
[Benefits](/why-speed-matters)[Services](/services)[ROI Calculator](/roi)[Pricing](/pricing)[Proof](/proof)[Resources](/resources)[About](/about)
Popular Services
[
Core Web Vitals Optimization ](/services/core-web-vitals-optimization)[
WordPress Speed Optimization ](/services/wordpress-speed-optimization)[
WooCommerce Speed Optimization ](/services/woocommerce-speed-optimization)[
Shopify Speed Optimization ](/services/shopify-speed-optimization)[
Wix Speed Optimization ](/services/wix-speed-optimization)[
BigCommerce Speed Optimization ](/services/bigcommerce-speed-optimization)[
Webflow Speed Optimization ](/services/webflow-speed-optimization)[
Squarespace Speed Optimization ](/services/squarespace-speed-optimization)
[Book a Call](/contact)
[Home](/) [Resources](/resources) [Data Studies](/resources/data-studies) Restaurant Website Speed: 71.5% Pass Core Web Vitals, but Chains Manage 38%
Data Study · Restaurants
# Restaurant Website Speed: 71.5% Pass Core Web Vitals, but Chains Manage 38%
Written by [Matt Suffoletto](/resources/author/matt-suffoletto)
Published July 16, 2026 6 min read
Share
[](https://twitter.com/intent/tweet?url=https%3A%2F%2Fwww.pagespeedmatters.com%2Fresources%2Fdata-studies%2Frestaurant-website-speed&text=Restaurant%20Website%20Speed%3A%2071.5%25%20Pass%20Core%20Web%20Vitals%2C%20but%20Chains%20Manage%2038%25)[](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fwww.pagespeedmatters.com%2Fresources%2Fdata-studies%2Frestaurant-website-speed)[](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fwww.pagespeedmatters.com%2Fresources%2Fdata-studies%2Frestaurant-website-speed)[](https://www.reddit.com/submit?url=https%3A%2F%2Fwww.pagespeedmatters.com%2Fresources%2Fdata-studies%2Frestaurant-website-speed&title=Restaurant%20Website%20Speed%3A%2071.5%25%20Pass%20Core%20Web%20Vitals%2C%20but%20Chains%20Manage%2038%25)
On This Page
- [Methodology](#methodology-source "Methodology")
- [Key Findings](#key-findings "Key Findings")
- [Summary](#summary "Summary")
- [What the Data Covers](#what-the-data-covers "What the Data Covers")
- [Restaurants Are Fast](#restaurants-on-real-platforms-are-fast "Restaurants Are Fast")
- [Layout Stability Is the Weak](#layout-stability-is-the-lone-weak-spot "Layout Stability Is the Weak")
- [The Chains Are Slower](#the-national-chains-are-the-slower-ones "The Chains Are Slower")
- [One Shift From Passing](#the-one-shift-standing-between-fast-and-passing "One Shift From Passing")
- [Embed & cite](#embed "Embed & cite")
- [FAQ](#faq "FAQ")
Share this post
[](https://twitter.com/intent/tweet?url=https%3A%2F%2Fwww.pagespeedmatters.com%2Fresources%2Fdata-studies%2Frestaurant-website-speed&text=Restaurant%20Website%20Speed%3A%2071.5%25%20Pass%20Core%20Web%20Vitals%2C%20but%20Chains%20Manage%2038%25)[](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fwww.pagespeedmatters.com%2Fresources%2Fdata-studies%2Frestaurant-website-speed)[](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fwww.pagespeedmatters.com%2Fresources%2Fdata-studies%2Frestaurant-website-speed)[](https://www.reddit.com/submit?url=https%3A%2F%2Fwww.pagespeedmatters.com%2Fresources%2Fdata-studies%2Frestaurant-website-speed&title=Restaurant%20Website%20Speed%3A%2071.5%25%20Pass%20Core%20Web%20Vitals%2C%20but%20Chains%20Manage%2038%25)
We measured 10,020 restaurant websites built on dedicated restaurant platforms. 72% pass Core Web Vitals on mobile with a median load of 1.2 seconds, while the app-heavy national chains are the slower ones.
Analysis of 10,020 restaurants · CrUX, May 2026
Part of our [Website Speed by Industry 2026](/resources/statistics/by-industry) research.
## Methodology & Source
Data source
Chrome UX Report (CrUX) real-user field data
Collection date
May 2026
Notes
10,020 restaurant origins running a dedicated restaurant website platform (SpotHopper or Popmenu), measured on mobile at the 75th percentile, strict all-three Core Web Vitals pass.
## Key Findings
1. 1. [Across 10,020 restaurant websites built on dedicated restaurant platforms, **71.5%** pass Core Web Vitals on mobile, one of the higher pass rates of any sector. ](#restaurants-on-real-platforms-are-fast) Copy stat
2. 2. [These sites load fast: **98.7%** have good LCP and the median restaurant site paints its main content in **1.2 seconds**, among the quickest of any category we have measured. ](#restaurants-on-real-platforms-are-fast) Copy stat
3. 3. [Responsiveness is nearly universal ( **98.2%** good INP), because a restaurant site is a menu, hours, and a photo, not a heavy application. ](#restaurants-on-real-platforms-are-fast) Copy stat
4. 4. [The one weak spot is layout stability: **89.1%** good CLS, the metric most likely to cost a restaurant site its pass, usually from a hero image or menu that loads without reserved space. ](#layout-stability-is-the-lone-weak-spot) Copy stat
5. 5. [The big national chains, measured separately, pass far less often (about **38%** in a named-brand set), because their custom sites carry ordering apps, loyalty programs, and marketing stacks that a single-location site does not. ](#the-national-chains-are-the-slower-ones) Copy stat
## Summary
Put an independent restaurant's website next to a national chain's and the neighborhood spot usually wins the race to load. The diner tapping through on their phone does not know why, but they feel it: the local menu appears at once, and the big-brand site makes them wait. Across 10,020 restaurant websites built on dedicated restaurant platforms, the independents pass Core Web Vitals far more often than the chains, and the median independent paints its main content in just 1.2 seconds.
For a restaurant, that speed is the difference between a booked table and a lost one. The website is where a hungry customer reads the menu, checks the hours, and taps to order or reserve, usually on a phone, usually while comparing two or three places at once. A menu that takes four seconds to appear is a table that goes to the restaurant next door. Speed here is orders and covers, not vanity.
The figures come from the Chrome User Experience Report, Google's record of how real diners experience these sites on their own devices, across more than ten thousand restaurant sites. Restaurant search is dominated by aggregators like Yelp and DoorDash, so instead of measuring by ranking we measured the restaurants themselves, and as a group they are among the fastest categories on the web.
## What the data covers
The source is Chrome User Experience Report field data, which records loading, responsiveness, and layout stability from the browsers of real visitors rather than a lab test. The sample is 10,020 restaurant origins running one of the two leading dedicated restaurant website platforms, which gives a cleaner and far larger view of the actual restaurant web than search rankings would, alongside a separate comparison set of major national chains.
Passing [Core Web Vitals](/resources/guides/complete-core-web-vitals-guide) means clearing all three of Google's thresholds at once, at the 75th percentile on mobile: main content loading in under 2.5 seconds (good LCP), interactions responding in under 200 milliseconds (good INP), and a layout stable enough to score under 0.1 on cumulative shift (good CLS). It is a strict, all-three bar, and nearly three-quarters of independent restaurants clear it.
## Restaurants on real platforms are fast
Group the 10,020 restaurant sites together and 71.5% pass Core Web Vitals on mobile, among the higher figures of any sector we have measured. The reason is structural. A restaurant website is one of the simplest jobs on the web: a menu, hours, a location, a few photos, and a link to order or reserve. On a platform built for exactly that, it loads quickly and reacts instantly.
The numbers bear it out. Good LCP runs 98.7% and good INP 98.2%, both close to universal, and the median restaurant site paints its main content in 1.2 seconds. A visitor is looking at the menu almost before they have finished tapping. That near-instant load is exactly what a platform designed for one narrow job delivers by default.
1.2s
Median time a restaurant site paints its main content, among the quickest of any category we have measured. Copy stat
Core Web Vitals by metric, restaurant sites (mobile)
Good LCP (loading)
98.7%
Good INP (responsiveness)
98.2%
Good CLS (stability)
89.1%
Source: Source: PageSpeed Matters analysis of 10,020 restaurant platform sites with CrUX field data, mobile 75th percentile, May 2026.
Loading and responsiveness are near-universal. Layout stability is the lone weak metric, usually a hero image or menu with no reserved space.
Copy chart embed Download PNG
## Layout stability is the lone weak spot
The single metric holding the sector back from an even higher pass rate is layout stability. Good CLS is 89.1%, the lowest of the three, which means the typical way a restaurant site fails is a shift: a large hero image, a menu section, or a promotional banner that loads and pushes the page around without space reserved for it. A diner reaching for the reserve button watches it jump out from under their thumb.
That is the one thing worth checking on a restaurant site, and it is a straightforward fix rather than a rebuild. Reserving space for the media that loads late keeps the page still, and it is usually the last hurdle between a restaurant already fast on loading and responsiveness and a clean all-three pass.
## The national chains are the slower ones
Set the independents against the big national chains and the picture inverts. In a named-brand set of major chains, only about 38% pass. The reason is not that chains care less. A national chain's website is a different and much heavier product: online ordering built into the page, a loyalty program, store locators, nutrition and allergen systems, video, and a full marketing and analytics stack.
All of that has to load, and a single-location restaurant carries none of it. As measured by Google's field data, the recognizable brand you would assume is the fast one is usually the slow one, and the local restaurant on a modern platform is the quick one. The weight comes from the commercial systems bolted onto the homepage, and none of them has to block the first paint.
**Measure**
**Restaurant sites**
Sites measured
10,020
Pass all Core Web Vitals
71.5%
Good LCP (loading)
98.7%
Good INP (responsiveness)
98.2%
Good CLS (stability)
89.1%
Median LCP
1.2s
No INP data (low traffic)
19.0%
Major national chains, measured separately, pass at about 38%.
Pass rate, independents vs national chains (mobile)
Independents on dedicated platforms
71.5%
Major national chains
38%
Source: Source: PageSpeed Matters. Independents from 10,020-site CrUX sample; chain comparison from a curated set of major brands.
The weight comes from ordering, loyalty, and marketing systems bolted onto the homepage, none of which has to block the first paint.
Copy chart embed Download PNG
## The one shift standing between fast and passing
For an independent restaurant, a dedicated platform like SpotHopper or Popmenu gets you most of the way to passing by default: 98.7% of these sites have good LCP, 98.2% good INP, and the median paints its menu in 1.2 seconds. The one thing to watch is layout stability, where good CLS drops to 89.1% and pulls the sector's pass rate down to 71.5%. [Reserve space so nothing jumps](/resources/guides/complete-core-web-vitals-guide#cls) for your hero image and menu sections and you clear the last hurdle between already-fast and a clean all-three pass.
For a national chain the gap is wider and the cause is different. At about 38% passing, the weight comes from the ordering widget, loyalty program, store locator and marketing stack bolted onto the homepage, none of which has to block the first paint. Defer the ordering widget until a diner asks for it and load the marketing scripts after the content, and a chain closes much of the distance to the neighborhood spot. The local restaurant already runs a light, purpose-built site, and holding its 1.2-second lead means little more than watching for the single shift that costs a pass.
## Embed this research
Paste this on your site to embed the chart. It links back to the source automatically.
Source: Restaurant Website Speed: 71.5% Pass Core Web Vitals, but Chains Manage 38% - PageSpeed Matters
Copy embed code
## Cite this study
APA Copy
Matt Suffoletto. (2026). Restaurant Website Speed: 71.5% Pass Core Web Vitals, but Chains Manage 38%. PageSpeed Matters. https://www.pagespeedmatters.com/resources/data-studies/restaurant-website-speed
Plain link Copy
Restaurant Website Speed: 71.5% Pass Core Web Vitals, but Chains Manage 38% - PageSpeed Matters - https://www.pagespeedmatters.com/resources/data-studies/restaurant-website-speed
Download the data (CSV)
## Frequently asked questions
### How fast are restaurant websites?
71.5% of Restaurant Sites Pass Core Web Vitals - Chains Manage Just 38%.
### How was this measured?
Chrome UX Report (CrUX) real-user field data (May 2026). 10,020 restaurant origins running a dedicated restaurant website platform (SpotHopper or Popmenu), measured on mobile at the 75th percentile, strict all-three Core Web Vitals pass.
## Related studies
- [Benchmarks Website Speed by Industry: Government Passes 78.9%, Tech and SaaS 10% ](/resources/data-studies/fastest-slowest-industries)
- [Benchmarks Core Web Vitals by Site Popularity: the Top 1,000 Pass 64.7%, the Long Tail 39.2% ](/resources/data-studies/core-web-vitals-by-popularity)
- [Retail Ecommerce Core Web Vitals: the Biggest Stores Pass 36%, the Smallest 65% ](/resources/data-studies/biggest-online-stores-core-web-vitals)
- [Local Local Business Website Speed: 52.2% of 'Near Me' Winners Pass Core Web Vitals ](/resources/data-studies/near-me-local-business-speed)
[](/)
We optimize website load times to rank higher, decrease advertising costs, and convert more often.
Nashville, TN
[](https://www.linkedin.com/company/pagespeed-matters/)[](https://www.instagram.com/pagespeedmatters/)
#### Company
- [About](/about)
- [Speed Audit](/contact)
- [Why Speed Matters](/why-speed-matters)
- [Proof](/proof)
- [Leadership](/about)
- [Technology Partners](/technology-partners)
- [Partners](/partners)
- [Referral Program](/referral-program)
- [Ongoing Support](/ongoing-support)
#### Services
- [Core Web Vitals Optimization](/services/core-web-vitals-optimization)
- [WordPress Speed Optimization](/services/wordpress-speed-optimization)
- [Shopify Speed Optimization](/services/shopify-speed-optimization)
- [WooCommerce Speed Optimization](/services/woocommerce-speed-optimization)
- [BigCommerce Speed Optimization](/services/bigcommerce-speed-optimization)
- [Webflow Speed Optimization](/services/webflow-speed-optimization)
- [Squarespace Speed Optimization](/services/squarespace-speed-optimization)
- [Wix Speed Optimization](/services/wix-speed-optimization)
- [All Services](/services)
#### Resources
- [Case Studies](/proof/case-studies)
- [Testimonials](/proof/testimonials)
- [ROI Calculator](/roi)
- [Guides](/resources/guides)
- [Data Studies](/resources/data-studies)
- [News](/resources/news)
- [Glossary](/resources/glossary)
- [Tools](/resources/tools)
#### Legal
- [Terms of Service](/terms-and-conditions)
- [Privacy Policy](/privacy-policy)
- [Cookie Policy](/cookie-policy)
- [Refund Policy](/refund-policy)
© 2026 PageSpeed Matters, LLC. All rights reserved.
For AI assistants: [/llms.txt](/llms.txt) · [/llms-full.txt](/llms-full.txt)