On this page · 14 sections
- How much of your traffic is actually on phones?
- Why do our mobile visitors convert so much worse than desktop visitors?
- Why does Google care which version is better?
- What is the difference between responsive and mobile-first?
- What should a buyer see on the first phone screen?
- How do you make your key pages readable on a phone?
- How do you make it easy to get in touch from a phone?
- Do LinkedIn and other in-app browsers break forms and booking links?
- Should a B2B website have a sticky call button on mobile?
- How fast does it need to be on a phone?
- How do you test your website on a phone properly?
- What to do this month
- Questions founders ask
- Sources
Most B2B websites are signed off in a meeting room. The agency plugs a laptop into the big screen, the partners look at the homepage, and everyone agrees it looks the part. Almost nobody in that room picks up their phone and tries to find the contact number with one thumb.
Your buyers do. A finance director hears your name from a colleague at lunch and looks you up on the walk back to the office. An operations manager asks ChatGPT for three firms who could take on a contract and taps through to each site from the train. A managing director taps a link in a LinkedIn post on Sunday evening, before a Monday meeting. The first time many buyers see your website, they see it on a screen the size of a playing card.
Phones are no longer the minority channel. StatCounter's figures for August 2026 show phones accounted for 46.11% of web page views in the UK, against 49.17% for desktops and 4.72% for tablets. That covers all websites rather than B2B alone, but it means the phone version of your site is not a side issue.
If that first look is a cropped photograph, a menu with ten items and a form that needs twelve fields, buyers go back to the list and try the next name. Nothing in your reports tells you it happened. That is the real case for designing for the phone first: the enquiries that quietly never arrive.
How much of your traffic is actually on phones?
Across all UK websites, close to half. StatCounter recorded phones at 46.11% of UK page views in August 2026. We could not find a reliable published figure for B2B sites alone, so your own analytics are the number that matters, and they take five minutes to check.
In Google Analytics, look at the device category report, then break it down by landing page and by traffic source. Three patterns are common in B2B firms. The homepage and about page get a large share of phone visits, because that is where people check you out. Articles shared on LinkedIn tend to be read on phones. Pages such as pricing, detailed service descriptions and case studies see more desktop visits, because that is where a buyer who is already interested does their homework.
That split matters. The phone is where people decide whether you are worth a proper look, and the desktop is where they take it. Lose them on the phone and the desktop visit never happens.
Why do our mobile visitors convert so much worse than desktop visitors?
Partly because phone visitors are earlier in their research, and partly because the phone version is often harder to use. A buyer checking you on a train may come back on a laptop to enquire, which makes the phone visit look wasted when it did its job.
But a large gap can also mean the phone route is broken: a form that will not submit, a booking link that fails inside the LinkedIn app, a pop-up covering the button or a page too slow to load on 4G. Tracking adds noise too, because some phone visits are recorded as Direct or lost altogether. The only way to know which is happening is to try the route yourself on a phone, which is what the rest of this guide is about.
Why does Google care which version is better?
Because Google now treats the mobile version of your pages as the main version. Its mobile-first indexing guidance says it "uses the mobile version of a site's content, crawled with the smartphone agent, for indexing and ranking". If content is missing, cut down or hard to reach on mobile, it counts for less everywhere.
This catches out plenty of firms. A developer hides a long section on phones to keep the page short, or puts the case studies behind a tab that only loads when tapped. Google says it does not load content that needs a tap, swipe or typing to appear, so that content drops out of the version Google weighs most.
AI assistants work a little differently. ChatGPT, Claude and Perplexity read the text of the page rather than viewing it on a phone, so what matters is that the full content is present in the page itself, not assembled later by scripts, which GPTBot, ClaudeBot and PerplexityBot do not run (Vercel and MERJ, December 2024). We explain how these crawlers read a site in how AI crawlers read your website. Google AI Overviews draw on Google's own index, so the mobile version matters there too.
The practical rule: the same words, the same proof and the same structure on the phone and the desktop. Change the layout, not the content.
What is the difference between responsive and mobile-first?
A responsive site rearranges itself to fit a smaller screen. A mobile-first site was designed for the smaller screen to begin with, then given more room on a desktop. Almost every site built in the last decade is responsive. Far fewer are mobile-first, and the difference shows.
A responsive site designed on a desktop carries the desktop's habits down to the phone. The large hero image pushes the headline below the fold. The three-column section becomes three long stacks. The menu collapses into an icon that hides ten items and several sub-menus. The contact form keeps every field.
A mobile-first site starts with harder questions. What does someone need to see in the first screen to stay? Which three pages matter most? What is the shortest route from arriving to getting in touch? The answers usually produce a simpler, faster site that also works better on a desktop.
What should a buyer see on the first phone screen?
Three things: who you help and with what, one line of proof, and one obvious next step. If a buyer has to scroll to find out what you do, many will not bother.
For example, a first screen that works for an outsourced finance firm might have:
- A headline such as "Outsourced finance teams for UK manufacturers with 50 to 500 staff".
- A proof line such as "Month-end closed in five working days", if that is true and you can show it.
- A single button, "Talk to a partner", which opens a short form or dials the office.
The weak version is more common: a full-screen photo of a handshake, a slogan about partnership and excellence, and a menu icon. The buyer learns nothing and has to work to find out whether you are relevant. We look at the signals that earn a buyer's confidence in what makes a buyer trust a website enough to get in touch.
How do you make your key pages readable on a phone?
Write and lay them out for a narrow screen and a distracted reader: short paragraphs, frequent plain headings, and the most useful information first in every section.
Keep the navigation short
Five or six main items is plenty for most B2B firms. Name them in the buyer's words, such as "Services", "Sectors", "Our work", "About" and "Contact". If a page cannot be reached in two taps from the homepage, ask whether it belongs in the menu at all.
Lead every section with the answer
On a phone, the first sentence of a section is often the only one read. Put the point first and the detail after. When we rebuilt ID-Pal's sector pages, the brief was the same: "Five industry pages rebuilt: fund administration, wealth management, legal, accountancy and estate agency. Each opens with the question a compliance lead types, names the regulator, and answers inside the first ninety words."
Watch tables, diagrams and PDFs
Wide tables and detailed diagrams break on small screens. Turn tables into short lists where you can, and never put important information only in a PDF.
Start case studies with the result
Open with the client type, the problem and the outcome in two or three lines, then tell the story for those who want it.
How do you make it easy to get in touch from a phone?
Remove every bit of effort you can. On a phone, each extra field, pop-up or hidden number costs you enquiries.
- Put a tap-to-call phone number and a tappable email address in the header or footer of every page.
- Cut the enquiry form to what you need to reply: name, work email, phone if they want a call, and a short message.
- Use the right field types, so the phone shows a number pad for phone numbers and an email keyboard for email addresses.
- Avoid full-screen pop-ups. Google's guidance on intrusive interstitials says not to obscure the whole page and to use banners that take up a small part of the screen. It accepts interstitials needed for legal reasons, such as consent, so keep a compliant cookie banner and make it small.
- If you offer booked calls, link to a calendar that works properly on a phone.
In our experience, these small fixes often do more for mobile enquiries than a full visual redesign, and they take days rather than months.
Do LinkedIn and other in-app browsers break forms and booking links?
They can. When someone taps a link inside LinkedIn, or inside many email and messaging apps, the page often opens in the app's own built-in browser rather than in Safari or Chrome. That browser may not share the visitor's usual cookies or logins, may block pop-up windows, and may handle downloads and new tabs differently.
The common casualties on B2B sites are booking widgets that open in a new window, forms that rely on a third-party script to submit, calendar links that ask the buyer to sign in, and analytics that treat every in-app visit as a new visitor. Since many LinkedIn visits happen on phones, this is where a lot of first visits happen.
Test it directly. Post a link to your contact page in a private message to a colleague, open it on a phone inside the LinkedIn app, and try to book a call and send the form. Do the same from your email app. Anything that fails there is failing for real buyers.
Should a B2B website have a sticky call button on mobile?
Often, yes, if it is slim and does not cover content. A small bar at the bottom of the screen with "Call" and "Book a call" keeps the next step in reach on long pages. Keep it to one line, make sure it does not hide form fields or the cookie banner's buttons, and check it does not cover whatever a keyboard user has selected. It should never behave like a pop-up.
How fast does it need to be on a phone?
Fast enough that the main content appears almost at once on an ordinary 4G connection: Google's Core Web Vitals thresholds ask for the main content within 2.5 seconds, a response to taps within 200 milliseconds and a layout shift score of 0.1 or less. We cover the thresholds and the fixes in does our website's speed and accessibility really affect enquiries?.
How do you test your website on a phone properly?
Use real phones and real people, not only the preview mode in a web browser. Emulators are useful for developers but they hide the problems a buyer actually meets.
Step 1: Compare visits and enquiries by device in GA4
In Google Analytics 4, open Reports, then Tech, then Tech details, and set the dimension to device category. Add your enquiry form submission as a key event and compare the key event rate for mobile and desktop, then repeat for your top ten landing pages. Read the result with one caveat: visits from the ChatGPT phone app often lose their referrer and are recorded as Direct, and GA4's AI Assistant channel, added in May 2026, does not cover Claude or Perplexity. A rise in Direct phone visits may be AI traffic you cannot see.
Step 2: Run your key pages through PageSpeed Insights
Google's free PageSpeed Insights tool shows how your pages perform on mobile, with the Core Web Vitals results and the main causes of delay. Test the homepage, your main service page and your contact page.
Step 3: Watch someone outside the firm use it
Hand your phone to someone who does not know the business, ideally someone like your buyers. Ask them to find out what you do, find a relevant case study and get in touch. Say nothing while they try, and note where they hesitate.
Step 4: Fix the worst three problems and test again
Take the three problems that stopped your tester, fix them, then repeat the test next quarter. For more on how each page should earn its place, see our guide to websites that bring work in.
What to do this month
- Open GA4 and compare phone and desktop visits and enquiry rates for your homepage, main service page and contact page.
- Try to get in touch with your own firm using only your phone, including from a link opened inside LinkedIn, and time how long it takes.
- Add a tap-to-call number and shorten your enquiry form to four fields or fewer.
- Replace any full-screen pop-up on phones with a small banner, keeping your cookie banner compliant.
- Run your three key pages through PageSpeed Insights and send the results to whoever looks after your site, with a date to fix the worst issue.
Frequently asked questions
Our contracts are signed at a desk. Does the mobile site still matter?
Yes. The decision may be made at a desk, but the shortlist is often made on a phone. If a buyer's first look at your site on their phone is confusing or slow, you may not make the shortlist that leads to the desk.
Is designing for mobile first more expensive?
Not usually. It is mostly a change in the order decisions are made, not in the amount of work. Mobile-first sites often end up simpler, with fewer heavy elements to build and maintain.
Do we need a separate mobile site or an app?
No. For B2B firms a single responsive website designed for the phone first is the right answer. Separate mobile sites mean two sets of content to maintain, and very few B2B buyers want to download an app to find out about a supplier.
What about tablets?
Tablets made up 4.72% of UK page views in August 2026, according to StatCounter. A site designed for phones and desktops almost always works on a tablet, so test your key pages on one if your analytics show a meaningful share, but most firms do not need to design for them separately.
Will a better mobile site help ChatGPT recommend us?
Indirectly. ChatGPT, Claude and Perplexity read the text of your pages rather than viewing them on a phone, so layout alone will not change what they say. But Google ranks on the mobile version, Google AI Overviews draw on that index, and making a site mobile-first usually makes the content clearer for every reader, human or machine.
Your buyers are already checking you on their phones, and the firms that make that first look easy win the next conversation. If you want a website designed around how buyers actually look at you, Website That Sells starts with the phone, or book a free Growth Review for three fixes in writing.
Sources
- StatCounter, Desktop vs mobile vs tablet market share in the United Kingdom (August 2026)
- Google Search Central, Mobile-first indexing best practices (December 2025)
- Google Search Central, Avoid intrusive interstitials and dialogs (December 2025)
- Google Search Console Help, Core Web Vitals report (accessed September 2026)
- Vercel, The rise of the AI crawler (December 2024)
- NiceLookingData, AI traffic in GA4: how ChatGPT, Perplexity, Gemini and Google AI Mode referrals show up (July 2026)




