Hotel websites: what guests look for in the first ten seconds

In the first ten seconds on a hotel website, a guest wants four answers: where it is, what it looks like, what makes it different from the hotel next door, and how to book. If those answers are on the first phone screen, they keep reading. If they have to scroll to find them, they go back to the booking platform they came from.

Why ten seconds

In 2011, Nielsen Norman Group looked at how long people stay on web pages. The finding: the first 10 seconds are critical, because that's when most visitors leave. Pages that get past that point are much more likely to be read for minutes. Their advice is simple: if you want someone's attention, tell them within ten seconds why they should stay.

For a hotel, this matters twice over. The guest has five or six offers open at once and is comparing. Your site is up against the listing on the booking platform, which is clear, fast and always has the booking button in view.

What goes on the first screen

On a phone, the first screen is small. Only a few things fit, so pick the ones that decide:

1. The name and the place, said plainly: the resort town, the area, how far it is to the beach or the center.
2. A real image that shows the hotel or the view, not a stock photo of some pool.
3. The numbers that work for you: number of rooms, distance to the sea, the year you renovated, whatever you do best.
4. The booking button or a short form with arrival and departure dates.

Everything else (rooms, restaurant, gallery, reviews) sits right below, one tap away.

What it looks like in practice

For a seaside hotel, the first screen needs an image guests won't mix up with any other offer on the same beach: the view from an upper floor, the entrance, something only your place has.

The booking form shows up on the first screen, not after three scrolls. The numbers that matter (number of rooms and distance to the beach) sit at the top and get read first. Rooms, pool, restaurant and gallery are one tap away, and check-in, check-out and the address are in one place, so guests don't have to call the front desk to ask. On phones, the buttons are big and within thumb reach, and the images are prepared to load quickly even on beach 4G.

Speed is part of those ten seconds

If the first image shows up after five seconds, half your time is gone. Google measures loading through Core Web Vitals, and for a good score the largest visible element (usually the top photo) should appear within 2.5 seconds. The threshold is judged at 75% of visits, separately for mobile and desktop.

In practice: a compressed top photo sized for the screen, no heavy autoplay video, no newsletter pop-up covering the booking form.

Direct booking and Google

Many guests look the hotel up on Google before they ever visit the site. Google offers hotels free booking links: unpaid links shown in hotel search results that send people straight to the hotel's own booking page, with the rate for the dates they picked. They're set up through Hotel Center, usually by your booking system provider if it's connected to Google.

For this to work, you need a booking page that runs well on a phone. We've written about why direct booking is worth it in our article on direct bookings.

What you tell Google in the code

Beyond the visible text, you can describe the hotel using schema.org with the Hotel type. Useful fields include check-in and check-out times (checkinTime, checkoutTime), number of rooms (numberOfRooms), amenities (amenityFeature) and whether pets are allowed (petsAllowed). It's the same information guests look for on the page, written once for people and once for search engines.

If you'd like to see how your site's first screen looks on an ordinary phone, our services page shows what we do for hotels and guesthouses.