How to make a mobile hotel website that works Built for a thumb, a small screen and weak signal.
For most hotels, a large share of visits comes from phones; check your own analytics to see yours. A guest on a phone has a small screen, one thumb and sometimes a weak signal. This guide explains what a mobile friendly hotel website needs, part by part, and how to test each part on your own phone in a few minutes.
free, by email, no calls, no obligationResponsive vs mobile-first, in plain words
A responsive hotel website is one site that changes its layout to fit the screen. On a laptop the rooms may sit in three columns; on a phone they stack in one. There is no separate mobile site and no separate address. This is the normal way to build a website today.
Being responsive only means the page fits. It does not mean the page is good on a phone. Many hotel sites were designed on a big screen and then squeezed down. The result fits, but the booking button ends up under a slideshow, the menu has twelve items, and the text is grey on a photo.
Mobile-first is a way of working, not a technology. You design the phone version first, with only what a guest on a phone needs, then add space for larger screens. It forces hard choices early: what goes on the first screen, how many menu items you need, which photos earn their weight. In our judgement, this is the right starting point for a small hotel, because the phone is where the decision is usually made.
Related: if your own site is slow on a phone or hard to book on, see signs your hotel website is outdated. We design hotel website design for independent hotels.
The first screen, sticky buttons and what covers them
Our page on your hotel website's first impression covers what the first screen should say. Here we look at the mechanics that make it work on a phone.
- A sticky Book buttonKeep one Book button fixed at the bottom of the screen as the guest scrolls. The bottom is easier to reach with a thumb than the top. It should open dates and prices directly.
- Call or message next to itMany guests want to ask one question before they book. A small bar with Book, Call and WhatsApp covers both kinds of guest. Keep it to two or three buttons so each is big enough to tap.
- A bar that stays out of the wayThe bar should be slim and should not cover form fields or the booking engine. Check that it hides or moves when the phone keyboard opens.
- Pop-ups on arrivalA newsletter or discount pop-up that fills the screen before the guest has seen a photo is the fastest way to lose them, and Google's guidance warns against intrusive pop-ups on mobile. Show a direct-booking perk inside the page instead.
- Cookie bannersWhere you need one, make it a compact bar at the bottom with Accept and Reject buttons of the same size. Check the rules that apply in your country with whoever handles your privacy policy.
- Chat widgetsA floating chat bubble often sits on top of the Book button. Move it so it does not overlap, or drop it and rely on the WhatsApp button.
Thumb-friendly menus, readable text and contrast
- Short menuFive to seven items is plenty: Rooms, Dining, Experiences, Location, Contact, with Book outside the menu. Long menus with sub-menus are hard to use with a thumb.
- Big tap targetsApple's and Google's design guides suggest roughly 44 to 48 points for a touch target, and WCAG 2.2 sets 24 by 24 CSS pixels as the minimum. Rows of tiny footer links are where most mis-taps happen.
- Text at a real reading sizeBody text around 16 pixels or larger reads comfortably on most phones without zooming. Keep paragraphs short. Never block zoom; some guests need it.
- Enough contrastLight grey on white, or white over a busy photo, is hard to read in sunlight. WCAG asks for a contrast ratio of at least 4.5 to 1 for normal text, and free contrast checkers will test your colors. Our page on hotel website accessibility covers the rest.
- Text as textDo not put room names, prices or offers inside images. On a phone they become tiny, and they cannot be translated, read aloud or tapped.
Image weight and speed on mobile data
Photos sell a boutique hotel, and photos are also what make most hotel sites slow. A guest at an airport or on a mountain road does not have office Wi-Fi. A home page with a full-screen video, a ten-image slider and uncompressed photos can show a blank screen for a long time on that connection.
The fixes are known. Serve each photo at the size the screen needs, so a phone gets a smaller file than a large monitor. Use modern formats such as WebP or AVIF. Load photos further down only when the guest scrolls near them. Replace an auto-playing video on the first screen with one strong photo. Our hotel website photos guide covers sizes and formats.
How to test. First the real test: turn off Wi-Fi on your phone and open your site on mobile data, ideally where the signal is not perfect. Count the seconds until you see the first photo and the Book button. Then use PageSpeed Insights, Google's free tool, and look at the Mobile tab. It shows lab data from Lighthouse, which simulates a mid-range phone on a mobile network, and, if your site has enough visitors, field data from real Chrome users over the last 28 days. The field data is closer to what guests experience.
Do not chase a perfect score. What matters is that the first screen appears quickly and the page does not jump while it loads, which is what Google's Core Web Vitals measure. Google retired its old Mobile-Friendly Test in December 2023, so guides that send you there are out of date; it points to Lighthouse in Chrome instead.
Galleries, maps, directions and one-tap contact
- Galleries that swipeGuests expect to swipe through photos and pinch to zoom. Small arrow buttons are hard to hit. Show a photo count, such as 3 of 12, and an easy way to close.
- Maps that do not trap the scrollA full-width embedded map can catch the guest's finger and scroll the map instead of the page. Use a small static map with a clear button that opens directions in the guest's own map app.
- Directions in plain wordsUnder the map, write how to arrive: from the airport, where to park, the last turn GPS often gets wrong. Check that your Google pin is in the right place, because many guests navigate from there.
- Click-to-callWrite the phone number as a tap-to-call link with the country code, so one tap starts the call.
- WhatsApp and emailA WhatsApp link opens a chat with your number filled in, and an email link opens the guest's mail app. Only offer the channels you will answer quickly.
Forms, date pickers and the booking engine's mobile flow
This is where a mobile hotel website most often fails, and it is the part owners test least. The home page may look fine, but the booking engine is usually a separate product with its own mobile problems.
Date pickers. A good mobile date picker shows a full month, lets the guest tap check-in and check-out in one view, and shows the number of nights. Bad ones are tiny calendars with small arrows, or two fields that each open their own calendar. If the guest picks dates on your site and then again in the booking engine, that is a step you can remove.
Forms. Ask only for what you need. Each field should be large, labelled above the box, and bring up the right keyboard: numbers for the phone, an email keyboard for email. Allow autofill. On iPhones, fields with text smaller than 16 pixels make the page zoom in when tapped, which feels broken; a slightly larger font fixes it.
The booking engine. Walk through a full booking on your phone, up to the payment screen. Check that it keeps your hotel's name, colors and logo, that the total with taxes and fees is clear before the card details, and that Apple Pay or Google Pay appear if your engine supports them. Our page on booking engines on hotel websites explains how the site and the engine share the work.
A guest who gives up halfway may book the same room on an OTA, and that booking carries commission. Our OTA commission calculator shows what that adds up to.
Testing on iPhone and Android
Desktop browsers have a phone view, and it is useful for a quick look. But it does not show how far the thumb reaches, how the keyboard covers a form or how the page behaves on weak signal. Always finish on real phones.
Test on at least one iPhone with Safari and one Android phone with Chrome. They handle fonts, date pickers, payment buttons and pop-ups differently, and a problem on one is often invisible on the other. An older, cheaper phone is a better test than the newest one, because many guests do not have the newest one.
Then ask someone who has never used your site to find a room and go as far as payment while you watch without helping. Note every place they hesitate. For a fuller review beyond mobile, use our hotel website checklist.
Mobile check: how to test on your phone and how to fix it
Run through this with your phone on mobile data, Wi-Fi off, opening the site from a Google search as a guest would.
| Check | How to test on your phone | Fix |
|---|---|---|
| Book button in reach | Scroll to the middle of a long page. Can you tap Book with your thumb? Does it open dates? | Slim sticky bar at the bottom; link Book straight to the date step |
| Nothing covers the first screen | Open the site in a private tab. Is the first photo hidden by a pop-up, banner or chat bubble? | Remove arrival pop-ups, shrink the cookie banner, move the chat bubble |
| Menu works with a thumb | Open the menu with one hand. Can you tap each item cleanly? | Cut to five to seven items, add space between them |
| Text is readable | Read a room description outdoors in daylight without zooming | Larger body text, darker text color, no text over busy photos |
| Fast on mobile data | Count the seconds until the first photo and Book button appear; then run PageSpeed Insights, Mobile tab | Resize and compress photos, use WebP or AVIF, remove video from the first screen |
| Gallery and map | Swipe a room gallery, then scroll past the map with one finger | Touch gallery with a photo count; static map with a Directions button |
| Phone and WhatsApp work | Tap the phone number and the WhatsApp button | Use tap-to-call and WhatsApp links with the full country code |
| Forms are easy | Fill the contact form. Does the right keyboard appear? Does the page zoom in on iPhone? | Fewer fields, labels above boxes, 16px text in fields, correct field types |
| Booking engine finishes | Book a room up to the payment screen on iPhone and on Android | Ask your booking engine provider to fix mobile issues or match your branding |
If many of these fail, small fixes may not be enough. Our page on hotel website design mistakes covers the wider problems that usually sit behind them.

