Restaurant Websites
Restaurant website speed: why a slow site quietly costs bookings
A guest searching "menu" on a phone outside your door will not wait eight seconds for it to load. Speed is where technical SEO stops being abstract: a slow restaurant website loses bookings and rankings at the same time, and the causes are usually boring and fixable.
Alex Opsenica · Founder, Moolah Media
Restaurant searches are disproportionately mobile, impatient and close to a decision. Someone walking down a street comparing two menus, or checking tonight's opening hours in a car park, is measuring your website in seconds. If the page hangs, they do not complain — they go back to the results and pick the restaurant whose menu opened instantly. You never see the booking you lost.
How slow is too slow?
Google measures real-world page experience through a set of measures called Core Web Vitals, drawn from actual visits on actual phones. The headline numbers worth knowing:
| Measure | What it feels like | Good | Poor |
|---|---|---|---|
| LCP — loading | How long until the main content appears | 2.5 seconds or less | Over 4 seconds |
| INP — responsiveness | Whether taps and menus respond immediately | 200 milliseconds or less | Over 500 milliseconds |
| CLS — stability | Whether the page jumps around as it loads | 0.1 or less | Over 0.25 |
LCP — loading
- What it feels like
- How long until the main content appears
- Good
- 2.5 seconds or less
- Poor
- Over 4 seconds
INP — responsiveness
- What it feels like
- Whether taps and menus respond immediately
- Good
- 200 milliseconds or less
- Poor
- Over 500 milliseconds
CLS — stability
- What it feels like
- Whether the page jumps around as it loads
- Good
- 0.1 or less
- Poor
- Over 0.25
One detail worth knowing: Google judges a page on the 75th percentile of real visits, so a page passes only when roughly three in four visits hit the 'good' threshold. A site that feels fine on the owner's new phone and office wifi can still fail on a guest's older handset on mobile data — which is the visit that counts.
It is common for restaurant websites to fail at least one of these on mobile, usually for reasons that have nothing to do with how expensive the site was. You can check any page free with Google's PageSpeed Insights tool — enter your menu page, not just your homepage, because the menu is the page guests actually load.
Source: Google PageSpeed Insights — Free, measures real visitor experience on mobile and desktop for any page on your site.
Source: web.dev — Core Web Vitals thresholds — Google's own definition of the LCP, INP and CLS thresholds and the 75th-percentile rule.
A testing routine that takes ten minutes
- Open PageSpeed Insights and test your menu page — the page guests actually load, not the homepage you are proudest of.
- Read the field data section first. It shows how real visitors on real phones experienced the page over the last month; the lab score below it is a simulation and secondary.
- Note the biggest opportunities listed underneath — they are ordered by impact and usually read like a to-do list: "properly size images", "reduce unused JavaScript".
- Repeat for the homepage and the booking or reservations page.
- Do it once more on your own phone, on mobile data, standing outside: open the menu from a Google search the way a guest would. If it feels slow to you, it is.
The usual causes on restaurant sites
- Photography straight from the camera. A full-resolution dish photo can be twenty times larger than it needs to be; a gallery of them is a mobile disaster. This is the single most common cause.
- Builder themes loaded with features you do not use. Every unused animation, font and plugin ships to every visitor's phone.
- PDF menus. They force a download, open in a separate viewer and are unreadable by search engines — the slowest possible way to show a menu.
- Third-party scripts stacked up over the years: booking widgets, review badges, chat bubbles and tracking tags, each adding its own delay.
- Cheap shared hosting that buckles precisely at 7pm when everyone is looking for dinner.
What slowness actually costs
The cost shows up in three places at once. Guests leave before they reach the menu or the booking button — nobody waiting outside in the rain gives a page a second chance. Google treats page experience as a genuine, if modest, ranking consideration: it says it aims to rank the most useful content even when page experience is poor, but that experience can be the deciding factor between pages of comparable quality — which is precisely the situation you are in against the restaurant two streets away. And every euro spent on ads or social pointing at a slow page buys fewer bookings than it should.
Source: Google Search Central — page experience — Google's statement on how page experience, including Core Web Vitals, factors into ranking.
What to fix first
| Fix | Typical effort | Typical impact |
|---|---|---|
| Compress and resize photos | An afternoon, no specialist needed | Often the single biggest win |
| Replace PDF menu with a text page | Half a day of content work | Speed and rankings together |
| Remove unused plugins and widgets | An hour of deletion | Moderate, and it compounds |
| Replace autoplaying hero video with a still | Minutes | Large on the homepage |
| Move to better hosting | A day of migration | Noticeable at peak hours |
| Rebuild the theme from scratch | Weeks | Rarely needed — try the above first |
Compress and resize photos
- Typical effort
- An afternoon, no specialist needed
- Typical impact
- Often the single biggest win
Replace PDF menu with a text page
- Typical effort
- Half a day of content work
- Typical impact
- Speed and rankings together
Remove unused plugins and widgets
- Typical effort
- An hour of deletion
- Typical impact
- Moderate, and it compounds
Replace autoplaying hero video with a still
- Typical effort
- Minutes
- Typical impact
- Large on the homepage
Move to better hosting
- Typical effort
- A day of migration
- Typical impact
- Noticeable at peak hours
Rebuild the theme from scratch
- Typical effort
- Weeks
- Typical impact
- Rarely needed — try the above first
None of this requires a redesign. Most restaurant speed problems are housekeeping: the site was assembled quickly and nobody ever cleared out what accumulated. A focused afternoon of fixes routinely halves load time.
Common questions
How do I check my restaurant website's speed?
Use Google's free PageSpeed Insights tool and test your menu page on the mobile setting — that is the experience most guests have. The field data section shows how real visitors experience the page, which matters more than any lab score.
Does website speed directly affect my Google ranking?
Yes, but modestly. Page experience is a confirmed ranking input, typically decisive only when you and a competitor are otherwise evenly matched. The bigger effect is indirect: fast pages keep guests, and kept guests book.
My site looks expensive — can it still be slow?
Very often, yes. Speed problems rarely come from how a site looks; they come from oversized photos, feature-heavy themes, accumulated plugins and cheap hosting. Some of the slowest restaurant sites are the most expensive-looking ones.
Is a PDF menu really that bad?
For mobile guests, yes: it is a download, a separate viewer and usually pinch-to-zoom. For search, it is worse — search engines can barely read it, so your dishes, prices and cuisine are invisible to the exact searches you want to win.
Will a booking widget slow my site down?
Any third-party script adds some delay, but a reputable booking widget is usually worth its cost — the booking it captures outweighs a fraction of a second. The problem is accumulation: a booking widget plus a review badge, a chat bubble, a gift-card popup and three tracking tags. Keep the ones that earn, delete the rest, and load the survivors after the main content where possible.
What score should I aim for in PageSpeed Insights?
Treat the field data — real visitor experience — as the target: all three Core Web Vitals in the 'good' range on mobile. The lab score out of 100 is a rough proxy, not a goal in itself; chasing 100 produces diminishing returns and broken features. Green vitals plus a menu that feels instant on a phone is the standard that matters.
Working on this yourself? How Moolah fixes restaurant websites.
Is your website helping or quietly getting in the way?
The audit reviews menu accessibility, location content, structured data and mobile performance, and separates search issues from booking friction.
Get Your Free Visibility AuditWritten by

Alex Opsenica
Founder, Moolah Media
Founder of Moolah Media, a specialist restaurant growth and local SEO agency based in Ireland, working remotely with hospitality operators worldwide on search, Google Business Profile and bookings.
Continue exploring
Restaurant Websites
What every restaurant website needs for search
The website fundamentals that affect restaurant discovery and booking: readable menus, location content, schema and mobile speed.
3 min read
Read InsightRestaurant Websites
Restaurant menu pages that search engines can actually read
Menu pages are the most-visited page on most restaurant sites, and usually a PDF. How to build one that works for guests and for search.
4 min read
Read InsightRestaurant Websites
Restaurant structured data: the schema that actually helps
Which structured data a restaurant website genuinely needs — Restaurant, Menu, opening hours and FAQ — how to implement it, and what it will not do.
4 min read
Read Insight


