Responsive web design means building one layout that adapts to whatever screen it lands on, instead of maintaining a separate mobile site alongside the desktop one. It stopped being a competitive advantage a decade ago. It is now the baseline that search engines, customers and your own analytics measure you against, and the useful question has moved from whether to do it to whether it survives contact with real content.
What responsive design actually does
A page that is not responsive squeezes the entire desktop layout into the width of a phone. Text, images and buttons shrink together, so you have to zoom in before you can press anything. Responsive design reflows instead of shrinking. A three-column desktop layout becomes a single column on a phone, navigation collapses behind a menu, and tap targets stay large enough to hit with a thumb.
The mechanism is the breakpoint - a width at which the layout is allowed to rearrange itself. A well-built site has a small number of deliberate breakpoints driven by where the content stops working, not by the screen sizes of whichever devices happened to be popular the year it was designed.
Why it is no longer optional
Google indexes the mobile version of a site rather than the desktop one, so the mobile experience is the version that ranks. Beyond search, a layout that is awkward on a phone loses people before they reach anything you wanted them to see. The cost of getting this wrong is not a penalty applied to you somewhere - it is visitors leaving, which is much harder to see in a report.
Where responsive builds go wrong
Most responsive failures are not layout failures. They are content and performance failures that only show up on a small screen and a slower connection.
The recurring ones: images shipped at desktop dimensions and scaled down in the browser, so a phone downloads several times the data it needs; data tables that have no sensible single-column form; forms that were never tested with an on-screen keyboard covering half the viewport; and content hidden at mobile widths to tidy up the layout, which quietly removes it for the majority of the audience.
Performance is the part that gets least attention and matters most. The One Playground site we built scores 100 out of 100 on Lighthouse best practices, with a 45-second content publish pipeline. That is a result of treating page weight as a design constraint from the start rather than an optimisation pass at the end.
How to tell whether your site is genuinely responsive
Open it on an actual phone rather than by resizing a desktop browser window, on mobile data rather than office wifi. Try to complete the single most important task on the site - book, buy, enquire, find the phone number. If you find yourself zooming, scrolling sideways, or hunting for something you know is on the desktop version, the site is adapted rather than responsive.
What changed since this article was first published
This article originally opened with an ACMA statistic that 94 percent of Australians aged 18 to 34 accessed the internet on a smartphone, and argued that responsive design was an emerging approach worth adopting. Both were fair in 2015. The statistic is now a decade old and the argument has been settled - responsive is the default, and a new site that is not responsive is broken rather than behind. We have replaced the case for adoption with what actually goes wrong in builds we are asked to rescue.