Why your old website looks bad on phones and what to do

Your old website looks bad on phones because it was built for a computer screen of a fixed width, and a phone has to squeeze that whole page into something the size of a playing card. The text shrinks until nobody can read it, the menu turns into a row of tiny links, and photos either spill off the side or shrink to stamps. The fix is not a setting you can switch on. The site needs a layout that rearranges itself for a narrow screen, which almost always means rebuilding the pages.

How websites used to be built

Until the early 2010s, most small-business sites were designed as one picture of a page: a box a set number of pixels wide, centered on the screen, with a menu across the top and two or three columns underneath. The designer chose exact sizes for everything because everyone had roughly the same kind of monitor.

Phones broke that. A phone browser that opens one of those pages has two choices: show it at full size so you scroll sideways, or shrink the whole thing to fit. Most phones shrink it. That is why your homepage on a phone looks like a postage-stamp version of the desktop page.

Modern sites are built "responsive", a word that just means the layout responds to the screen. On a computer you might see three columns; on a phone the same content stacks into one column, with large text and buttons a thumb can hit. That behavior is decided by how the page is built, so it cannot be added on top of an old design.

The six things that go wrong on an old site

Here is what customers actually run into, and why each one happens.

Text too small to read. The page was shrunk to fit, so twelve-point text on a computer becomes something like four-point on a phone. Customers pinch to zoom, lose their place, and give up.
Sideways scrolling. Wide tables, big banners or a fixed-width box push the page past the edge of the screen. Customers drag left and right and miss half of every line.
A menu nobody can tap. Eight links in a row across the top, each the width of a fingernail. People tap "Services" and get "About".
A phone number that is just text. On older sites the number is often typed into the page or, worse, part of an image. On a phone, tapping it does nothing, so the customer has to remember it and dial by hand.
Forms built for a mouse. Small boxes, drop-down menus that open off-screen, and buttons that sit under the keyboard once it pops up.
Things that no longer run at all. Very old sites may use Flash, a format phones never supported. Those sections show up as blank boxes or nothing.

Test your own site in two minutes

You do not need any tools. Take your phone, open your web browser, and type in your address as a customer would.

Can you read the first screen without zooming? If you have to pinch, so do your customers.
Can you tell what you do and where, without scrolling? The first screen should answer that.
Tap your phone number. Does your phone offer to call it?
Open the menu and tap three different pages. Did each tap land where you meant?
Scroll a page from top to bottom. Did anything stick out past the right edge?
Fill in your contact form and send it. Did the message arrive in your inbox?

Then ask someone older than you to try the same on their phone, without help. Watch where they hesitate. That is worth more than any report. For a slower, more thorough version, is your website mobile-friendly? How to check in a minute adds a few more checks, and Google's own PageSpeed Insights will tell you how quickly a phone loads your page.

Why it matters for your business

When a customer finds you on a phone and the site is hard to use, they do not email you to complain. They press back and tap the next business on the list. You never hear about the call you did not get. A site that works on phones does not guarantee calls, but a site that fails on phones turns away people who were ready to call.

Google also checks how a page works on phones, because most searches happen on them. Mobile-friendly websites and Google explains what it looks at. Nobody can promise a position in search results, but a page Google can read easily on a phone is one obstacle removed.

Your options, from smallest to biggest

Patch the old site. If your site is on WordPress or a builder, sometimes a newer theme or template makes it responsive. That works when the site was already fairly modern underneath. On a hand-built site from the 2000s, patching usually costs nearly as much as rebuilding and still leaves odd corners.

Move it to a builder yourself. Wix, Squarespace and others produce phone-friendly layouts. You copy your text and photos over, page by page. This is fine if you have the time and the patience to check every page on a phone.

Have it rebuilt. A designer or a rebuild service takes your existing words and photos and puts them into a layout made for phones first. Ask that every old page address keeps working, so links and Google results still land on the right page.

Whichever route you take, keep what works. The text customers already understand and the photos of your own work usually deserve to move over. What has to change is the frame around them.

What to do this week

Run the six-step phone test above and write down what failed.
Check whether your phone number is a tappable link. If not, that alone is worth fixing now.
Find your logins for the domain and the hosting, so whoever does the work can start.
Look at two competitors' sites on your phone and note what made them easy or hard.

If the words on your site are fine and it is the phone experience that lets you down, you can see your site rebuilt first, open the preview on your own phone, and compare the two side by side.