RunCabin Blog · Fix-it guide
Why does my website look bad on my phone?
August 15, 2026 · 7 min read
Short answer: the site was built and checked on a laptop screen, then never re-checked on the narrow, touch-only screen most of your customers actually use. That gap - "looks fine on my computer" versus "looks broken on my phone" - is one of the most common, least-noticed reasons a website stops sending jobs, because nobody reports it. A visitor who hits a broken layout does not email you about it. They just leave.
Here is what "bad on phone" actually looks like, why it happens even on sites that used to be fine, and how to fix it without a redesign project.
What "bad on phone" actually looks like
| Symptom | What it usually means |
|---|---|
| Text so small you have to pinch and zoom to read a sentence | The page was laid out at a fixed desktop width and shrunk to fit, instead of reflowing for a narrow screen |
| You can scroll sideways as well as up and down | Something on the page (an image, a table, a wide banner) is wider than the phone screen and forcing the whole layout to stretch |
| Buttons or links are so close together you tap the wrong one | Tap targets were sized for a mouse pointer, not a fingertip, which needs more room |
| The menu will not open, or opens and covers the whole screen with no way back | A desktop dropdown menu with no mobile version built for it |
| The page takes a long time to appear, or images pop in one at a time | Large, unoptimized photo files that a phone on cellular data has to download in full before showing anything |
Any one of these on its own is a minor annoyance. On a local-service site, where the visitor is often standing in the exact moment they need help - the kitchen with the leak, the driveway with the dead sprinkler - it is usually enough to send them back to the search results.
Why it happens even to sites that used to look fine
Three ordinary causes, none of them anyone's fault at the time:
- The site was never built to be responsive. "Responsive" means the layout automatically reflows to fit whatever screen opens it - phone, tablet, or laptop - from one single page. Older sites, and some DIY page-builder templates, were built at a fixed width and simply scale that same layout down, which is why the text ends up tiny and the buttons end up cramped.
- A page builder let the desktop and mobile views drift apart. Many DIY builders let you drag and resize elements on a desktop-sized canvas, with a separate "mobile view" you have to open and fix by hand. It is an easy step to skip - most owners build on a laptop and never open the mobile editor - so every future edit (a new phone number, a new photo) gets made on the desktop version and quietly never applied to the phone version.
- Phones themselves keep changing shape. A layout that was manually tuned to fit one phone a few years ago can look wrong on a newer, larger, or differently-proportioned screen it was never tested on. A genuinely responsive layout does not need retuning every time a new phone ships - it adapts on its own.
Why this matters more than a cosmetic complaint
People searching for a local plumber, painter, cleaner, or landscaper overwhelmingly do it from a phone, often in the moment the problem is happening - not later at a desk. If your site is hard to read or hard to tap on that exact device, in that exact moment, the visitor does not fight it. They hit back and call the next name on the results page. Nobody files a complaint about a menu that would not open; it just shows up later as a slower month with no obvious cause, the same way a "Not Secure" warning or a broken contact form quietly costs jobs nobody hears about.
It also affects whether people find you at all. Search engines look at how a page performs on mobile devices as part of deciding where to rank it, since that is how most people search. A site that is hard to use on a phone is working against itself twice: fewer people are shown it, and the ones who do click through are more likely to leave.
How to check your own site right now, for free
Skip the tools and do the honest version: pick up your own phone, on your regular cell signal rather than your office wifi, and try to do what a customer would do.
- Read the headline and the first paragraph without pinching to zoom.
- Tap the phone number - it should dial immediately, not just highlight the text.
- Open the menu, then close it, then get back to where you started.
- Fill out the quote form with your thumbs, start to finish.
- Watch how long the page takes to fully load on cellular data, not wifi.
If any of those steps makes you stop and think "I know a trick to get around this," a first-time visitor - who has no reason to be patient with your site - will not find the trick. They will leave. Ask a friend or your spouse to try the same five steps cold, on their own phone, without you coaching them; watching where they hesitate tells you more than any checklist.
What actually fixes it
The fix is not a "mobile version" bolted onto the existing site - that was the old workaround, back when some businesses ran a separate stripped-down address just for phones. It is not needed anymore, and it creates two pages to keep in sync instead of one. What fixes it is the underlying page being responsive: one layout, one set of content, that reflows itself to whatever screen opens it.
In practice, that means:
- Text that resizes to the screen, not a fixed pixel size copied from a desktop design.
- Buttons and links sized and spaced for a fingertip, not a mouse pointer.
- A phone number that is a real tap-to-call link in plain text, not an image or a number buried in a paragraph - the same fix that matters for a contact form vs. just a phone number.
- Photos sized for the web, not the multi-megabyte original straight off a phone camera, so the page loads fast on a job-site cell signal.
- A menu built to collapse and reopen cleanly on a narrow screen, not a desktop dropdown squeezed down.
If your site is on a DIY builder, most platforms do have a mobile-editing view - it is just a separate step from the desktop editor, so go check it directly rather than assuming it inherited your desktop changes. If the site is older, built by a designer years ago, or was never responsive to begin with, retrofitting a fixed desktop layout is usually slower and more expensive than it looks; a from-scratch responsive rebuild is often the faster path, the same call as when a web designer disappears and the honest move is to rebuild rather than resuscitate old code.
Where RunCabin fits
Every site RunCabin builds is responsive by default - one layout that adapts to phone, tablet, and laptop, for $39.99/mo with no separate mobile plan, no mobile add-on, and no second editor to remember to open. There is also no drift between a desktop version and a mobile version to fall out of sync, because there is only one page: when you change something, you say it in plain English - "make the phone number bigger" or "the menu is hard to tap, fix it" - and the AI updates the one responsive layout everyone sees, on whatever device they're holding.
See a mobile-friendly site built for your business
We build a real preview with your name, your work, and your city - before you pay anything. Sixty seconds, no card.
See your free site preview →Related reading: why isn't my website getting me any jobs? · why does my website say "Not Secure"?