Responsive Web Design: How It Works and How to Test It
Responsive web design is one page whose layout adapts to any screen, from a small phone to a wide monitor, and Portland Peak SEO builds every site this way. Three techniques do the work: fluid grids, flexible images and CSS media queries. A viewport meta tag tells phones to use their real width, and builds start at $2,200.
Written and maintained by Andreas Benavente, Founder, Portland Peak SEO · Updated October 31, 2026
Rated 5.0 out of 5 on Google from 4 reviews (Google Business Profile, read October 20, 2026)
VIEWPORT · MEDIA QUERIES · WCAG REFLOW · MOBILE-FIRST INDEXINGResponsive web design: key takeaways
- ✓ One URL and one HTML document serve every device, while CSS changes the layout.
- ✓ Responsive web design began in 2010, and today CSS grid and flexbox do most of the work.
- ✓ Google indexes the mobile version of a site, since that switch finished in October 2023.
- ✓ WCAG 2.2 asks for pages that still work at 320 CSS pixels wide, without two-way scrolling.
- ✓ Good Core Web Vitals: LCP within 2.5 s, INP at 200 ms or less, CLS at 0.1 or less.
- ✓ Test real widths, zoom and a real phone, because the Mobile-Friendly Test is gone.
What is responsive web design?
Responsive web design, named by Ethan Marcotte on May 25, 2010, lets one HTML page fit any screen. He listed three ingredients, namely fluid grids, flexible images and media queries. MDN still teaches it as an approach rather than a separate technology.
Before it, many businesses ran a second site for phones, often on an m-dot subdomain. That meant two sets of pages and links, so the two versions drifted apart. A responsive page drops the second site, because the same HTML reaches every device while CSS decides the layout.
Read the original in Marcotte's 2010 article, then the current techniques in MDN's responsive design guide. Both sources agree on the core idea: design for the content first, then let the screen decide the arrangement.
How does responsive web design work?
Responsive web design works through 4 parts: a viewport meta tag, flexible layouts, media queries and responsive images. The viewport tag sets the layout width to the device. Grid and flexbox then fill the space that exists. Media queries change the layout at chosen widths, while responsive images fit the file to the screen.
The viewport meta tag
One line in the page head does it: <meta name="viewport" content="width=device-width, initial-scale=1">. According to MDN's viewport reference, some phones otherwise render a 980-pixel virtual viewport and then shrink the result. MDN now lists width=device-width alone as its recommended setting, whereas web.dev's basics guide also adds the initial scale.
Fluid layouts with grid and flexbox
Modern CSS layout bends by default, unless fixed widths get in the way. A grid rule such as repeat(auto-fit, minmax(14rem, 1fr)) fits as many columns as the space allows, even without a breakpoint. Widths in percentages, rem or fr units stretch and shrink, whereas fixed pixel widths force sideways scrolling.
Media queries and breakpoints
A media query applies CSS only while a condition holds, such as a minimum width. MDN's media query guide shows the newer range syntax, for example @media (width >= 48rem). Mobile-first code writes the narrow layout first, then adds columns when width grows. Place breakpoints where the content breaks rather than at device names, as web.dev also advises.
Flexible and responsive images
Flexible images come first, because one oversized photo can push a whole page sideways. Setting max-width: 100% on img, picture and video elements keeps media inside its container at any width. MDN's responsive design guide uses that exact rule.
The srcset and sizes attributes list several files, and they also tell the browser how wide the image will display. The browser then picks a file that suits the screen, as MDN's responsive images guide explains. The picture element handles art direction, for example a tighter crop on phones.
What does a responsive layout look like in practice?
The box below holds 6 cards laid out by one CSS grid rule, rather than any media query. Drag its lower right corner to narrow it, and the cards wrap into fewer columns, then into one. On a phone, turn the screen sideways instead and watch the columns change.
The rule behind it: grid-template-columns: repeat(auto-fit, minmax(min(9rem, 100%), 1fr)). Keyboard users get the same effect by zooming the browser, because zoom narrows the layout width in CSS pixels.
Every table on this page also shows the reverse trick. Below 640 pixels wide, each row stacks into labeled lines, so no column hides off-screen.
How does responsive web design compare with adaptive design and separate mobile sites?
Google documents 3 setups for phones: responsive design, dynamic serving and separate URLs. It recommends responsive web design, because it is the easiest pattern to implement and maintain. Adaptive design usually means dynamic serving, when the server detects the device and sends different HTML. Separate URLs, by contrast, run a second mobile site with redirects between versions.
| Setup | URL and HTML | What must stay in sync | Usually fits |
|---|---|---|---|
| Responsive design | One URL and the same HTML for every device, while CSS changes the layout | Nothing extra, since only one version exists | Almost every business site, especially one that changes often |
| Dynamic serving (adaptive) | One URL, but different HTML chosen by user agent, with a Vary header | Content, structured data, titles and alt text, including every template pair | Apps, when phone features differ sharply |
| Separate URLs (m-dot) | Two URLs per page, so each page has two HTML files | Every page pair, including the redirects between them | Older sites, until a migration finishes |
The parity rules in Google's mobile-first indexing guide apply whenever a site uses the second or third setup. They ask for the same content and structured data, including equivalent titles, descriptions and image alt text. A responsive page meets all of them by default, because there is nothing to compare.
Why does responsive web design matter for Google search?
Google declared mobile-first indexing complete on October 31, 2023, so it ranks the mobile version of a site. It also crawls that version with its smartphone agent. Anything missing from the phone version is therefore missing from what Google indexes. A responsive page avoids that, because it sends both audiences the same content.
Content that loads only after a tap is the real risk. Google's guide says it won't load content that stays hidden until someone swipes, clicks or types. Keep primary content in the HTML from the first load, and then read the October 2023 announcement for the history.
Speed also sits beside this. Google's Core Web Vitals page says good scores align with what its core ranking systems seek to reward. It stops short of promising any position, and so should any designer. Our technical SEO service covers the crawl side, while the on-page SEO guide covers the words.
How much of Portland Peak SEO’s own search traffic comes from phones?
Phones sent 25.5% of the Google search clicks to portlandpeakseo.com from June 6 to September 5, 2026. Desktop sent 74.5%, while tablets sent none. Our buyers choose services for their businesses, so desktop still leads, and a responsive site has to serve both. Source: our Search Console device export for that 92-day window.
We count clicks rather than impressions, because a click needs a person behind it. The split also says to test the desktop layout as hard as the phone, especially at 1280 pixels.
A consumer business will often see the opposite split, so read your own device report before you set priorities. In Search Console, open Performance, then the Devices tab, for the same comparison.
Which WCAG 2.2 rules apply to responsive web design?
WCAG 2.2 sets 2 Level AA criteria that shape every responsive layout. Reflow, criterion 1.4.10, asks that content still work at 320 CSS pixels wide without scrolling in two directions. Target Size (Minimum), criterion 2.5.8, asks for pointer targets of at least 24 by 24 CSS pixels. Spacing and a few other exceptions also apply.
| Criterion | What it asks | How to build for it |
|---|---|---|
| 1.4.10 Reflow (AA) | Nothing lost at 320 CSS px wide, or at 256 CSS px tall when content scrolls sideways | Relative widths, wrapping text and tables that restack before they overflow |
| 2.5.8 Target Size (Minimum) (AA) | Pointer targets at least 24 by 24 CSS px, unless spacing keeps them apart | Padding on links and buttons, especially in menus |
| Zoom in the viewport tag | At least 2x scaling, per MDN's note on WCAG, while MDN suggests allowing 5x | Never set user-scalable=no, since it blocks zoom |
Why 320? The W3C's Understanding Reflow page explains that 320 CSS pixels equals a 1280-pixel desktop window at 400% zoom. A reflow test therefore doubles as a zoom test for readers with low vision. Maps, diagrams, video, games and data tables may need two-dimensional layout, so the criterion exempts them.
The Target Size (Minimum) explainer lists the exceptions, including inline links inside a sentence. Both criteria also sit in WCAG 2.2, the current W3C recommendation.
How fast should a responsive web design load on a phone?
Aim for 3 good Core Web Vitals thresholds at the 75th percentile of page loads. Track mobile and desktop apart, since they often differ. Largest Contentful Paint should land within 2.5 seconds, while Interaction to Next Paint stays at 200 milliseconds or less. Layout shift should also stay at 0.1 or less.
| Metric | What it measures | Good | A common responsive cause of failure |
|---|---|---|---|
| LCP | When the largest element finishes loading | 2.5 seconds or less | A desktop-sized hero image, especially on slow phones |
| INP | How fast the page responds when someone taps or types | 200 ms or less | Heavy scripts, especially behind sliders and menus |
| CLS | How much the layout jumps during loading | 0.1 or less | Images and embeds, when they lack width and height |
These figures, including the 75th percentile rule, come from web.dev's Web Vitals article. It also records INP becoming a stable Core Web Vital in 2024. Keep width and height on every image, because the browser can then reserve space before the file arrives. Our Core Web Vitals optimization page also covers fixes for existing sites.
How fast do Portland Peak SEO’s own pages load on a phone?
12 of our 16 rebuilt pages reached Largest Contentful Paint within 2.5 seconds on a throttled phone. The median was 2.4 seconds. None of the 16 scrolled sideways at 320 pixels. Each page loaded 3 times, with 4x CPU slowdown and 150 ms network latency during every load. Source: our lab test of October 20, 2026, not Google field data.
Lab numbers suit comparison between builds, because every page faces the same conditions. Field data from real visitors decides the Core Web Vitals assessment, so treat this test as an early warning.
The profile used 150 ms latency, 1.6 Mbps down, 750 kbps up and a 4x slower processor. We took the median of 3 completed loads per page with the cache off, since single loads vary. We reran any load the browser cut off, and we measured 6 pages again later that day. The raw files keep every attempt.
How do you test responsive web design before launch?
Run 6 tests before launch: a width sweep, 400% zoom, tap targets, a real phone, the Googlebot view and speed. A narrowed desktop window misses keyboards and slow networks, so it cannot stand alone. Google retired its Mobile-Friendly Test on December 1, 2023, so no single pass or fail verdict remains.
| Test | How to run it | Pass mark |
|---|---|---|
| Width sweep | Device mode in Chrome DevTools at 320, 375, 768, 1024 and 1280 CSS px, then drag between them | No sideways scrolling, unless a data table needs it |
| 400% zoom | A desktop window at 1280 px wide, when browser zoom sits at 400% | The same as 320 px, so every control stays reachable |
| Tap targets | Inspect links, buttons and form fields, especially in menus | At least 24 by 24 CSS px, unless spaced apart |
| Real phone | Fill in every form while the on-screen keyboard is open | Fields stay visible while you type, and submit works |
| Googlebot view | URL Inspection in Search Console after launch | The rendered page shows the full content, including tables |
| Speed | Lighthouse in the lab, then field data once real visits build up | LCP, INP and CLS in the good range, especially on phones |
These tests catch common faults, for example a fixed-width video, a hover-only menu or a banner over a button. Google's note on the retired Mobile-Friendly Test also gives the retirement date.
How did page one for responsive web design score on a 320-pixel test?
1 of 8 results on page one for responsive web design scrolled sideways at 320 CSS pixels, by 10 pixels. All 8, however, set a device-width viewport tag. A US web search returned 10 results, but 1 refused our test browser and 1 redirected to another result. Source: our 320-pixel phone test, run October 20, 2026.
| Measure | Result | How we measured it |
|---|---|---|
| Results loaded and distinct | 8 of 10 | 1 refused the connection, while 1 redirected to a page already in the list |
| Viewport set to device width on a phone | 8 of 8 | The viewport meta tag, read from the loaded page |
| Sideways scrolling at 320 CSS px | 1 of 8, by 10 CSS px | Document scroll width compared with the 320 px window |
| This page, same test | No sideways scrolling | Re-run on this build before release |
Method: Playwright with Chromium, an iPhone user agent, touch enabled and a 320 by 640 window. Each page loaded in a fresh browser, then waited four seconds before the reading. We report totals only, because the pattern matters rather than any one site.
The lesson is small but real. Still, a 10-pixel overflow fails reflow on its own. That is why the test runs on every template, not only the homepage.
What does responsive web design cost with Portland Peak SEO?
Every build is responsive, and Portland Peak SEO publishes 3 one-time prices: Starter $2,200, Growth $4,500 and Authority $8,500. The layout work sits inside the build price, and the scope comes in writing before work starts. Monthly SEO stays separate, so you can add it later at $450, $950 or $2,500, month to month.
STARTER
Five to eight pages for one shop or office with one core service, live in four to five weeks.
Get a Starter quoteGROWTH
Ten to 25 pages for a firm with several services or service areas, usually live in five to eight weeks.
Get a Growth quoteAUTHORITY
Thirty pages or more for multi-location and regional businesses, with the timeline set in the written scope.
Get an Authority quoteHosting and the domain sit outside these prices, since you may keep your own provider. The pricing page lists every tier, while the web design cost guide explains what moves a quote.
For the service itself, start at web design in Portland, Oregon, especially if you are nearby. Then pick the build that fits: custom website design, WordPress website design, small business websites or ecommerce design.
An older site that only needs a new layout may suit a website redesign instead. The web design process page shows each step before you commit.
Who builds responsive websites at Portland Peak SEO?
Andreas Benavente has led Portland Peak SEO since 2015 and writes the code, from Lake Oswego, Oregon. Builds are hand-coded pages or WordPress, depending on whether your team edits often. A free quote arrives with a recorded video review, and a free mockup shows the design before you commit.

