What is responsive web design? How it works, the standards behind it, and common mistakes

Responsive web design lets a single website rearrange itself automatically for phones, tablets, and desktops. It isn't a shrunken desktop website. It's a deliberate decision, made for every screen width, about what comes first.

Responsive web design (RWD) is an approach in which a website has a single URL and a single set of content, and its layout automatically rearranges itself to fit the screen width of whatever device it's viewed on. Three cards that sit side by side on a desktop stack vertically on a phone, and text, images, and buttons resize so they're comfortable to read and tap at that size. For any new website built in 2026, responsive design is a baseline requirement, not an add-on, and Google explicitly recommends this approach (Google Search Central, mobile-first indexing guide).

This article explains how responsive design works, which parts are official standards and which are just industry conventions, and the mistakes we see most often on mobile. If you're working out a budget, start with how to read a web design quote. If you already have a website and only the mobile version is the problem, read redesign or rebuild first. To see how we approach custom layouts, see custom web design.

Responsive design rests on three techniques: fluid grids, flexible images, and media queries

The technical core of responsive design comes down to three ideas, plus one line of code that tells mobile browsers to use the actual screen width. The term comes from a 2010 article by web designer Ethan Marcotte, which broke the approach down into these three ingredients (A List Apart, Responsive Web Design).

  • Fluid grids let columns follow the screen. A fluid grid sizes columns in proportions instead of fixed pixels, so the layout fills the screen at any width instead of spilling off the edge of a phone.
  • Flexible images never break the layout. Images are capped at the width of their container, so they shrink along with the screen instead of forcing a horizontal scrollbar across the page.
  • Media queries decide when the layout changes. A media query is a CSS rule that applies different styles at different screen widths, for example, "below this width, switch from three columns to one." That switching point is what designers call a breakpoint.
  • The viewport setting makes phones use their actual width. Without it, some mobile browsers lay out the page on a virtual canvas about 980px wide and then shrink the whole thing down, which means styles written for small screens never take effect (MDN Web Docs, viewport meta reference).

Industry terms and official standards aren't the same thing

"Responsive web design" itself is an industry term, not a specification issued by any standards body. The only places with hard numbers are Google's search documentation and the W3C's accessibility standard. Most of the rest is just how design teams usually work.

Term What it is What it says Source
Responsive web design Industry term Fluid grids, flexible images, media queries A List Apart, Ethan Marcotte (2010)
Breakpoints Industry convention No fixed values; chosen based on content and layout No official standard
Mobile-first indexing How Google Search works Google indexes and ranks the mobile version of your content Google Search Central
Reflow W3C accessibility standard WCAG 2.2, Level AA At a width equivalent to 320 CSS px, content is fully usable without scrolling in two directions W3C, WCAG 2.2 Success Criterion 1.4.10
Minimum target size W3C accessibility standard WCAG 2.2, Level AA Buttons and other tap targets are at least 24×24 CSS px, with exceptions such as adequate spacing W3C, WCAG 2.2 Success Criterion 2.5.8
Viewport setting Browser behavior width=device-width lays out the page at the device's actual width MDN Web Docs

WCAG (Web Content Accessibility Guidelines) is the international accessibility standard published by the W3C. The 320 CSS px figure is equivalent to a 1280px-wide window zoomed to 400%, a real-world scenario for people with low vision (W3C, Understanding SC 1.4.10 Reflow).

Google lists three ways to build a mobile website and recommends responsive design

Google describes three mobile configurations and says responsive design is the easiest to implement and maintain (Google Search Central, mobile-first indexing guide).

Approach URLs Content maintenance When it fits
Responsive design One URL One set of content, in sync across every device Almost all corporate websites, brand websites, and one-page websites
Dynamic serving One URL The same URL returns different HTML for each device, so there are two templates to maintain Mobile and desktop layouts differ radically, and there are engineers available to maintain both
Separate mobile URLs Two URLs (for example, an m. subdomain) Two websites, plus URL mapping between them Mostly legacy setups; rarely chosen for new websites

Why responsive is the default: Google indexes the mobile version

Google builds its index and rankings from the mobile version of your website, so whatever is on your mobile website is what Google sees.

  • As far as Google is concerned, your mobile website is your website. Google crawls with a smartphone crawler and uses that version of the content for indexing and ranking (Google Search Central, mobile-first indexing guide).
  • Content hidden on mobile isn't indexed. Google explicitly states that only content shown on the mobile website is used for indexing, and suggests placing content in accordions or tabs instead of removing it (Google Search Central, mobile-first indexing guide).
  • One URL keeps things simple. Shared links, links from other websites, and search results all point to the same page, with no desktop-to-mobile URL mapping to manage.
  • Only one set of content to maintain. Update it once and every device stays in sync, instead of editing two separate websites as people used to.

To be clear, going responsive doesn't make your rankings rise on its own. It's a baseline: an incomplete or hard-to-use mobile version is what puts a website at a disadvantage.

Responsive design isn't a shrunken desktop website. It's deciding what comes first

