How a responsive website works
A responsive website has one set of code and one set of content. The browser checks the screen width and the layout changes accordingly: three columns on desktop become one column on a phone, the menu folds into a button, and images shrink to the screen width. The points at which the layout changes are called breakpoints.
For this to work, the head of every page needs a viewport tag, which tells the mobile browser to display the page at the device width rather than as a shrunken desktop screen. Without it, a site looks like a small picture of itself on a phone, and visitors have to pinch to zoom.
Responsive site, separate mobile site or app
| Responsive site | Separate mobile site | App | |
|---|---|---|---|
| Address | Same URL on every device | A separate address, for example a mobile subdomain | Downloaded from an app store |
| Content | Same content | Two versions that must be kept identical | Content separate from the website |
| Maintenance | Update once | Update twice | Separate development and updates for Android and iOS |
| The setup Google recommends | Supported, but needs extra configuration so Google can link the versions | Does not replace a website in search results | |
| When it fits | Almost any business | Mainly older sites already built this way | When returning customers use the service again and again, for example bookings or a loyalty club |
Why it matters: Google ranks by mobile
Google uses the mobile version of a site, crawled with its smartphone crawler, to index and rank pages. In October 2023 Google announced that the move to this approach, called mobile-first indexing, was complete, and since 5 July 2024 even the few sites still crawled with the desktop crawler are crawled with the smartphone crawler. According to Google, a site whose content is not accessible at all from a mobile device will no longer be indexed, and content that exists only on the desktop version may not count.
According to Google Search Central guidance, Google recommends responsive design because it is the easiest to set up and maintain. Titles, descriptions, structured data and image alt text should also be the same on mobile and desktop. You may fold content into tabs or accordions on mobile, but primary content should not load only after the visitor taps something.
Google's Mobile-Friendly Test and the Mobile Usability report in Search Console were retired in December 2023. Today you test with Lighthouse, PageSpeed Insights and by hand.
What to check on a phone
Text size
Body text should be readable without zooming. The default size in browsers is 16 pixels, which is a good starting point for body text.
Buttons and links
According to web.dev, a tap target should be about 48 by 48 pixels, roughly 9 millimetres, with about 8 pixels between neighbouring targets. Crowded links in the footer are the usual problem.
Menu
Opens and closes with a tap, shows every link, and scrolls when it is long. Check that it does not cover the contact button.
Forms
The phone field opens a number keypad, the email field opens a keyboard with @, autofill works, and error messages appear next to the field and not hidden behind the keyboard.
Click-to-call and WhatsApp
The phone number is a tel: link that opens the dialler. The WhatsApp button opens a chat with the number in international format: 972 followed by the number without the leading zero. Test both on a real phone.
Images and tables
Images do not overflow the screen and are not too heavy. A wide table scrolls within itself or turns into cards, rather than pushing the whole page sideways.
RTL problems that show up in Hebrew on mobile
A theme designed for English and adapted to Hebrew after the fact sometimes looks fine on desktop and breaks on a phone. Common problems:
- Sideways scrolling: an element sticking out past the left edge of the screen makes the whole page slide left and right as you scroll.
- Mixed text: a phone number, price, email address or English brand name inside a Hebrew sentence flips or jumps to the end of the line.
- English fields: email and phone fields should run left to right even in a Hebrew form.
- Arrows and sliders: the "next" arrow should point left, and a slider should move in the reading direction.
- Fonts: a font without Hebrew letters is replaced by the device font, and the design differs between Android and iPhone.
How to test: Chrome DevTools and a real phone
- 01
Device mode in Chrome
Open developer tools (F12, or Cmd+Option+I on a Mac) and click Toggle device toolbar. Pick a device or drag the width slowly, looking for the point where something breaks.
- 02
Network and CPU throttling
In the throttling list choose Mid-tier mobile or Low-end mobile, and see how the page loads on an average phone rather than a powerful computer.
- 03
A real phone
According to the Chrome documentation, device mode is only an approximation. Test on at least one Android phone and one iPhone: scrolling, menu, form, call and WhatsApp.
- 04
Measure
Run PageSpeed Insights on the main pages, and check the mobile Core Web Vitals report in Search Console.
Core Web Vitals on mobile
Core Web Vitals are three metrics Google collects from real users: how fast the largest element loads (LCP), how quickly the page responds to a tap (INP) and how stable the page is while loading (CLS). According to web.dev, they are assessed separately for mobile and desktop, at the 75th percentile of page loads.
A responsive site is not necessarily fast on mobile. It can still show a huge background image, a slider and a pop-up on a phone, and load slowly. For how to measure and what to fix, see website speed optimisation.
Building a responsive website: what to ask for
When you order a business website or a landing page, ask to see the mobile design before the desktop design, not just a promise that "it will work on mobile too". Ask for testing on real phones before launch, and try the form and the WhatsApp button yourselves. If you are still deciding on a platform, see the guide how to choose a content management system: almost any system can be responsive, and the difference lies in the theme and how the site is built.