I'm Gonzalo. I ran hotels for more than five years, from small properties to remote lodges, and now I build websites for them. Can I help with your hotel or your website? Write to me at gonzalo@hotelcrafted.com. I answer myself, usually within one business day.
Four steps, from dated to done.
- Step 01
Review
Send us your website. We reply by email with what we'd change and a fixed price.
- Step 02
Design
A new look shaped around your property and its story. You approve it before we build.
- Step 03
Build
Fast, clean and connected to your booking engine. Simple for your team to update.
- Step 04
Care
We launch it with you, then stay close to keep it fresh.
Questions hoteliers ask us.
What is a mobile friendly hotel website?+
It is a hotel website that is easy to use on a phone, not just one that fits the screen. Guests can read without zooming, tap buttons with a thumb, see photos quickly on mobile data and book without the page breaking, including in the booking engine.
What is the difference between a responsive and a mobile-first hotel website?+
Responsive means one site that changes its layout to fit any screen. Mobile-first means the phone version was designed first and the larger screens came after. Most good sites today are both: responsive in how they are built and mobile-first in how they were planned.
How do I check if my hotel website is mobile friendly?+
Open it on your own phone with Wi-Fi off and try to book a room. Then run PageSpeed Insights, Google's free tool, and look at the Mobile results. Test on an iPhone and an Android phone, because they show different problems.
Do I need a separate mobile version of my hotel website?+
No. A separate mobile site with its own address is an old approach that is harder to maintain. One responsive site designed with phones in mind is the standard today.
Why is my hotel website slow on phones?+
Usually large photos, auto-playing video, image sliders and too many third-party scripts such as chat widgets and tracking tags. Resizing and compressing photos and removing what guests do not need usually helps the most.
Does mobile friendliness affect my hotel's Google ranking?+
Google indexes the mobile version of websites, so what a phone sees is what Google judges. Page experience is one of many factors. A good mobile site will not guarantee a high ranking, but a poor one makes everything harder.
More on hotel websites.
Not sure how your site works on a phone? Send it for a free review, by email.
You'll get a short list by email within one business day. No calls, no pressure.
Thank you. We got it.
You'll have our review in your inbox within one business day.
Prefer email? Send your website link to gonzalo@hotelcrafted.com and I'll reply with 3 things I would change. I answer myself, within one business day. No calls, no newsletter.