Responsive web design means the site rearranges itself to fit the screen: on a phone everything stacks into one column; on a computer it spreads across several. It’s not a separate version of the site; it’s the same site behaving differently.
Why it matters: for most service businesses, the majority of visits come from phones, and in many local trades it’s well over half. If the site looks bad there, it looks bad to most of your customers.
How to check in two minutes
No tools needed:
- Open your site on your phone with Wi-Fi off. Count the seconds until you can read something. More than three, and you’re already losing people.
- Do you have to zoom to read? Bad.
- Can the page slide sideways? Bad: something is wider than the screen.
- Can you tap buttons with your thumb without fear of missing? They should be at least 44 pixels tall.
- Are your phone number and text button visible without scrolling?
Those five points catch almost every real problem.
Responsive isn’t the same as usable
A site can be technically responsive and still be awkward. The cases I see most:
- A menu that swallows the screen with no clear way to close it.
- Wide tables. A five-column pricing table on a phone is unreadable. On mobile it should become stacked cards.
- Heavy images. A 4 MB photo downloads in full even when shown small. The number one cause of slowness.
- Long forms. Seven fields with the keyboard open on a six-inch screen is where people quit.
- Pop-ups that appear after two seconds with a tiny close button.
- 12-pixel text. On a phone, 16 is the comfortable minimum.
Mobile first isn’t a buzzword
Designing for the small screen first forces you to decide what matters, because everything won’t fit. Then, as the screen grows, you add what the extra space allows.
The reverse (design for desktop, then “adapt”) always ends the same way: the desktop site looks good and the phone version is a cramped copy with the important things buried at the bottom.
What Google looks at
Google indexes the mobile version of your site. For ranking purposes, the desktop version barely exists. And for years, speed and visual stability on phones (content not jumping around while loading) have been ranking signals measured with real-user data.
In other words: a site that’s slow on mobile doesn’t just convert worse; it also ranks lower.
What to fix first on an existing site
In order of impact:
- Compress images. The cheapest fix with the biggest effect.
- Increase text size to at least 16 pixels.
- Make call and text buttons sticky at the bottom of the phone screen.
- Cut the form to three fields.
- Remove the two-second pop-up, or delay it.
All five can be done without rebuilding the site. If it’s still slow afterward, the problem is the foundation (a heavy theme or too many plugins), and the decision becomes patch or rebuild. The rest of the checklist is in the 7 elements of a website that sells.
The sites I deliver are built phone-first, with AVIF and WebP images and no pile of plugins. Here’s how, and if you need to know what’s slowing down the site you already have, that’s the strategic audit.