Responsive or mobile-first? What a hotel website needs now
Every hotel website is responsive now. The useful question is what the phone version puts first, and whether the booking flow was designed for a phone at all.
A guest finds your hotel on their phone at lunchtime, from an Instagram post a friend shared. They look at two rooms and close the tab. That evening they open the laptop, search your name and book. One guest, two screens, and your website had to work on both.
A responsive website is one site whose layout adapts to the screen it is shown on. A mobile-first website is a responsive site designed from the phone screen upwards, with the larger layouts added afterwards. In 2026 every hotel website worth keeping is responsive, so the label matters less than two questions: what the phone version puts first, and whether the booking flow was designed for a phone or squeezed onto one.
That is the conversation our Website & Development practice has at the start of every rebuild, and it usually ends somewhere more useful than "mobile-first".
Responsive and mobile-first, defined
When this blog first wrote about responsive design in 2012, the alternatives were a separate mobile site on an "m." subdomain, or an app. One responsive site meant one set of content, one set of URLs for search engines, and a booking form a guest could use without pinching and zooming. That argument won. Nobody briefs an m-dot site for a hotel now.
Mobile-first came later, as a design method rather than a technology. The designer starts with the smallest screen, decides what has to be there, and adds to it as the screen grows. Done well, it forces the priorities. Done badly, the desktop looks like a stretched phone.
Google settled the search side. Since 5 July 2024 it has crawled and indexed every site with its smartphone crawler, as its mobile-first indexing documentation explains, so the phone version is the one Google judges. It also retired the Mobile-Friendly Test and the Mobile Usability report in December 2023. There is no longer a badge to pass. There is only whether the site works.
Why the label misleads
The case for mobile-first rests on traffic, and the traffic is real. On most of the hotel sites we see, the majority of sessions now come from phones, especially from social and paid campaigns.
Bookings are a different story. In the projects we work on, discovery happens mostly on phones, but a large share of the booking itself still completes on a larger screen, often close to half. Guests browse on the commute and pay at a desk, with the card to hand.
So I do not think the choice between mobile-first and desktop-first is a real one. The phone version should be a prioritised edit of the same website, not a different website, and the desktop version has to stay good enough to take the booking. A site built only for the phone wins the browsing and can still lose the revenue.
Responsive decides how a page fits the screen. Mobile-first decides what the guest sees first. Neither decides whether they can book.
Pages that respond, flows that don't
The useful split is between the pages a guest reads and the steps a guest completes.
Content pages should simply respond
Rooms, dining, spa, the local guide. These pages carry the same content on every device, reordered. On a phone the room's photograph, its price from and the button to check availability come first; the floor plan and the long description can follow further down.
Prioritise, but do not delete. Anything removed from the phone version is removed from what Google indexes, and the guest who wanted the detail goes looking for it on an OTA. Folding content into an accordion is fine.
The booking flow deserves its own design
Booking is where responsive stops being enough. A flow designed on a desktop and reflowed for a phone keeps the desktop's ideas, such as a two-month calendar, six rate plans side by side or a map to pick from, and each becomes fiddly on a small screen.
When we build a booking flow, we often load a different version on a phone from the one on a desktop, working from the same rates and the same booking logic underneath. Strictly, that is not responsive design, and it does not need to be. A map that suits a large screen becomes a short list on a phone. A rate comparison becomes one room at a time, with the differences spelt out. A date range picker can become a month first, then the nights. The details of a calendar that guests find easy are in our piece on booking frustrations.
Whether you can do this depends on who owns the flow. A third-party booking engine shows its own mobile layout. Our piece on the future of hotel booking engines covers what to ask of one, including how it handles payment on a phone.
What the phone version gets first
A phone screen has room for very little, so everything at the top of the page competes with the photograph that sells the room.
The header's space budget
On a phone the header should shrink to what a guest needs on every page: the logo, a way to book, a way to call and the menu. Keep it slim and fixed, so the book and call buttons stay within reach as the guest scrolls, and let it collapse further rather than take a quarter of the screen. A Christmas menu banner on top of a cookie notice on top of a tall header leaves the guest a letterbox to look at the hotel through. What goes inside the menu itself is covered in our piece on hotel website navigation.
Speed you feel when you tap
The delay a guest notices most on a phone is the one after a tap, and Google's Core Web Vitals now measure it. Interaction to Next Paint replaced First Input Delay in March 2024, and Google's guidance on INP treats 200 milliseconds or less as good. A date picker that takes a second to respond on a phone, because a dozen tracking and chat scripts are loading behind it, fails that test and the guest's patience at once.
Run the homepage and a room page through our free speed audit on the mobile setting first. Then decide what the phone version leads with:
- The room, not the hotel's history. The photograph, the price from and the availability button above the fold.
- Still images over video. A hero video costs the most on the device least able to afford it.
- Images sized for the screen. A phone should never download the desktop photograph and shrink it.
- Fewer scripts. Every chat widget, review badge and tag delays the first tap.
Carrying the guest between devices
Most hotel websites treat the guest who browsed on a phone and the guest who booked on a laptop as two strangers.
The cheapest fix is a booking link that carries the stay. If the dates, guests and room sit in the URL, a guest can send it to themselves or a partner and pick up exactly where they left off. An "email me this stay" button does the same, and with a marketing opt-in beside it, gives the hotel a way to follow up.
A guest account goes further, because a signed-in guest is the same guest on every device, as long as the account offers something worth signing in for, such as a member rate.
Measurement has the same gap. In GA4 a guest who browses on a phone and books on a laptop usually looks like two users unless they sign in, so the phone gets little credit for bookings it helped start. Read device figures by stage, not as one conversion rate. The wider picture of what to measure is in our guide to optimising a hotel website for conversions.
Checking your own site
- Split the journey by device. In GA4, compare sessions, booking engine starts and purchases by device category. Where the phone's share falls most between two stages is where the phone flow needs work.
- Read the first screen. Open your five most visited landing pages on a phone. If what fills the screen before scrolling is not the hotel and a way to book, rearrange it.
- See what Google sees. Run the same pages through Search Console's URL Inspection tool, which renders them as Google's smartphone crawler does.
- Check the booking engine on its own. Ask whether it can run a different flow on a phone, and what you can change in it.
- Then check the desktop. Book a stay on a laptop too, and make sure the larger screen has not been left looking empty.
The 2012 version of this article told hotels to ask for a responsive website. That request has been granted everywhere. The one worth making now is a booking flow that someone designed with a phone in their hand, and a desktop one that still takes the money.
Questions hotels ask
A responsive website is one site whose layout adapts to the size of the screen. Mobile-first is a way of designing a responsive site, starting with the phone layout and adding to it for larger screens. Every mobile-first site is responsive, but not every responsive site was designed from the phone up.
It needs to work properly on a phone, because that is where most browsing happens and the version Google indexes. It does not need to treat the desktop as an afterthought, because many guests still complete the booking on a larger screen. The best approach is a prioritised phone version of the same site, with a booking flow designed for each device.
Yes. Since July 2024 Google has crawled and indexed every site with its smartphone crawler, so the phone version is the one it judges. Content that appears only on the desktop version is not seen by Google.
Not for booking rooms. A separate mobile site splits your content and your search visibility, and most guests will not install an app to book a stay. One responsive site, with a booking flow that adapts properly to the phone, does the job of both.