Is your hotel website slow on mobile? Core Web Vitals explained for hoteliers (2026)

Updated: 9 November 2026

Most of your guests look at your website on a phone, and so does Google: it indexes and ranks the mobile version. Google measures loading experience with three metrics called Core Web Vitals. This is what Google Search Central, web.dev, the PageSpeed Insights and Search Console help pages, and Bing say (sources at the end), explained without jargon.

The three metrics in plain words

Google measures them with real visits and looks at 75% of them (the '75th percentile'), separately for mobile and desktop. The thresholds are the same for both.

LCP (loading): how long the biggest thing on screen takes to appear, almost always the hero photo. Good: 2.5 seconds or less. Poor: more than 4 seconds.
INP (responsiveness): how long the page takes to react when a guest taps a button, opens the calendar or picks dates, across the whole visit. Good: 200 milliseconds or less. Poor: more than 500. It replaced the old FID metric on 12 March 2024.
CLS (stability): how much the content 'jumps' while loading, for example when you go to tap 'Book' and the button moves. Good: 0.1 or less. Poor: more than 0.25.

How much does it count in Google?

Google says Core Web Vitals are used by its ranking systems and recommends good scores. But it also says there is no single page experience signal, that it always tries to show the most relevant content even if the page experience is sub-par, and that good results do not guarantee a top position. In practice: a fast site does not replace good content, but it helps when many pages are equally useful. Above all, a guest who waits or taps the wrong button may leave before booking.

Mobile is the version that counts

Google uses the mobile version of your site, crawled as a smartphone, for indexing and ranking. Make sure the mobile site has the same content as desktop (rooms, facilities, location, policies) and that the main content does not appear only after a tap.

Test your site in 2 minutes

Open PageSpeed Insights (pagespeed.web.dev), paste your home page address and press 'Analyze'. Look at the 'Mobile' tab first.
At the top you see real-user data (from Chrome, last 28 days) and whether your site passes Core Web Vitals: it passes if LCP, INP and CLS are green at the 75th percentile.
Below is the 0-100 score: a lab test that simulates a mid-tier phone on a mobile network. 90 or more is good, 50-89 needs improvement, below 50 is poor. It helps find problems; it is not what Google uses from your real visits.
Repeat for the rooms page and the booking page, which tend to be the heaviest.

What if it says 'no data'?

That is normal for sites with few visits. If a page lacks enough data, PageSpeed Insights uses data for your whole site and, if that is missing too, shows no real-user data; then rely on the lab test. In Search Console, the Core Web Vitals report uses the same real-user data, splits mobile and desktop, groups similar pages and shows 'No data available' when there is not enough. Once you fix something you can start validation there: Google monitors for 28 days.

Usual culprits on hotel websites

Huge photos: the hero image uploaded straight from the camera. It should be the size it is shown at, in a modern format and compressed.
Sliders and hero videos: they delay the first thing guests see. If the first image is lazy-loaded, LCP always gets worse.
Booking engine widget, chat, maps and social feeds: each adds third-party code the phone must process, and they can shift the page if no space is reserved.
Too many fonts: they take time to load and can make text jump.
A cookie banner that pushes the page down when it appears: better to overlay it or reserve its space from the start.
Images without width and height: the page rearranges when they arrive.

What to ask your web provider

That the home and rooms pages pass Core Web Vitals on mobile in PageSpeed Insights, and to show you the result.
Resized, compressed images with width and height set, and the hero photo not lazy-loaded and given high priority.
Reserved space for the booking engine, maps and cookie banner, so nothing jumps.
Fewer scripts: remove the ones you no longer use (old chats or pixels) and load the rest only when needed.
One or two font families at most, and a CDN if your visitors come from several countries.

What about AI?

Google says there are no additional requirements or special optimisations to appear in AI Overviews or AI Mode: the page must be indexed and eligible to show with a snippet, and it recommends the usual fundamentals, including a great page experience. It does not say a faster site appears more in AI, so nobody should promise you that. Bing lists page load time among its main ranking parameters: it usually treats slow loading as a poor user experience.

How iQuota helps

iQuota's official booking page is lightweight and built for mobile, and your website can link to it without loading heavy widgets. It does not fix your own site's speed and nobody can guarantee positions in Google or any AI, but it takes weight off the step that matters most: the booking.

Want an official booking page AI can read and a connector with your real prices, commission-free? The first 30 hotels join free until 30 June 2027.

See the Founding Hotels programme

Frequently asked questions

Do I need 100 in PageSpeed Insights?

No. What matters is passing Core Web Vitals with real users on mobile; the lab score helps find problems.

My site is new and has no data. Am I penalised?

There is no real-user data until there are enough visits. Meanwhile, use the lab test to fix whatever shows in red.

Will a faster site get me into ChatGPT or AI Overviews?

Nobody can claim that. Google says there are no special requirements for its AI features; a fast site is good for your guests and part of SEO fundamentals.

Sources

More guides for hotels

More guides for hotels →

Español · Italiano · Português · Ελληνικά