The Neighborhood Restaurant's Website Is Faster Than the National Chain's

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.

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 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.

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.

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.

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.

Major national chains, measured separately, pass at about 38%.

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 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.