A business website can make contacting you on a phone difficult when it hides the offer, loses the contact button, scrolls sideways, responds poorly to touch or puts barriers in the form. These are signs to investigate, not proof of lost revenue. First, retrace the customer's journey from arrival to contact, and only then decide on an upgrade.
How to distinguish a mobile problem from a problem with the offer
A low number of enquiries does not automatically mean you need a new website. The cause may be poorly matched traffic, an unclear service scope, seasonality or a technical error. This guide covers one specific situation: an interested person trying to understand the offer and contact the business on a phone. It does not replace an analysis of campaign effectiveness or conversations with customers.
Have the URL of an important service page, a phone and a sheet of paper ready. Open the website without logging in, preferably also outside the company Wi-Fi network. Record specifics: the URL, step, symptom and expected action. “Contact option covered by a banner” is a useful observation; “the website is outdated” does not yet tell you what to fix.
1. On arrival, it is unclear what the business offers
On a computer, a headline, description and button can fit side by side. On a phone, a tall image, several empty gaps and a generic slogan can push essential information far down the page. The user sees an attractive cover but cannot tell whether the business solves their problem. This particularly affects visits directly to a service page, bypassing the homepage.
Test: after opening the page, try to say in your own words what can be ordered, who the service is for and what the next step is. If answering requires searching through the menu, simplify the heading and introduction. This is an editorial recommendation, not a guaranteed way to increase conversion. Keep important offer conditions rather than removing them merely to shorten the screen.
2. The contact button disappears or leads somewhere else
A mobile menu often replaces desktop navigation. The problem begins when the only route to contact disappears with it. Another version is an “Ask about the service” button that opens the general homepage, a nonexistent section or a messaging app without explanation. A colourful button alone does not make a working journey.
Test: scroll to the middle of the description and use the available call to action. Check the final URL and what is actually visible when scrolling stops. Changing the URL fragment to “#contact” is not enough if the form is still off-screen. Choose one main next step that matches the button's promise; additional contact details can remain as alternatives.
3. Text or buttons run off the screen
Symptoms include horizontal scrolling across the entire page, a cut-off button label or having to zoom out. The cause may be a fixed-width image, a wide table, a long URL or a multi-column layout. Hiding overflow in CSS can mask the problem, but it will not fix content that cannot be reached.
Test: check the entire page at a width of 390 px, then at a narrower viewport. In its Reflow criterion, W3C describes the reflow of ordinary content at a width equivalent to 320 CSS pixels, with specified exceptions. A result at 390 px therefore does not confirm WCAG compliance. A table may have its own scrolling; paragraphs, fields and CTAs should remain readable without moving the entire page sideways.
4. It is difficult to tap a menu item or action
Tiny icons, tightly spaced links and a banner's close button can make a simple task difficult. The actual clickable area matters, not just the size of the drawn icon. Also check whether a dropdown menu can be closed and whether it stays over the content after an item is selected.
Test: use the menu and contact options without zooming in. WCAG 2.2 criterion 2.5.8 specifies a minimum of 24 × 24 CSS pixels or compliance with the stated exceptions, including those concerning spacing. This is not a universal promise of usability. For primary actions, it is worth designing a larger touch area and checking it on a device rather than limiting yourself to the formal minimum.
5. The page jumps or does not respond to touch
A large image loads late, a button moves after a font loads, and tapping the menu produces no response for a moment. The user may not know whether the action was performed. However, do not draw conclusions about speed from one successful visit on a new phone with a fast connection.
Test: record the symptom you observe and separate it from measurement. The web.dev documentation gives thresholds for a good experience of LCP up to 2.5 s, INP up to 200 ms and CLS up to 0.1, assessed at the 75th percentile, separately for mobile and desktop devices. A laboratory result does not replace real-user data. Missing data means neither success nor failure; mark it as not measured.
6. The form asks for too much or does not explain errors
For an initial enquiry, you rarely need every invoicing detail, a registered office address and a detailed brief. Consider the purpose of each required field. Users should understand what you expect, why a field is required and how to correct their input. A placeholder that disappears while typing should not be the field's only description.
Test: without submitting a fictional enquiry, check the labels, required-field indicators and validation messages. W3C recommends format instructions and clear information about errors and the submission outcome. An on-screen confirmation proves only what the application actually handled. Message delivery must be checked separately in an agreed, clearly labelled test and in the recipient's inbox; do not create a random production enquiry.
7. A banner or widget covers an important step
A cookie banner, chat window and sticky contact bar may each look reasonable separately, yet together occupy most of the screen. On a phone, the on-screen keyboard adds to this. As a result, the user cannot see a button, instructions or an error message. Testing in a fresh session matters more here than the owner's view, where all the pop-ups were dismissed long ago.
Test: check the initial view and the state after rejecting optional cookies. Open and close the widget without sharing personal data. See whether you can still read, scroll and reach the contact option. Do not accept tracking just to hide the problem. Consent rules and wording require a separate assessment; this test concerns the accessibility of the journey.
A checklist to give your provider
Instead of ordering a “mobile refresh”, collect a list of observations. The outline below helps you check fixes under the same conditions in which the problem was found. It is not a pricing model or an assessment of financial loss.
- URL and conditions: record the URL, date, device, browser, viewport width and cookie state.
- Customer journey: arrive on the service page → understand the scope → choose a contact option → see a clear next step.
- Evidence: attach a screenshot and a description of one reproducible symptom, without customer data.
- Priority: unavailable contact options and obscured actions first, then usability difficulties, then cosmetic issues.
- Acceptance criterion: specify the button's expected destination, field accessibility and the absence of clipped content.
- Retest: follow the same journey after the change, including from another page and in a fresh session.
Targeted fixes or a full upgrade?
If the offer and structure are understandable and the problem concerns a single element, start with a limited fix. When the same barriers recur across many templates, menus and forms, a broader upgrade may be justified. Base the decision on the extent of reproducible errors and the maintainability of the current solution, not solely on the website's age.
Record a baseline before making changes. Compare contacts from similar sources and devices, accounting for seasonality and whether measurement is working. A phone-link click is not a conversation, and a form submission is not a sale. This guide does not present any company's results or promise more enquiries; it provides conditions for making a decision and checking the work performed.
Sources and scope of recommendations
Checked on 24 October 2026. Technical requirements come from the documentation below; the diagnostic order and priorities are editorial recommendations.
- W3C — Reflow, criterion 1.4.10: content reflow and exceptions.
- W3C — Target Size (Minimum), criterion 2.5.8: target sizes and spacing.
- W3C — Form Instructions and User Notifications: form instructions and messages.
- web.dev — Web Vitals: definitions, thresholds and interpretation of measurements.
- web.dev — Responsive web design basics: adapting layouts to the screen.
Want to improve your mobile website?
Prepare the URL and a description of the point where making contact becomes difficult. Let's discuss the scope of a fix or upgrade before you decide to rebuild.
Let's talk about improving your website ↗