How fast should a hotel website be?
Short answer
A hotel website should meet Google's Core Web Vitals "good" thresholds for most visitors: Largest Contentful Paint (LCP) within 2.5 seconds, Interaction to Next Paint (INP) of 200 milliseconds or less, and Cumulative Layout Shift (CLS) of 0.1 or less, measured at the 75th percentile of page loads on mobile and desktop. In practice, mobile matters most. For hotels, the biggest problems are usually oversized hero images and galleries, heavy third-party scripts, and booking widgets that shift the layout as they load.
By Lodging Engine Editorial Team· Reviewed by Eric Zwanenburg· Last reviewed
The three Core Web Vitals
| Metric | Measures | "Good" target |
|---|---|---|
| LCP — Largest Contentful Paint | How quickly the main content (often the hero image) appears | ≤ 2.5 s |
| INP — Interaction to Next Paint | How quickly the page responds to taps and clicks | ≤ 200 ms |
| CLS — Cumulative Layout Shift | How much the layout jumps while loading | ≤ 0.1 |
Targets come from web.dev and apply at the 75th percentile of real page loads.
Lab data vs real-user data
- Real-user (field) data reflects your actual visitors' devices and connections. It's what the thresholds are based on.
- Lab data comes from a simulated test. Useful for diagnosing problems, but it can differ from what guests experience.
Small hotel sites may not have enough traffic for field data in public datasets; then lab tests are your main guide.
Common causes on hotel sites
Slow LCP
- Huge hero images or videos.
- Images served without modern formats or appropriate sizes.
- Slow hosting or no caching.
Poor INP
- Heavy chat widgets, review widgets, and tracking scripts.
- Complex sliders and animations.
High CLS
- Booking bars or cookie banners that push content down after loading.
- Images without defined dimensions.
- Late-loading fonts that reflow text.
Practical fixes
- Resize and compress images; serve modern formats; lazy-load gallery images below the fold.
- Preload the main hero image and keep it a sensible size.
- Audit third-party scripts — remove what you don't use, delay what isn't essential.
- Reserve space for booking widgets and banners so they don't shift content.
- Use good hosting with caching and a CDN.
Common mistakes
- Optimizing desktop only.
- Autoplaying background videos on mobile.
- Adding widgets without checking their performance cost.
- Judging speed from a single test run.
Checklist
- LCP, INP, CLS measured on mobile
- Hero image optimized and preloaded
- Gallery images lazy-loaded
- Third-party scripts audited
- Space reserved for booking bars and banners
- Caching and CDN in place
Sources
- Web Vitals — web.dev (Google)