Someone sees an ad on social media, taps the link, scrolls the page with their thumb and decides whether to call or close the tab. All of it happens on a phone. For most business websites, mobile visitors stopped being the exception long ago; they're the main stream of traffic. So the mobile version of a site isn't a "scaled-down copy." It's the primary screen that leads come from.
Let's look at how responsive website design, a separate mobile site and the mobile-first approach differ, how search engines treat them, and what specifically changes in the interface when someone opens a site on their phone.
Why a mobile-friendly site matters more than you think
The smartphone has become the main device for searching and shopping: people look up services on the go, compare prices, and arrive from messaging apps and social media ads. This is especially noticeable in retail, consumer services and anything promoted through targeted advertising. In B2B, desktop's share is usually higher, but even there the first encounter with a site often happens on a phone.
Rather than relying on market-wide figures, look at your own. In Google Analytics, the device category report shows what share of visitors come from smartphones, and comparing conversion rates by device shows where leads are being lost. If lots of people arrive on mobile but leads mostly come from desktop, the problem is almost certainly the mobile version.
Responsive, separate mobile site or mobile first
These three terms are often lumped together, even though they belong to different categories. Responsive design and a separate mobile site are technical ways to build a site for phones. Mobile first is a way of thinking about design, and it can be combined with responsive.
| Responsive | Separate site (m.) | Mobile first | |
|---|---|---|---|
| What it is | One site that rearranges itself to fit the screen width | A second site on a subdomain for phones | An approach: design for the phone first |
| Page URLs | One for all devices | Two: main and m. | No effect |
| Maintenance | One codebase and one set of content | Two templates, content must be kept in sync | Adds no work, changes the order |
| SEO | The simplest option | Needs annotations between versions and redirects | Helps: the mobile version is complete |
| When it fits | Almost always | Rarely, for a distinct mobile use case | When most traffic comes from phones |
Responsive design
A responsive site is a single page with a single URL whose layout changes depending on screen width: columns stack into one, the menu collapses into a button, images load at the right size. Google explicitly recommends this option as the easiest to maintain, and it has become the standard for corporate websites, landing pages and online stores.
A separate mobile site
A separate mobile site lives on a subdomain like m.example.com, and the server sends phone users there. Large portals used to do this because rebuilding an old site cost more than creating a second one. Today the approach has more downsides: two templates, the risk that the mobile version ends up with less text and fewer products, and extra configuration so search engines understand which page corresponds to which.
Mobile first as a design approach
Mobile first means the designer starts with the narrowest screen. A phone has no room for anything secondary, so you have to decide right away what people need first and in what order. Then the layout is expanded for tablet and desktop, adding what fits there. Going the other way, squeezing a desktop layout down to a phone, usually produces a long stream of blocks nobody on a small screen will scroll through.
Mobile first isn't about screen width. It's about the order of decisions: the essentials first, everything else after.
Mobile-first indexing: how search engines see your mobile site
Google has switched to mobile-first indexing: it evaluates and ranks pages based on what its mobile crawler sees. If the mobile version has trimmed text, or is missing some products, reviews or structured data, then for search purposes they effectively don't exist. That's one more argument against a separate "lite" version.
Page experience on smartphones also feeds into how Google treats a site, and Google Search Console reports Core Web Vitals separately for mobile. In practice, the requirements all point the same way: the phone should show the same content as the desktop, the page should load quickly, text should be readable without zooming, and nothing should overflow the edge of the screen.
What changes in design on a phone
Responsive web design is more than rearranging columns. Every type of block needs its own solution on a small screen, and that's exactly where careful responsive work differs from a box-ticking one.
- Navigation. The menu collapses behind a button, but the most important sections, search and contacts are better kept visible. A header that sticks on scroll should be short, or it will eat up a third of the screen.
- Forms. A minimum of fields, large inputs, the right keyboard: numeric for phone numbers, with "@" for email. If the font in an input is smaller than 16 pixels, the iPhone zooms the page on focus and the form shifts out of view.
- Tables. A wide table of prices or specs can't simply be shrunk. It's turned into cards, kept with horizontal scrolling and a pinned first column, or trimmed to the key columns only.
- Catalogs and filters. Filters move into a separate panel that opens with a button, while results stay visible right away. A product card in a list shows the photo, price and button; everything else is inside.
- Call and messaging buttons. On a phone, the number should be a link that starts a call immediately, and messaging buttons should open the right chat. For many services, this is the main way customers get in touch.
- Touch targets. A finger isn't a cursor. Buttons and links need to be large enough and not crammed together: Apple and Google guidelines put the benchmark at roughly 44 to 48 pixels. Hover effects don't work on phones, so nothing important should hide in them.
- Speed and image weight. Phones often run on mobile data. Images are served at the right size and in modern formats, the first screen loads first, and heavy background videos are better replaced with a static image on mobile.
It's also worth making sure the main action on a phone is available at any moment. A Call or Request a Quote button pinned to the bottom of the screen, in the thumb zone, often works better than a form at the very end of the page.
Breakpoints and mockups: what to design and what to agree on
A breakpoint is the screen width at which the layout rearranges: the number of columns, font sizes and menu style change. There's no universal set, but phone, tablet and desktop are the most common, with a maximum content width for wide monitors. Tying breakpoints to specific device models isn't a good idea: there are too many of them, and it's better to place breakpoints where the design itself starts to break.
For the client, it's important to agree on the set of mockups in advance:
- key pages, such as the homepage, catalog, product page, service page and contacts, are designed in at least mobile and desktop versions;
- complex pages with tables and filters get a tablet version too, since tablet layouts are often the weakest spot;
- standard blocks are described as components with rules for behavior at different widths rather than redrawn for every screen;
- states that only exist on phones, like an open menu, a filter panel or a pinned button, also belong in the mockups.
The mobile flow is easiest to test before design, on a prototype: block order on a phone is a decision about priorities, and it's cheaper to change in a wireframe than in finished code.
Checklist: how to test a mobile site before launch
Before launch, go through the mobile version by hand on several real phones, iPhone and Android, with narrow and wide screens. A browser emulator is useful but no substitute for an actual device.
- there's no horizontal page scrolling at any width, and nothing overflows the edge;
- text is readable without zooming, and paragraphs have a comfortable line length and line spacing;
- the menu opens and closes, and the main sections are reachable from anywhere;
- the phone number is tappable, and messaging buttons open the right chat;
- forms can be filled in without the page zooming, the right keyboard appears, and errors show next to the field;
- buttons and links are easy to tap with a finger, and neighboring elements don't overlap;
- tables, filters and galleries work on both phone and tablet;
- pop-ups and cookie banners don't cover content and are easy to dismiss;
- the mobile version has the same text, products and data as desktop;
- the page passes PageSpeed Insights and Lighthouse checks for mobile;
- conversion events in Google Analytics fire on mobile too: calls, form submissions, clicks to messaging apps.
Common mobile website mistakes
Most mobile problems don't come from complexity. They come from remembering the phone at the end of the project, after the desktop version has already been approved.
- Responsive "by default." The designer only draws desktop, and the developer decides how everything will fit on a phone. The result is a random block order, with important buttons ending up at the bottom.
- Full-screen pop-ups. A newsletter or discount pop-up that appears immediately and is hard to close simply drives people off the page on a phone.
- A heavy first screen. A large video, a slider and several fonts make loading slow, especially on mobile data.
- Small, cramped elements. Footer links and social media icons sit so close together that hitting the right one is hard.
- No testing on real devices. The site looks fine in an emulator, but on a particular phone the header breaks or the form doesn't work.
When a site is built from scratch, all of these questions are settled at the structure and prototype stage, not after launch. That's how we work as a web development agency: research and user flows first, mobile ones included, then design and responsive build. You can see examples of our custom website development on our work page.
FAQ
Which is better for a business: a responsive site or a separate mobile version?
For most business websites, responsive. One URL and one codebase are easier to maintain, search engines have no doubt about which page to index, and content doesn't drift apart between phone and desktop. A separate mobile version is rarely justified: only when the mobile use case is fundamentally different and there's a dedicated team behind it.
How is mobile first different from responsive design?
Responsive design is a technical solution: one site that rearranges itself to fit the screen width. Mobile first is a design approach: you first decide what people need on a phone and in what order, then expand the layout for tablet and desktop. They usually work together: you design from the mobile screen up and build responsively.
How many mockups does a responsive site need?
As a rule, key pages are designed in at least two versions, phone and desktop, with a tablet version added for complex pages. In-between widths are described by rules: how the grid, columns and images behave between breakpoints. Standard blocks don't need separate mockups if they're built from components with documented behavior.
How do you find out how many visitors come to your site on mobile?
In Google Analytics, open the Tech report, look at device category and check the share of smartphones, tablets and desktops. It also helps to compare lead conversion by device: if lots of people come on mobile but few of them submit a lead, the mobile version is most likely getting in the way.
Can you make an existing website responsive?
Yes, but the result depends on the code. If the site is built with a fixed width on tables, going responsive means rebuilding the templates, and sometimes it makes sense to combine it with a redesign. If the front end is modern, reworking the grid, navigation, forms and tables is often enough.




