Responsive design

One site that rearranges, not two that drift apart

Before this was normal, plenty of businesses ran two websites: the real one, and a stripped down mobile version at its own address. Two sets of pages, two sets of edits, and the mobile one always fell behind. The new service never got added to it. The phone number stayed wrong for a year.

Responsive keeps one set of pages and lets the layout move instead. Three columns on a monitor stack into one on a phone. The menu folds into a button. Images scale to the width they are given. Tap targets grow to the size of a thumb. The words and the photos are the same words and photos either way, which is the point: fix your service description once and it is fixed on every screen.

Say you have a page with an estimate form beside a photo of a finished job. On a laptop they sit side by side. On a phone the photo goes on top, the form goes underneath, the fields run the full width, and the phone number becomes a button somebody taps rather than a string they have to copy.

The phone layout is the version that gets graded

People look for a plumber, a dentist, or a tow truck on the device already in their hand, usually while standing in the room with the problem. That is the layout your business gets judged on, by the customer and by the search engine both: under mobile-first indexing engines rank from the mobile version of a page, so the phone view is not a courtesy copy of your website. It is the website.

Responsive is the floor, though, not the finish. A page can technically fit a phone and still be miserable: text set too small to read at arm's length, links crowded close enough to mis-tap, a form asking fifteen questions, a full height photo that shoves everything useful out of sight. Designing for the small screen first and letting it grow tends to produce a better page than shrinking a desktop layout down. Every site we build starts that way, which is part of what custom web design covers.

The test that counts is not dragging your browser window narrower. Hand your phone to somebody who has never seen the site and ask them to book a job, one handed, outdoors, on a connection that is not your office wifi. One job board we built for a Philadelphia staffing agency lives that way in practice: the owner posts her openings from her phone.

Fitting the screen and feeling fast are separate jobs

A responsive page can still be slow, and slow is its own complaint. Layout decides where things sit. Page speed decides how long they take to arrive, and cumulative layout shift covers the particular irritation of content jumping as late images load, so you tap the wrong thing.

The closest neighbor is above the fold. Responsive rules decide how your first screen reshuffles on a phone, and that reshuffling is exactly what pushes your phone number and your booking button up into view or down out of it. None of this is a switch somebody flips later. It is decided while the page is being built.