| Client site | Platform and size | What to check on your phone |
|---|---|---|
| The Manhattan Group International | Hand-coded HTML and CSS homepage, eight versions | The field photo gallery and video, especially at phone width |
| PDX Elevator Safety | 27 pages on WordPress.com, launched in three waves | Inspection pages for two states, so each state has its own pages |
| Blue Heron Services | A 43-page launch on WordPress with Elementor | Each service page and its contact path, including the phone link |

Each named site and its scope also appear on the clients and case studies page. Read more about the founder, ask for a free website mockup, or request a free web design quote.
Which sources does this responsive web design guide rely on?
This guide links 18 primary sources, so every technical claim points to the body that sets the rule. That means the W3C for accessibility, while MDN covers HTML and CSS. Web.dev and Google Search Central cover performance and indexing, while Marcotte’s 2010 article covers the history.
- Ethan Marcotte, Responsive Web Design, A List Apart, May 25, 2010
- MDN, Responsive web design · viewport meta · using media queries · responsive images · container queries
- W3C, Understanding 1.4.10 Reflow · Understanding 2.5.8 Target Size (Minimum) · WCAG 2.2
- Google Search Central, mobile-first indexing best practices · Mobile-first indexing has landed, October 31, 2023
- Google Search Central, Core Web Vitals · Mobile-Friendly Test retirement · URL Inspection tool
- web.dev, Web Vitals · Responsive web design basics · Chrome DevTools device mode · Lighthouse
Cite this page
Benavente, A. (2026, October 20). Responsive web design: how it works and how to test it. Portland Peak SEO. https://portlandpeakseo.com/responsive-web-design/
For structured data on a new build, see the schema markup guide.
What do Google reviews say about the firm behind this responsive web design guide?
Our Google Business Profile showed a 5.0 rating from 4 Google reviews when we read it on October 23, 2026. Two of those reviews appear below word for word, one from Michael Richardson of MGI, a construction and environmental services firm, and one from Jacob Levin of Jacob Levin Law, a law firm in Redding, California, with each reviewer's name as Google shows it. Both mention the websites. Every review, and the current count, is also on our Google Business Profile.
★★★★★
“5 star service. Whenever we need changes on our website Andreas calls us back Immediately. The AI skills are top notch. They made our website stand out and get noticed.”
★★★★★
“Andreas is a wizard with rankings. His websites are amazing, his communication is superb. Cannot recommend enough.”
These are clients' own words, so we have not edited them. One client's experience, however, does not predict another's.
Questions about responsive web design
The basics: what responsive design means
What is a responsive design?
A responsive design is a layout that rearranges itself to fit the space it gets. On the web, the same HTML fits phones, tablets and desktops. For example, a three-column product grid on a laptop becomes a single column on a phone. The words, images and links stay the same.
Is responsive web design the same as mobile-friendly design?
Not quite. Mobile-friendly describes a result, namely a page that reads and works well on a phone. Responsive web design is one route to that result, because a single page serves every screen. A separate mobile site can be mobile-friendly too, although it doubles the pages to maintain.
What is the difference between responsive and mobile-first design?
Responsive describes what the finished page does across screens, whereas mobile-first describes the order of work. Base styles target small screens first, and later rules add columns as space grows. Most responsive builds today start mobile-first, since adding layout is simpler than removing it.
Mobile sites, the viewport tag and core principles
Do I still need a separate mobile website?
Rarely. Google still supports separate mobile URLs, although its own documentation favors responsive design as easier to run. Two sites mean two sets of content, redirects and markup, so both need constant checks. One responsive site, instead, removes that whole class of mismatch.
What does the viewport meta tag do?
It tells a phone browser to use the width of the device, rather than a desktop width. Without it, many phones draw the page on a wider virtual canvas, then shrink the result to fit. Text turns tiny, so the reader has to pinch and zoom before reading anything.
What are the key principles of web design?
For a site that must work on every screen, five principles carry most of the weight. Put the content first, then let a fluid layout arrange it. Keep text readable and controls at least 24 by 24 CSS pixels. Load fast, so the main content shows within 2.5 seconds on a phone. Finally, give every visitor one URL and the same content.
Making an existing site responsive
Can an existing website become responsive without a rebuild?
Sometimes. A site on a modern theme often needs targeted fixes, including fixed widths, oversized images and cramped buttons. An old table layout or a separate mobile site usually costs more to patch than to replace. A free quote review then tells you which case applies to your site.
Are WordPress themes responsive by default?
Most current themes ship with responsive layouts, but plugins, page builders and custom code can break them. For example, one slider with fixed pixel widths can cause sideways scrolling on a phone. Test the finished pages, especially forms, rather than the theme demo.
Is Wix responsive design?
It depends on the editor. The Wix help center says its Studio Editor builds fully responsive sites, with breakpoints you can adjust. The classic Wix Editor instead creates a mobile version from the desktop design. Design changes made on that mobile view do not affect the desktop version, so it behaves like a second layout. Test any Wix site at several widths before launch.
Container queries and testing tools
What are container queries in CSS?
Container queries let a component respond to the width of the box around it rather than the whole window. You declare a container with the container-type property, then write rules inside an @container block. A product card can then stack in a sidebar while it spreads out in the main column.
What replaced the Google Mobile-Friendly Test?
Nothing replaced it one for one. Lighthouse in Chrome runs lab checks, while Search Console’s URL Inspection shows how Googlebot renders a live page. Pair both with a real phone, because neither tool fills in your forms with a thumb.
Cost and working with us
Is a mobile layout an add-on to the build price?
No. Responsive layout comes with every build, so no separate mobile line appears on the quote. You pay the published build price instead: $2,200 for Starter, $4,500 for Growth or $8,500 for Authority, one time.
Can a business outside Portland hire you for a responsive website?
Yes. The studio works from Lake Oswego, Oregon, for clients across the Portland metro and in other states. Work runs by email and video, with calls when a decision needs one. Every client gets the same published prices and a written scope before work starts.
How do I find out whether my site passes on a phone?
Send your address through the free web design quote form. You get a recorded video review from Andreas Benavente, plus a fixed price if a rebuild makes sense. You sign nothing until you approve a written proposal.
More web design guides and services
Find out how your site does on a phone
Send your current address, or a note if you have no site yet. You get a recorded video review and a fixed price, with nothing to sign.