Website Looks Bad on Mobile
On phones, your layout, menu, text, buttons, or forms are cramped, broken, or hard to use — and phones are where most of your visitors actually are.
Common signs of this issue
- Text is tiny, or reading requires pinch-and-zoom.
- The menu doesn't open, opens behind content, or overlaps the page.
- Buttons and links are too small or too close together to tap reliably.
- Content runs off the screen sideways, or the whole page scrolls horizontally.
- Forms are unusable — fields cut off, keyboards covering inputs, submit buttons unreachable.
- It looks fine on your desktop, which is why it's gone unnoticed while mobile visitors struggled.
Safe checks you can do yourself
None of these require sharing passwords with anyone.
- Test on two or three real phones (yours, a family member's, ideally one iPhone and one Android) — not by narrowing a desktop window, which approximates the layout but misses touch targets, real keyboards, and Safari quirks.
- Walk the visitor's actual journey on a phone: find the menu and open it, read a service page, tap the phone number (does it dial?), fill and submit the form, tap the main button. These few interactions are where mobile problems cost money — a slightly awkward layout is cosmetic; an unusable menu or form is a closed door.
- Scope the damage: is it every page or just some? One broken page points at that page's content — usually a wide element pasted in. Every page points at the theme or a site-wide setting. The fixes differ completely in size.
- Hunt the classic rogue elements that force sideways scrolling: a wide table, an embedded map or video, an oversized image, or content pasted from Word/email carrying fixed pixel widths. Removing or re-adding one element at a time on a test page finds the culprit quickly.
- Check the timeline: did mobile break after a theme update, a new plugin, or a batch of pasted content? Recent-change problems are narrow and reversible; always-been-this-way problems are usually the theme's age showing.
- Check the theme's own claims: a theme from the last several years is almost certainly responsive (mobile-adapting) by design — pointing at content-level culprits. A genuinely ancient theme that predates mobile-first design is a bigger conversation (see below).
- Glance at Search Console if you have it — its page-experience and usability information reflects how Google sees your mobile pages, which doubles as a priority list.
What this usually means
Modern themes adapt to phones automatically, so most mobile ugliness comes from content and additions fighting the theme: pasted material with fixed widths, wide tables and embeds, oversized images, or a plugin's output that ignores screen size. These are narrow, fixable problems — one element, one page, one setting — which is why scoping (every page vs one page) is the first diagnostic.
If the whole site is fundamentally cramped and non-adaptive, the theme itself likely predates responsive design or was customized in ways that broke it. That's the honest fork in the road: a targeted cleanup can't modernize a pre-mobile theme, and a theme change or rebuild — while bigger — is sometimes the truthful recommendation. A review tells you which side of the fork you're on before you spend either way.
The stakes are simple: most traffic is mobile, Google indexes and ranks the mobile version of your site first, and visitors judge trustworthiness in seconds. A site that's broken on phones is broken for the majority of its audience while looking fine to its desktop-using owner — the most common blind spot in small business web presence.
What not to do
- Don't paste fixed pixel widths into content (or paste directly from Word) — fixed-width content is the single most common way owners break their own mobile layout.
- Don't judge mobile by shrinking your desktop browser — it misses touch targets, keyboards, and Safari behavior; real phones or nothing.
- Don't rebuild the whole site before scoping — if it's one rogue table on one page, a rebuild is a five-thousand-dollar fix for a fifty-dollar problem.
- Don't disable the mobile layout to 'show the desktop version' on phones — a zoomed-out desktop site is worse for visitors and for Google than an imperfect mobile one.
- Don't ignore it because desktop looks fine to you — you are the site's least representative visitor.
- Don't fix layout while ignoring speed — mobile is also where heavy pages hurt most; the speed guides pair naturally with this one.
When to get help
A focused mobile cleanup — fixing rogue elements, menu behavior, tap targets, and form usability on your key pages — is well-defined work, typically a session or two with visible before/after on a real phone. A full theme change or rebuild is the bigger prescription, warranted only when the foundation genuinely predates mobile design. A short review distinguishes the two honestly — ask specifically "cleanup or rebuild, and why" — and be wary of anyone who reaches for the expensive answer without scoping first.
Not sure what to do next?
Answer a few short questions and we'll point you to the safest next step — DIY, a freelancer, or a direct review. No passwords required.
Frequently asked questions
How do I know if my site is mobile-friendly?
Test on real phones: open the menu, read a page, tap the number, submit the form. For Google's view, Search Console's page-experience reports show how your mobile pages measure up. Five minutes of honest phone testing beats any tool's summary.
Is one broken page a whole-site problem?
Usually not — a single page breaking on mobile points at that page's content: a wide table, an embed, pasted fixed-width material. Site-wide breakage points at the theme. Scope first; the two fixes differ by an order of magnitude in cost.
Why does content pasted from Word break my mobile layout?
Pasting from Word or email carries hidden fixed widths and formatting that override your theme's flexibility, forcing pages wider than phone screens. Paste as plain text (or use the editor's paste-as-text option), then format in the site editor.
Does a bad mobile site hurt my Google rankings?
Yes — Google evaluates and indexes your mobile version first, and mobile usability feeds its page-experience signals. The direct penalty is modest; the indirect one (most visitors bouncing off a broken experience) is the expensive part.
My theme is from 2012 and mobile has never been good. Can it be patched?
Honestly, usually not worth it — themes predating mobile-first design need fighting on every page, and the patches break with updates. A modern theme (keeping your content) is typically cheaper than perpetual patching, and everything from speed to security improves with it.
What should I test after any mobile fix?
The money path, on a real phone: menu opens, pages read without sideways scrolling, phone number dials on tap, form submits, main button works. If you sell, add checkout. That list caught the problem; it also verifies the fix.