6 frustrations guests have when booking a hotel online
Guests who give up at the booking stage have usually chosen the hotel. Six small frustrations stop them, most of them where one system hands over to the next.
The guests a hotel website loses at the booking stage have mostly said yes already. They liked the photographs, they checked the location, they opened the booking engine. Then something small and irritating got in the way, and the same room was a tap away on an app they already trust.
Six frustrations do most of that damage on hotel websites. A page that jumps as the guest taps it. A consent banner sitting on top of the dates. Dates that vanish on the way to the booking engine. A calendar that will not say what is free. Questions asked before the sale. And silence once the card has been charged.
Most of them happen at a join, where the website hands the guest to the booking engine, or the confirmation is left to a system nobody in marketing looks at. That is why our Website & Development practice starts with the whole booking journey rather than the homepage.
This piece takes the guest's side of the screen; the measurement is in our guide to optimising a hotel website for conversions.
Before the booking engine
The first two happen before the guest has seen a rate. They feel minor to a hotel team that knows the site and uses it on office Wi-Fi.
A page that moves under your thumb
A guest on a train opens the rooms page on a phone. The text appears, then the hero image arrives and pushes everything down, and the "Book" button they were reaching for has become a link to the spa. They tap back and try again.
Speed matters, but a page that will not keep still or answer a tap irritates more. Google measures both. Cumulative Layout Shift scores how much a page jumps while it loads, and since March 2024 Interaction to Next Paint has scored how quickly a page responds when someone taps. Heavy hero video, late-loading fonts and stacks of third-party scripts are the usual causes.
Then there is the size of the target. WCAG 2.2 sets a minimum of 24 by 24 CSS pixels for tap targets, and the tiny arrows on many date pickers fall short of it. If the guest has to tap twice to hit the button, the page is asking them to be careful, and people booking on a phone are rarely in a careful mood.
The 2022 version of this article complained about autoplay video with sound. Chrome and Safari now largely block unmuted autoplay by default, so the modern version is a silent video heavy enough to delay everything else. Run a room page and the first booking step through our free speed audit to see what yours is carrying.
A consent banner in the way
On a phone the cookie banner can cover the availability checker, and some make "Accept" one tap and "Reject" a journey through settings.
The ICO's guidance on cookies and its letters to many of the UK's busiest websites have been clear that rejecting should be as easy as accepting. A banner that nags is also a banner that loses data, because the irritated guest rejects everything.
The fix is a banner that sits low, leaves the dates and the book button visible, and offers both choices with the same weight. Respecting the guest's choice and keeping the booking button in view are the same piece of design.
Inside the booking engine
The frustrations that cost the most bookings happen here, where the hotel often has the least control.
Dates that do not survive
The guest picks two nights in March and two adults on the hotel's homepage, presses search, and lands in the booking engine looking at tonight's date for one adult. They enter it all again. Then they change their mind about the room, press the browser's back button, and the search is gone a second time.
It is still common, because the website and the booking engine are separate systems, and the dates are only carried across if someone set up the link properly. The same is true of the back button, which many booking engines still treat as leaving rather than as a step back.
A guest never sees where your website ends and your booking engine begins. They only notice when something they typed goes missing.
Search from every booking widget on the site, offer pages included, and check the dates, guests and any promotion code arrive intact. Then press back at every step and see what is left.
A calendar that hides the answer
A guest planning a weekend usually has some flexibility. Many hotel calendars ignore it. Every date looks the same until they search, and "no availability" arrives as a dead end with nothing to try next.
The calendars guests find easy share a few habits:
- Availability before the search. Sold-out nights are greyed out, so nobody searches for a weekend that does not exist.
- Nights in plain words. A summary such as "Friday 12 to Sunday 14 March, 2 nights" removes the doubt about whether the last date is a night or a departure.
- A price on the dates. A lowest rate on each day lets a guest move a night rather than leave.
- A next step when it is full. The nearest available dates, or a sister property, instead of an empty page.
That last one needs the website to read live availability, which some booking engines expose and some do not. Find out which yours is before you brief a redesign.
Questions before the sale
Some booking engines make the guest create an account, with a password, before they can pay. Others want a postcode, an arrival time and how they heard about the hotel before the room is secured.
Every question that does not decide the booking can wait. Ask for a name, an email and payment, then gather the rest afterwards in the confirmation or a link to manage the stay. Where an account is worth having, for member rates or a guest portal, a link sent by email (often called a magic link) creates one without a password.
Form fields marked up properly let the phone fill in the guest's name, email and card, and Apple Pay and Google Pay remove the card number entirely. If the price grows on the way to this page, no form design will save it, and our piece on psychology in hotel marketing explains why that is now a legal question as well as a trust one. Treat every field before the payment button as a reason to leave, and keep only the ones you need to take the booking.
After the payment
The last frustration starts once the hotel has the money, which is why it so rarely shows up in conversion reports.
Silence once it is paid
The guest pays, the screen says thank you, and then nothing. The confirmation email takes twenty minutes, lands in spam or reads like a receipt from a car park. They want to add a dog, or move dinner, and the only way is to phone.
Silence like that sends guests looking for reassurance, in their inbox, back on the website or on the phone to reception. The fix is a confirmation that arrives straight away and says what was booked, when payment is taken, how to cancel and how to change something, ideally without a call. What comes next, in the weeks before arrival, is covered in our guide to the upcoming stay email.
It is the clearest join of all. The booking engine sends the confirmation, the CRM sends what follows and the PMS holds the booking, so the guest's first experience after paying depends on three systems agreeing.
Booking your own hotel as a guest
These are easy to miss from the inside. Find them by booking your own hotel on a mid-range phone, on mobile data, away from the office.
- Tap through a room page as it loads. Note anything that moves or needs a second tap.
- Reject the cookies. Check you can still see the dates and the book button, and that rejecting took no longer than accepting.
- Search from every widget. Check the dates and guests arrive in the booking engine, then press back at each step.
- Search a sold-out weekend. See whether the calendar warned you and whether it offered anything else.
- Count the questions. List every field before payment and mark the ones that decide the booking.
- Time the confirmation. Note when it arrives, where it lands and whether you could change the booking from it.
Start with whichever one the booking engine's step-by-step drop-off says costs the most. Five quick conversion wins covers some of the faster fixes for the rest of the site.
The guest who gives up halfway has already done the hard part of choosing you. Losing them to a jumping button or a forgotten date is the most avoidable loss a hotel website has.
Questions hotels ask
Most guests who leave the booking engine have already chosen the hotel. The common reasons are a slow or jumpy page on a phone, dates lost between the website and the booking engine, a calendar that hides availability, forced account creation, long forms, a price that grows at checkout and doubt about what happens after paying.
Not before payment. Ask for a name, an email and payment details, then offer an account afterwards. If an account brings member rates or a guest portal, a passwordless link sent by email creates one without asking the guest to invent a password.
Book a stay yourself on a mid-range phone over mobile data. Reject the cookies, search from every booking widget, press back at each step, try a sold-out weekend and time the confirmation email. Session recordings of real guests then show how often each problem happens.