The first version of every design I ever showed a client was the desktop version. That's how most web designers were taught to work — build the big version, then figure out how it works on mobile.

I stopped doing that years ago. The reason is simple: it consistently produces worse results.

The traffic reality

More than half of web traffic globally is on mobile devices. For small businesses in particular — where social media referrals and Google searches are the primary traffic sources — that number is often 60–70% or higher. Your analytics will tell you exactly what your split is.

This means the experience most of your visitors have is on a small screen, with a thumb, on a connection that may or may not be fast, often while doing something else. Designing primarily for a desktop assumes a user who represents a minority of your traffic.

Why desktop-first consistently goes wrong

When you design for desktop first, every decision gets made in the spacious version. Wide navigation. Large imagery. Side-by-side columns. Generous whitespace. It looks great.

Then the designer or developer translates it to mobile, and the problems surface. The navigation doesn't fit. The columns have to stack, but the order they stack in makes the content confusing. The hero image that looked cinematic at 1440px looks cropped and disconnected at 375px. Text that was readable in a two-column layout is now too long and dense in a single column.

The "responsive" version of a desktop-first design is often just the desktop design with things rearranged to technically fit on a phone. It works in the sense that it doesn't break. It rarely works in the sense of being a good experience.

What mobile-first changes

Starting with mobile forces a hierarchy decision before any visual ones. If you only have room for one thing on the screen, what is it? If someone has to tap twice to find anything, what are the two things that should be immediately visible?

Those constraints produce clarity. The mobile design has to make explicit what the desktop design can leave implicit — because on desktop, you can show everything at once and let the visitor sort it out. On mobile, you can't. The designer has to choose.

When you go from mobile to desktop, you're adding. You have the core experience and you're enhancing it with additional space and context. When you go from desktop to mobile, you're subtracting — and subtraction at the end of a process is more likely to cut something that mattered than addition at the beginning.

The performance connection

Mobile-first design tends to produce more performant sites, for the same reasons. Decisions about what to include get made early under constraint, which means less unnecessary content, fewer large images, tighter code. Page speed matters for SEO and conversion, and the design decisions that produce a good mobile experience tend to support the performance decisions that produce a fast one.

What this looks like in practice

For every new project, the first design deliverable is the mobile layout — the smallest screen, the most constrained version of the experience. We get that right first. Then we design upward: tablet, desktop, wide desktop.

The client review starts with mobile. Not because that's the only thing that matters, but because it's where the experience lives for most of their users, and because the decisions made there will define the quality ceiling for everything else.

If you're starting a web project, ask your designer or developer to show you the mobile design first. If they don't have one, or if the mobile design is visibly an afterthought, that's worth paying attention to.