Responsive design

What it means

Responsive design builds a site so the same page adapts to the width of the screen: on a phone the columns stack, the menu collapses, and the text stays readable without zooming.

It is not a separate mobile version on another address. One page, one URL, one set of content - which is also why a responsive site is better for SEO than two separate ones.

Being responsive is more than shrinking the page. Design also decides the order of content: what sits in a sidebar on a desktop moves below the main text on a phone, or disappears. That is why the mobile view is now often designed first, and why it is a question of UX, not just of code.

How it works in practice

Most visits to company sites and online stores now come from a phone, so mobile is not an extra but the primary view. In practice you check type size, whether buttons are reachable with a thumb, form length and loading speed.

Modern CMS themes are responsive by default; the trouble usually comes from customisations and embedded tables or videos. So after any significant change it is tested on at least one small and one large device.

On a landing page or a service firm’s site, three things decide on mobile: a phone number you can tap, a contact form with as few fields as possible, and a price list that does not fall apart on a narrow screen. Wide tables are therefore rebuilt as cards or scroll sideways inside their own frame.

What to watch out for

Poor mobile rendering costs twice: it lowers conversion and hurts search position, since search engines evaluate the mobile view. Slow loading has the same effect as being unavailable, just less visibly than an uptime failure.

Testing in a narrowed browser window is not enough. A real phone on a slower connection exposes heavy images, content that jumps while loading and buttons hidden under the cookie bar; that is exactly what Core Web Vitals measure, and they feed into how search rates the page.