Mobile website problems cost leads when they make an interested visitor work harder than necessary to understand the service, trust the business or make contact.
The biggest mistake is treating “mobile responsive” as a design checkbox. A page can technically fit a small screen and still be frustrating to use.
These 12 mobile website mistakes focus on lead generation: the moments where a phone user is most likely to give up before calling, messaging, booking or submitting a form.
12 mobile website mistakes that cost enquiries
| # | Mistake | What it costs |
|---|---|---|
| 1 | Phone number is not easy to tap | Urgent visitors cannot act quickly |
| 2 | Hero section is too tall | Main service and proof are pushed down |
| 3 | Slow or unstable loading | Users wait or tap the wrong element |
| 4 | Buttons are too small or crowded | Mis-taps and frustration |
| 5 | Menu is difficult to use | Visitors cannot reach key pages |
| 6 | Pop-ups and cookie banners dominate | Content becomes hard to reach |
| 7 | Forms fight the phone keyboard | Enquiry completion drops |
| 8 | Too many sticky widgets compete | Screen space disappears |
| 9 | Long text has poor spacing | Scanning becomes tiring |
| 10 | Images or tables overflow | Layout feels broken |
| 11 | Third-party tools are not mobile-friendly | Booking/payment journey fails |
| 12 | Nobody tests a real phone journey | Problems survive because previews look fine |
If mobile is only one part of a wider enquiry problem, use the conversion audit checklist to check traffic, trust, messaging and lead delivery as well.
1. The phone number is visible but not tappable
A phone number displayed as ordinary text creates unnecessary work.
On mobile, use a proper tel: link so the visitor can tap once and open the dialler.
Then check:
- the number is easy to find;
- the button is large enough;
- it is not hidden by another widget;
- the displayed number matches the dialled number;
- opening hours are accurate.
For urgent services, the phone action may deserve a sticky mobile position. For non-urgent services, it can remain a clear secondary option.
2. The hero section uses most of the first screen
Large desktop hero layouts often become enormous on a phone.
The user may see:
- a logo;
- a menu;
- a large empty background;
- half a headline;
- no service detail;
- no proof;
- no action.
Reduce decorative height. Make sure the first screen gives enough context to confirm the visitor is in the right place.
3. The page loads slowly or moves while the user is trying to tap
Mobile performance is not only about a score.
Watch the experience:
- Does the main heading appear quickly?
- Can the user interact while other assets load?
- Do buttons move?
- Does a late-loading image push the form down?
- Does a banner appear after the user starts reading?
Our guide to website speed and user experience explains how performance problems affect real use without treating one lab score as the whole story.
4. Tap targets are too small or too close together
A mouse pointer is precise. A thumb is not.
Check:
- menu items;
- accordion controls;
- form checkboxes;
- pagination;
- carousel arrows;
- phone and WhatsApp buttons;
- close icons;
- cookie choices.
Give controls enough size and spacing that the user can select the intended action without zooming.
5. The mobile menu is a maze
A compact menu is useful. A hidden information architecture is not.
Common problems include:
- too many nested levels;
- unclear labels;
- tiny expand arrows;
- menu does not close after navigation;
- important contact action buried at the bottom;
- menu panel extends beyond the screen.
Prioritise the pages a mobile visitor actually needs: services, key locations, pricing/process where relevant and contact.
6. Pop-ups and cookie banners occupy the whole screen
A consent interface must work, but it should not make the underlying site unusable.
Also review:
- newsletter pop-ups;
- discount pop-ups;
- chat prompts;
- app-install banners;
- exit-intent overlays;
- notification requests.
Desktop pop-up dimensions often become aggressive on small screens. Test the close action with one hand.
7. The form is technically responsive but painful to complete
A form can fit the screen and still be poor mobile UX.
Check:
- labels stay visible;
- email fields open an email-friendly keyboard;
- phone fields open a numeric-friendly keyboard where appropriate;
- dropdowns are understandable;
- error messages appear near the relevant field;
- the page scrolls to the error;
- the form keeps entered data after validation fails;
- autofill works sensibly;
- CAPTCHA is usable.
After fixing the interface, run the complete contact form test to make sure the enquiry also arrives.
8. Too many sticky elements compete for the same corner
Mobile sites often collect:
- sticky header;
- cookie button;
- WhatsApp bubble;
- chat bubble;
- call bar;
- back-to-top button.
Each tool may be useful alone. Together they can cover content, controls and form buttons.
Choose priorities. A visitor should not need to play “find the text” between floating circles.
9. The content is readable on desktop but exhausting on mobile
Long-form content can work perfectly well on mobile if it is structured.
Use:
- short paragraphs;
- clear headings;
- lists;
- tables only where they remain usable;
- enough line spacing;
- comfortable margins;
- direct answers near important questions.
Do not reduce font size simply to fit more words on screen.
10. Images, tables and embeds overflow
Test:
- comparison tables;
- maps;
- videos;
- calendars;
- before-and-after sliders;
- PDF embeds;
- social posts;
- large logos.
An element that creates horizontal scrolling makes the whole page feel broken.
For wide tables, consider a scrollable container or a mobile alternative rather than shrinking text until it is unreadable.
11. Third-party booking, payment or chat tools break the journey
Your own page may be excellent. The lead can still disappear when the visitor enters an embedded tool.
Test the full journey through:
- booking calendars;
- payment gateways;
- finance applications;
- CRM forms;
- live chat;
- quote calculators;
- map directions.
Check real mobile behaviour, not only whether the embed appears.
12. The site is never tested on a real phone
Browser responsive mode is useful during design. It is not the final test.
Use at least one real iPhone and one real Android device where practical, or test across a suitable device service.
Try:
- arrive from Google;
- open the menu;
- read a service page;
- tap the main CTA;
- complete the form;
- make a test call;
- open WhatsApp;
- dismiss the cookie banner;
- rotate the device;
- use mobile data.
Mobile contact options need a hierarchy
Mobile gives businesses more possible actions because the device can call, message, email and open apps.
That is useful, but it can create clutter.
Our phone, form and WhatsApp comparison explains when each contact route makes sense.
A simple rule:
- one primary contact action;
- one clear alternative;
- other options available without competing visually.
Mobile mistakes by page type
| Page | Critical mobile check |
|---|---|
| Homepage | Can users understand the business and reach a service quickly? |
| Service page | Can users compare scope, proof and next step without endless scrolling? |
| Location page | Is service area clear and contact action easy? |
| Contact page | Do form, phone and map work cleanly? |
| Checkout | Can payment be completed without zooming or hidden controls? |
| Blog guide | Is long content easy to scan and are useful links tappable? |
A 20-minute real-phone test
- 3 minutes: load the homepage on mobile data.
- 3 minutes: navigate to the main service using the menu.
- 3 minutes: read and scroll with one hand.
- 3 minutes: test phone/WhatsApp links.
- 4 minutes: complete the main form.
- 2 minutes: dismiss every overlay.
- 2 minutes: write down the top three frustrations.
What to fix first
Prioritise issues closest to revenue and easiest to verify.
- Broken contact or checkout action.
- Hidden or unusable primary CTA.
- Form failures.
- Major layout overlap.
- Slow or unstable critical content.
- Navigation problems.
- Readability and spacing.
- Cosmetic improvements.
If the site has accumulated structural mobile problems across many templates, a targeted website redesign may be more efficient than fixing each symptom separately. The decision should come from the audit, not from the age of the site.
Accessibility problems often become conversion problems on mobile
Mobile usability improves when controls are understandable, focus states are visible, labels are associated with fields and the interface can be used without precision tapping.
Check the page with larger text settings and, where possible, keyboard or assistive technology. A design that only works at one text size is fragile.
Do not hide important content just to make mobile shorter
Some sites solve a long mobile page by removing useful pricing, proof, FAQs or process information. That can make the page visually shorter while making the buying decision harder.
Instead:
- remove repetition;
- use clear section headings;
- collapse genuinely secondary detail;
- keep core buying information visible;
- move decorative elements below decision-critical content.
Test the bottom of the screen as carefully as the top
The lower edge of a phone is crowded territory. Browser controls, operating-system gestures, sticky CTA bars, chat bubbles and cookie controls can all compete there.
Check that a sticky call or quote bar does not cover:
- form submit buttons;
- checkout controls;
- pagination;
- cookie choices;
- chat input;
- important legal links.
Create a small mobile device test matrix
| Test | Why |
|---|---|
| Small iPhone-sized viewport | Find cramped layouts and overlap |
| Large phone | Check scaling and spacing |
| Android/Chrome | Test common browser behaviour |
| Safari/iOS | Catch input, viewport and sticky-position differences |
| Mobile data | See the page under less forgiving network conditions |
You do not need every handset on the market. You need enough real testing to stop designing only for the desktop editor.
Prioritise mobile performance by customer task
Performance work should protect the elements people need first. On a lead-generation page, that may be the headline, service summary, phone button and form. On ecommerce, it may be product information, variant selection, basket and checkout.
Audit third-party scripts that delay those tasks. Chat widgets, maps, review embeds, tracking scripts and video can all add value, but they should not stop the primary journey becoming usable.
Test form completion with poor connectivity
Mobile users are not always on fast Wi-Fi. A form that works perfectly in the office may fail when a request times out, a file upload stalls or the connection changes.
Test with mobile data and a small image upload where relevant. Make sure the user receives a clear success or failure state and is not encouraged to submit the same enquiry repeatedly because the page appears frozen.
Watch orientation and browser chrome
Rotating a phone, opening the keyboard or scrolling can change the available viewport. Fixed-height sections and sticky elements sometimes break only after those changes. Test portrait and landscape where the journey could reasonably use both.
Use mobile lead data to decide what deserves attention
Compare mobile and desktop by successful enquiries, not only sessions. If mobile traffic is strong but qualified leads are disproportionately weak, inspect the contact journey, page speed and forms before blaming the traffic source. If both devices convert poorly, the problem may be the offer or intent rather than mobile design alone.
Keep a mobile bug log instead of fixing problems from memory
When you spot a mobile issue, record the device, browser, page, action and screenshot. This makes recurring problems easier to reproduce and prevents a developer from fixing only one visible symptom.
Mobile website mistakes FAQs
What is the biggest mobile website mistake?
For lead-generation sites, a broken or difficult contact journey is often the most commercially serious problem. That includes untappable phone numbers, unusable forms and buttons hidden by overlays.
Does a responsive website automatically mean it is mobile-friendly?
No. Responsive design means layouts adapt to screen size. Mobile usability also depends on touch targets, speed, forms, menus, readability, overlays and the complete customer journey.
Should I use a sticky call button on mobile?
It can be useful for phone-led services, especially urgent ones. Make sure it does not cover content or compete with several other sticky widgets.
How do I test mobile website conversion?
Complete the full customer journey on a real phone, verify the enquiry arrives, and compare successful leads from mobile traffic rather than relying only on visual previews.
Should I hide long content on mobile?
Not automatically. Useful long content can work well when it is clearly structured, readable and easy to navigate. Remove repetition and clutter rather than hiding information customers need.
