Key points at a glance
- Most guests open your website on a phone and on the go, often with a patchy connection. For them, every second until they see opening hours, menu and booking counts.
- Google measures user experience with three Core Web Vitals: loading time of the largest content (LCP), response to input (INP) and layout shifts (CLS).
- The biggest slowdown is almost always oversized photos. Cropped properly and saved as WebP or AVIF, they become many times smaller without looking any worse.
- PDF menus, embedded social media feeds, sliders, background videos and lots of plugins in site builders cost a great deal of time on phones.
- With Google's free PageSpeed Insights you can test your page in a minute. What matters is the mobile view, not the desktop one.
This post is general information and does not replace legal or tax advice. Rules change and some differ between federal states: check the details with your chamber of commerce (WKO) or IHK, the competent authority or your tax adviser.
Why loading speed matters so much for venues
People usually look for a place to eat just before they decide: on the way home from the office, while strolling through the old town, in the car on a day trip. Guests see your venue in Google Maps or your Google Business Profile, tap “Website” and expect an answer right away. On a phone the connection is often worse than at home: between tall buildings, in basement venues, in mountain valleys or on a network overloaded by a street festival.
A slow page therefore costs you guests quite directly. Someone staring at a white screen for ten seconds does not call and does not book; they choose the next venue on the list. Then there is the search engine: Google recommends good Core Web Vitals and takes user experience into account in its ranking systems. Content and relevance still matter more, but between similarly good pages, speed can make the difference. How loading speed, content and listings work together is explained in the guide to local SEO.
Core Web Vitals in plain words
The Core Web Vitals are Google's way of describing how a page feels to real visitors. There are three metrics, each with a target value that Google rates as “good”. They are not measured on a single visit but across many: a page counts as good when at least 75 percent of visits reach the target, separately for phones and desktops.
| Metric | What it measures | Good according to Google | Typical cause at venues |
|---|---|---|---|
| LCP (Largest Contentful Paint) | When the largest visible element has finished loading, usually the big header photo | Up to 2.5 seconds | Huge header photo, slow hosting, slider with several images |
| INP (Interaction to Next Paint) | How quickly the page reacts to a tap, for example on the menu or a button | Up to 200 milliseconds | Lots of third-party scripts, heavy site builder plugins |
| CLS (Cumulative Layout Shift) | How much content jumps around while loading | Up to 0.1 | Images without a fixed size, banners and pop-ups that appear late |
In everyday terms: the header photo of your dining room or signature dish should appear quickly, the “Book a table” button should respond immediately, and the phone number must not jump down at the last moment so that the guest taps a voucher banner instead. That last point annoys many guests more than a few tenths of a second of loading time.
Testing with PageSpeed Insights
Google's free tool PageSpeed Insights shows you within a minute how fast your website is and what is slowing it down. You need no account and no technical knowledge.
Enter the address
Open pagespeed.web.dev, paste the address of your home page and click “Analyze”. Then test your menu and booking page as well.
Choose the “Mobile” view
PageSpeed Insights shows the mobile results first. Desktop values usually look better but say less about guests on the go.
Read the field data
At the top, if there are enough visits, you see the values of real Chrome users over the last 28 days. This is the assessment that counts for the Core Web Vitals.
Lab data and performance score
Below that, Google simulates a visit on an average phone and gives a performance score from 0 to 100. It varies a little from test to test and is mainly useful for troubleshooting.
Work through the suggestions
Under “Diagnostics” you can see what is slowing things down, such as oversized images or render-blocking scripts. Start with the items that save the most time.
Compressing photos: the biggest lever
Photos sell food, atmosphere and rooms, and they belong on every hospitality website. A photo straight from a phone or a photographer's camera, however, is often several megabytes and 4,000 pixels wide or more. On a phone it is displayed at about 400 pixels wide. So the guest downloads many times what they actually see. On a home page with a header photo, a gallery and team pictures, this quickly adds up to an amount of data that takes noticeable time on mobile data.
Crop
Resize photos before uploading to the size at which they are shown. For a large header photo around 2,000 pixels wide is usually enough, for gallery images much less.
Modern format
Use WebP or AVIF instead of JPEG or PNG. According to Google, WebP images are typically around 25 to 35 percent smaller than comparable JPEG and PNG files.
Compress
Use an image editor or a free online tool to lower the quality until you can no longer see a difference on screen.
Serve several sizes
Good website systems automatically create smaller versions for phones and larger ones for big screens. Ask whether yours does.
Load lower images later
Load images further down the page only when the guest scrolls there (lazy loading). The header photo at the very top, on the other hand, should load immediately, or your LCP suffers.
Also give every image a fixed width and height in the page code, so that the space is reserved before it loads and nothing shifts. How to get good photos in the first place, even with a phone, is covered in the guide to food photography.
PDF menus: slow and awkward
Many venues upload their printed menu as a PDF. It is quick to do, but for guests on a phone it is often the worst option. A PDF with photos and embedded fonts can be several megabytes, opens in a separate app or downloads depending on the phone, and the text is barely readable without zooming. Someone who just wants to check on the move whether there are vegetarian dishes often gives up here.
| PDF menu | Menu as text on the website | |
|---|---|---|
| Loading time on phones | Often slow, especially with photos | Fast, loads with the page |
| Readability | Zooming and swiping needed | Adapts to the screen |
| Google and AI assistants | Content hard to process | Dishes and terms easy to find |
| Accessibility | Often difficult for screen readers | Accessible if built cleanly |
| Changes | Create and upload a new file | Edit a single dish or price directly |
A menu as text is faster, easier to read and findable on Google. How to build and maintain one is explained in the guide to the digital menu. If you also want to offer a print-ready version for parties or catering, link the PDF as an extra, not as the only menu. For the tables, the menu QR code creates a table stand that leads straight to the text menu.
Bloat in site builders and templates
Site builders and ready-made templates are convenient, but they often bring a lot of code your page does not need. Every extra feature loads its own scripts, fonts and styles, even if it is only used on one subpage. On a fast office computer you hardly notice; on a budget phone on mobile data you certainly do. Typical slowdowns on hospitality websites:
- Image sliders and background videos on the home page: several large files before the guest can read anything.
- Embedded Instagram or Facebook feeds: they load third-party scripts and often dozens of images. A link to your profile is faster.
- Embedded maps: an interactive map loaded right away takes time. An image of the map with a link to directions is usually enough.
- Lots of plugins and widgets: chat windows, review widgets, weather, pop-ups for newsletters or vouchers.
- Several fonts in many weights, each loaded from a third-party server.
- Tracking and advertising scripts: every service slows the page down and often needs an entry in the cookie banner too. Think about which numbers you really need; more in the guide to website analytics.
How to get it right
- One strong, well-compressed header photo instead of a slider
- A link to Instagram instead of an embedded feed
- One or two fonts, ideally from your own server
- Keep only the plugins guests actually use
- Hosting with servers close to your guests and caching
Better not
- An autoplay video as the home page background
- Uploading photos straight from the camera
- A menu only as a PDF or photo
- A pop-up on the first visit that covers the content
- Scripts from services nobody uses any more
Some slowdowns cannot be switched off in a site builder because they are part of the platform. Then the only options are to keep the page lean or to change systems. The guide What does a restaurant website cost? compares the options and their costs.
How to keep your website fast
A website rarely becomes slow all at once, but step by step: a new full-size photo here, a widget for a long-finished promotion there. So plan a short check twice a year, for example before the summer season and before the Christmas period, when particularly many guests search for party venues and vouchers.
Checklist for a fast hospitality website
- PageSpeed Insights checked for home page, menu and booking, in the mobile view
- LCP up to 2.5 seconds, INP up to 200 milliseconds, CLS up to 0.1
- All photos cropped, compressed and saved as WebP or AVIF
- Images with a fixed size, lazy loading further down the page
- Menu as text, PDF at most as an extra
- No slider and no autoplay video on the home page
- No embedded social media feeds, links instead
- Unused plugins, widgets and tracking scripts removed
- Opening hours, phone number and booking button visible on a phone without scrolling
- Self-test on your own phone on mobile data
At Meine-Gastro-Website, speed is part of the foundation: photos are automatically served in suitable sizes and modern formats, the menu is text on the page, and no unnecessary scripts are loaded. You can see what that could look like for your venue in our example websites or right away in a free preview.
Your fast website as a preview
See for free what your own hospitality website could look like: fast on phones, with a menu as text and a booking button.
A free preview of your venue website, designed by us.