A good responsive website rethinks the order of information at every breakpoint. On a desktop, things sit side by side; on a phone, they line up in a single column. Deciding what goes first in that line is a design decision that shouldn't be left to the code.

One set of content: fluid grid, flexible images, media queriesPhoneOne columnTitleImageTextContactTabletTwo columnsTitleImageTextContactDesktopSeveral columnsTitleImageTextContact
One set of content: fluid grid, flexible images,media queriesPhoneOne columnTitleImageTextContactTabletTwo columnsTitleImageTextContactDesktopSeveral columnsTitleImageTextContact
Figure 1. The same content laid out for phone, tablet, and desktop, with the phone order decided first

These are the things we check, one by one, during design:

  • The first mobile screen carries the single most important thing. A small screen shows only a small slice at a time, so what visitors need most (what you do, how to reach you) has to appear first.
  • Navigation works with one hand. Once the menu collapses, important pages should still be no more than two taps away.
  • Buttons are large enough and spaced far enough apart. Buttons that are too small or too crowded cause mis-taps. The WCAG figure of 24×24 CSS px is a minimum, and primary buttons are usually larger.
  • Images and code are slimmed down for mobile networks. Phones are often on cellular data, and serving images sized to the screen noticeably reduces waiting time.
  • Forms aren't hidden by the keyboard. When the on-screen keyboard pops up, the input field and the submit button still need to be visible.

Most of these problems don't show up when you simply narrow a desktop browser window. They have to be checked on real phones.

The five most common mobile mistakes

Most mobile problems aren't difficult technical problems. They come from designing only for the desktop.

  • Horizontal scrolling. Usually caused by fixed-width tables, oversized images, or elements that overflow their container. The WCAG reflow criterion uses a 320 CSS px width with no sideways scrolling as its benchmark.
  • Text that's too small. Small type that looks refined on a desktop makes people squint on a phone, so body text needs its own mobile font size and line height.
  • Content hidden on mobile. Hiding important sections to make the layout look cleaner hurts both visitors and search indexing.
  • Text inside images. Words in an image shrink with the image and can't be read by search engines. Headings and key points should be real text.
  • Testing only in an emulator. Browser device emulation is fine for a first pass, but real phones handle fonts, scrolling, and keyboards differently. Check on actual devices before launch.

Case study For Punto Gelato, we checked every width from 320 to 1440 px, with the menu going from four columns to two to one and no horizontal scrolling anywhere

When responsive design alone isn't the answer

Responsive design suits almost every website, but in a few situations, it isn't enough on its own, or a fully refined mobile layout isn't worth the effort.

  • Services that need the camera, push notifications, or offline use. These usually call for an app. A responsive website can serve as the entry point, but it can't replace app features.
  • Internal tools used only on fixed screens. For a CMS admin panel used only on office desktops, it's enough to make sure it's readable and doesn't break on a phone, without refining the layout for every screen size.
  • Old websites laid out with fixed-width tables. Retrofitting them to be responsive often takes longer than rebuilding, so it's worth weighing redesign or rebuild first.

FAQ

What is the difference between a responsive website and an app?

A responsive website opens in the browser and works on every device from a single URL, with nothing to download. An app is installed from an app store and can use phone features such as the camera, push notifications, and offline mode, but it costs more to build and maintain. For most corporate websites, a responsive website is all you need.

How can I tell whether my website is responsive?

The quickest check is to open it on your phone and see whether you have to pinch to zoom or swipe sideways to read it. You can also narrow your desktop browser window and watch whether the layout changes from several columns to one. After that, we still recommend walking through your main pages and forms on a real phone.

How many breakpoints should a website have?

There's no right answer. Breakpoints are an industry convention, not an official rule. The common practice is to let the content decide, adding a breakpoint wherever the layout starts to feel cramped or too sparse, instead of targeting specific phone models.

Does responsive design cost extra?

Responsive design should already be part of the design and development scope. When you compare quotes, check whether mobile and tablet layouts are designed and whether testing on real devices is included. At 留白設計 BLANK DESIGN, one-page websites start at NT$80,000 and brand websites at NT$180,000, and both are designed and checked at phone, tablet, and desktop sizes. For how quotes are structured, see how to read a web design quote.

What to prepare

Having these ready before you get in touch makes the first conversation more productive:

  • Your current website address. If you already have a website, we can check its mobile problems on real devices first.
  • Your split between mobile and desktop traffic. If you have analytics installed, this figure helps set design priorities.
  • Screenshots of the pages that are hardest to use on a phone. Problems that you or your customers have actually run into are more concrete than any checklist.
  • What you want visitors to do on a phone. For example, call you, add you on LINE, fill out a form, or make a booking.
  • Brand assets. Your logo, brand colors, photos, and copy, as much as you have.

When you're ready, tell us about your situation through a free consultation, and we'll explain the approach and timeline that fit your needs.

References

  1. Understanding SC 1.4.10 Refloww3.org
  2. mobile-first indexing guidedevelopers.google.com

More to read