A customer is standing outside your shop, phone in hand, quickly looking up your opening hours. Another is on the bus trying to find a tradesperson's phone number. A third taps a short enquiry into a contact form at the kitchen table. This is the everyday reality in which a local business website succeeds or fails - and this reality is mobile. Since 5 July 2024, Google has assessed websites solely on the basis of their mobile version (Google Search Central). A site that only works on a large desktop screen but stumbles on the phone therefore loses twice: with visitors and in search. This article explains why a website in 2026 has to be conceived from the small screen up - not shrunk afterwards, but built mobile-first from the ground. As a web agency from the Hildesheim region, we build websites so that they work as reliably on the smartphone as they do at the desk.
Key takeaways
- Since 5 July 2024 (Google Search Central), Google has assessed websites solely on their mobile version. Content, structured data or images that exist only in the desktop layout cannot be evaluated by Google in full.
- Mobile-first means designing for the small screen first and expanding afterwards. A responsive page that merely shrinks a desktop template keeps its running order: visitors scroll past galleries and body text before the phone number appears.
- In Germany about 44 percent (StatCounter) of website visits come from smartphones, and the share is higher for local businesses: 76 percent (Think with Google) visit a business within a day of a local phone search and want opening hours, address and contact at once.
- WCAG 2.2 sets a minimum of 24 by 24 (WCAG 2.2) CSS pixels for controls, while Google recommends around 48 by 48 (Google) pixels for tap targets. Two correctly sized buttons stuck together still cause mistaps, so spacing counts as well.
- Google measures Core Web Vitals at the 75th percentile (web.dev) of mostly mobile page views: LCP below 2.5 seconds, INP below 200 milliseconds, CLS below 0.1 (web.dev). A banner shifting in while loading sends the thumb next to the call button.
- Typical contact and checkout flows run to around 11 form fields (Baymard Institute); a first enquiry needs no more than name, phone number and a short message. The phone number belongs in a tappable call link rather than plain text to copy out.
Why mobile-first Is Non-Negotiable in 2026
Mobile-first does not mean a website somehow also runs on the phone. It means designing the page for the small screen first and then expanding it for larger displays - not the other way round. For a long time it worked in reverse: you built a desktop page and squeezed it onto smartphone width at the end. The result is tiny type, misplaced buttons, oversized tables and forms that become a test of patience under the thumb. Mobile-first flips the order and asks: what does a visitor operating the site one-handed on the move actually need - and how do they get there in two or three taps?
The share of mobile visits is higher than many businesses assume, and at the same time lower than sensational percentages claim. Worldwide, mobile devices have accounted for more than half of all web traffic since 2017 (Statista); in June 2026 the global mobile share stood at around 52 percent (StatCounter). In Germany the picture is different: only about 44 percent (StatCounter) of website visits come from smartphones, because a lot of browsing happens at the desktop workplace here. For a local business, though, the national average is the wrong figure - it mixes office work, online banking and big-screen research with the very different situations in which someone searches for a business nearby.
Because the searches that really matter for a tradesperson, a restaurant or a practice happen on the move: at the bus stop, in the car, right outside the door. Google found that 76 percent (Think with Google) of people who search locally near them on a smartphone visit a relevant business within a day. In these moments mobile use is the norm, not the exception. The mobile share that counts for a local business is therefore well above the 44 percent national average - and that is exactly why the mobile version is not a side note but the actual stage.
Rethink, don't just shrink
What Google's Mobile-First Indexing Means for Ranking
The most consequential change lies in how Google captures websites in the first place. After years of gradual transition, the search engine completed the switch to mobile-first indexing on 5 July 2024 (Google Search Central). Since then Google crawls practically all websites with the mobile Googlebot and bases index and ranking on the mobile version. The desktop view no longer plays a separate role in the assessment - it is not drawn on separately any more.
The mobile version is the assessed version
For local businesses this is a clear signal: the mobile version has to be complete in content, not stripped down. Anyone who shows important text, services or contact details only on the desktop gives away visibility. In practice, that means being consistent on a few points:
- Complete content on mobile: text, services and FAQ are fully available on the phone too and are not removed to save space.
- Structured data on mobile: markup such as opening hours, address and reviews is present in the mobile version, not just the desktop variant.
- Images with alt text: images embedded on mobile carry meaningful alternative text so Google can interpret their content.
- Matching metadata: titles and descriptions are identical across both views so the assessment is not based on a stripped-down version.
- Reachable internal links: the linking between pages works on mobile just as on desktop, so Google can capture the whole website.
Anyone who wants to be found locally therefore treats the mobile version as the first address, not a fallback. How ranking comes about overall is explored in our article on SEO basics for local businesses; the technical basis for it is laid by sound search engine optimization from Hildesheim that thinks mobile and content signals together.
The Everyday Reality of Local Businesses Is Mobile
To understand how a mobile website has to be built, it helps to look at what people on the phone actually want from a local business. They rarely research at leisure - they need a specific piece of information and a simple action, fast: When are you open? Where do I find you? How do I reach you quickest? These few questions decide the enquiry, and they have to be answered without detour.
Opening hours visible instantly
The most common mobile question to a local business is: are you open right now? Anyone who finds the answer only after long scrolling is often already gone. Current opening hours belong visibly at the top.
Click-to-Call: tap instead of type
On the phone the number is not text to memorise but a button to call. A tappable call link starts the call with a single touch - no noting the number and switching apps.
Address and quick directions
Location and route are decisive on the move. A clearly visible address and a direct path to navigation save the visitor the search and bring them to you.
A short enquiry on the go
Those who prefer not to call send their enquiry via a form - often from the waiting room or the building site. A short, tappable form makes that possible in under a minute.
These actions decide the enquiry, and they have to be reachable without detour. Anyone who finds the phone number only after zooming twice is more likely to call the next provider. In addition, a well-kept Google Business Profile ensures opening hours and address are already correct in search, and online appointment booking for local businesses takes in enquiries even when no one at the business can answer the phone.
Built Thumb-Friendly: The Design Rules
A smartphone is usually held in one hand and operated with the thumb. From this follows a simple rule: important controls belong where the thumb comfortably reaches, and they have to be large enough to hit reliably. What seems trivial on the desktop with a mouse and a large screen - a small link, a tight button - becomes a hurdle on the phone. Good mobile design removes these hurdles from the outset.
There are concrete benchmarks for the size of controls. The accessibility standard WCAG 2.2 requires a minimum size of 24 by 24 (WCAG 2.2) CSS pixels for controls, so they can be hit safely even by people with motor impairments. For tap targets, Google recommends at least 48 by 48 (Google) pixels with sufficient spacing, so you do not accidentally hit the neighbouring element. Neither is a luxury - both are the basis of a page that can be operated safely on the phone.
Large, tappable buttons
Buttons and links are large enough and far enough apart for the thumb to hit them reliably - at least 48 pixels, with spacing to the next element.
Click-to-Call and tel links
Phone numbers are stored as clickable links that start the call directly. That saves typing and noticeably lowers the barrier to contact.
Short forms
Forms are limited to a few required fields and bring up the right keyboard - a number pad for the phone, an email keyboard for the address.
Readable type without zoom
Body text is easy to read without zooming in. Sufficiently large type and enough line spacing spare the eye the strain on a small display.
Reachable navigation
The menu is within thumb reach and clearly structured. Key targets such as contact and call sit in the comfortable area, not hidden at the top edge.
Stable, calm layout
Content does not jump around while loading. Fixed places for images and banners prevent the thumb from mistapping because the page shifts at the last moment.
How large tap targets should be
| Aspect | Desktop page squeezed afterwards | Built mobile-first from the start |
|---|---|---|
| Type | Small, often readable only with zoom | Large enough, readable without zoom |
| Buttons | Tight, hard to hit | Large and spaced, thumb-friendly |
| Navigation | Carried over from desktop, overloaded | Reduced to the most important targets |
| Form | Many fields, tedious typing | Few required fields, matching keyboard |
| Phone number | Plain text to type out | Tappable call with one touch |
| Layout | Jumps while loading, images shift in | Stable, fixed places, calm |
Core Web Vitals on the Phone: Stable Layouts
Google measures the user experience with three metrics, the Core Web Vitals, and assesses them at the 75th percentile (web.dev) of real page views - predominantly from mobile devices. This matters: a page that feels smooth on the fast office desktop can fail on an average smartphone over a mobile connection. Anyone testing only on their own large screen does not see this problem - Google and the visitors do.
For mobile design, two of the three values are especially decisive. Cumulative Layout Shift (CLS) measures whether the layout jumps while loading - a good value is below 0.1 (web.dev). On small displays this is particularly tricky: if an image or a consent banner shifts in while the thumb is already on its way to the call button, the tap lands off target. Interaction to Next Paint (INP) measures how fast the page reacts to a touch; below 200 milliseconds (web.dev) is considered good. The third value, Largest Contentful Paint (LCP), should be under 2.5 seconds (web.dev) so the most important content appears promptly.
Pure loading speed - how quickly anything appears at all and which levers in images, hosting and code help - we covered in detail in the article improve website loading speed. Here it is about the other, mobile side of the coin: calm, stable layouts, large tap targets and operation that does not stall even on a fluctuating mobile network. The two belong together, because as many as 53 percent (Google) of users leave a mobile page if it takes longer than three seconds to load - and those who stay want to be able to operate the page comfortably afterwards.
The mobile version is not half the website. It is the website that Google assesses and that your customers actually hold in their hands - everything else is the exception.
Short Forms and Click-to-Call: Conversion on the Phone
Typing on a smartphone is tedious. Every additional form field costs patience - and therefore enquiries. Research by the Baymard Institute shows that average checkout and contact flows contain around 11 form fields (Baymard Institute), although in many cases roughly half would suffice. For a first enquiry you rarely need more than name, phone number and a short message. Every field you cut lowers the barrier and raises the number of people who actually submit the form.
Just as effective is the simplest of all mobile functions: the call by touch. A phone number stored as a link starts the call instantly - no noting, no switching apps, no mistyped digit. For many local businesses the direct call is the most important path to an enquiry, and on the phone it is just one touch away. These details decide whether a visit turns into a contact.
- Contact details and the call button sit in the immediately visible area, not only after long scrolling.
- The phone number is stored as a tappable call link, not as plain text.
- The form is limited to a few required fields - name, phone, short message.
- The right keyboard appears automatically for phone and email fields.
- Buttons are wide enough for the thumb and clearly separated from the neighbouring element.
- No intrusive overlays permanently cover the content or the submit button.
These details add up. A more usable mobile page turns into more calls and more completed forms - exactly the goal of any conversion optimisation. How visitors are turned into enquiries systematically is shown in the article turn website visitors into enquiries. And precisely on small displays, a GDPR cookie banner must not permanently cover the content, while large tap targets and readable type at the same time pay into accessibility under the BFSG - mobile usability and accessibility pull in the same direction.
How We Build Mobile-First in Hildesheim
Our approach is simple to describe and makes the difference in practice: we design every website for the small screen from the start and then expand it for tablet and desktop - not the other way round. That way no desktop page has to be laboriously squeezed onto phone width at the end; instead a web design from Hildesheim emerges that works on the smartphone first. Key actions such as calling, directions and enquiring sit where the thumb reaches them, the type is readable without zoom, and the layout stays calm while loading.
For existing sites, the best moment to put this right is a planned website relaunch: instead of patching a grown structure ever further, the foundation is laid cleanly once - mobile-first, fast and maintainable. We measure the Core Web Vitals on real mobile devices, check tap targets and forms, and make sure the mobile version is complete in content so that Google's mobile-first indexing does not miss anything.
A mobile-first site is not an end in itself but pays directly into more enquiries from the region. Those who combine it cleverly with local visibility gain in several places: whether you first invest in Google Ads or SEO, think about more enquiries through your website or strengthen local visibility through local SEO - the foundation in every case is a page that convinces on the device your customers actually use: the smartphone in their hand.
Sources and studies