Recommended Free Tools
Build a responsive website by starting with a readable, single-column page in normal document flow, then adding flexible layouts and content-led breakpoints as the available space grows. Set the viewport, make images adapt to their containers, and test at changing widths, zoom levels, and with a keyboard. Responsive design is a way of building, not a separate technology or a set of layouts for particular phone models.
What makes a website responsive?
A responsive page adapts its layout, content, and media to the space and conditions in which it is viewed. HTML text already wraps naturally, but fixed-width containers and rigid columns can defeat that behavior: they may force horizontal scrolling on a phone, squeeze text into narrow columns, or leave a small page marooned in a wide desktop window.
Use the browser’s normal document flow as your foundation. Add CSS Grid or Flexbox to arrange content that can grow, shrink, and wrap. Add media queries only when a real content or usability problem calls for a change. A page that works at intermediate widths, under zoom, and with a keyboard matters more than a layout tuned to a few named devices.
Build from a flexible, narrow-screen baseline
1. Put content in a useful reading order
Write the HTML in the order people should read and navigate it: for example, page heading, main content, related material, then footer. Keep the narrow-screen layout in ordinary document flow so that content remains readable without depending on visual tricks or a wide display. This also gives keyboard navigation a natural source order.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →#1 Best Overall
- HTML CSS Design and Build Web Sites
- Comes with secure packaging
- It can be a gift option
Start with semantic elements and headings that describe the page. A basic document might look like this:
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width">
<title>Example page</title>
<link rel="stylesheet" href="styles.css">
</head>
<body>
<header><h1>Example page</h1></header>
<main class="layout">
<article><h2>Main content</h2><p>...</p></article>
<aside><h2>Related information</h2><p>...</p></aside>
</main>
</body>
</html>Replace the ellipses with actual content; they are shown only to keep the example short. Avoid hard-coding a page’s overall width to a value that cannot fit a narrow viewport. Instead, let the page use available space while constraining it where necessary for comfortable reading.
2. Configure the viewport
Include <meta name="viewport" content="width=device-width"> in the document head. Some narrow devices otherwise use a wider virtual viewport, which can make a page look zoomed out and prevent small-screen CSS rules from responding as expected. initial-scale=1 is common but is usually not necessary; consider it if overflow causes an unwanted initial shrink. Do not disable user zoom.
Use flexible CSS before adding breakpoints
Give the page a fluid foundation. Here is one starting point for the example markup:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
* {
box-sizing: border-box;
}
body {
margin: 0;
font-family: system-ui, sans-serif;
line-height: 1.5;
}
header,
.layout {
width: min(100% - 2rem, 72rem);
margin-inline: auto;
}
.layout {
display: grid;
gap: 1.5rem;
}
img {
max-width: 100%;
height: auto;
}The min() expression lets the content use nearly all the available width on a narrow screen while stopping it from growing without limit on a wide screen. Grid creates a flexible layout, and a single column is a natural starting point. Flexbox is useful for items that should line up or wrap within a row; Grid is useful when content belongs in a larger two-dimensional arrangement. Neither requires a device-specific layout.
Long lines can become tiring to read, so constrain text measures where appropriate rather than stretching paragraphs across a very wide screen. Likewise, avoid fixed-width sidebars or cards that cannot shrink. Let controls and groups wrap when space gets tight, and check that they remain usable rather than merely avoiding overflow.
Add breakpoints when the content needs them
First view the flexible layout at different widths. Add a breakpoint at the point where the content becomes cramped, columns become too narrow, or an arrangement stops making sense—not because a screen is labeled “tablet” or “phone.” Use relative units for breakpoint thresholds so the layout responds to available space rather than assuming a particular device.
For example, the following rule changes the example from one column to two when there is enough room for both sections:
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Rank #3
@media (min-width: 48rem) {
.layout {
grid-template-columns: minmax(0, 2fr) minmax(14rem, 1fr);
align-items: start;
}
}The values here are a starting point for this example, not a universal breakpoint. Resize the actual page and adjust the threshold to the content. The minmax(0, ...) track allows the main column to shrink instead of letting long content force the whole grid wider.
Media queries can respond to more than width. Depending on the design, they can examine viewport height, orientation, resolution, pointer or hover capability, and user preferences. Do not infer device type from width alone: two people viewing at the same width may have different input methods or preferences. Add a condition when it meaningfully improves the experience, not just because it is available.
Make images and other media fit the view
At minimum, prevent an image from overflowing its container with max-width: 100% and preserve its proportions with height: auto. That keeps the image visually within the available space, but it does not by itself choose an efficient file or the best crop for each display.
When the appropriate resolution depends on the display, use srcset and sizes so the browser can select among image candidates. When the desired crop changes for a particular presentation, use <picture> with alternate sources and a fallback image. A single very large image scaled down can waste transferred data; a crop chosen for a wide layout can also make a small-screen subject hard to see. Check both the visual result and the image choice at narrow and wide widths.
Rank #4
- Brand: Wiley
- Set of 2 Volumes
- A handy two-book set that uniquely combines related technologies Highly visual format and accessible language makes these books highly effective learning tools Perfect for beginning web designers and front-end developers
Check zoom, text size, and keyboard order
Responsive work includes people changing how they view a page. Keep zoom available, use text sizing that can adapt, and inspect the page with enlarged text. Look for clipped headings, overlapping labels, controls that become difficult to reach, and content that disappears behind fixed-size elements.
CSS Grid and Flexbox can change the visual placement of items. If you reorder content visually, verify that the HTML source order and keyboard focus order still make sense. Someone tabbing through a page should not encounter controls in a confusing sequence merely because a wide-screen layout moved them visually. Liquid layout is one technique for adapting to available width and text size; it is not a requirement to use one particular CSS recipe.
Test the page at changing widths
- Begin with the narrow view. Confirm that text and controls fit in normal flow, and that no essential content depends on horizontal scrolling.
- Resize gradually. Watch where text becomes difficult to read, controls crowd, or columns become too narrow. Add or adjust a breakpoint at the point that fixes the observed problem.
- Inspect wide and intermediate views. Ensure a layout that works at its breakpoint also remains coherent between that width and a larger screen.
- Test zoom and enlarged text. Check that content remains available and readable rather than clipped or obscured.
- Navigate with a keyboard. Tab through interactive elements and compare the focus sequence with the reading order.
- Check relevant conditions. Try portrait and landscape orientations and, if your design responds to input or user preferences, verify those behaviors too.
- Review media. Check image crop, clarity, and whether the selected image is appropriate at the tested size.
Do not treat a screenshot at one desktop width as proof that the page is responsive. A useful review includes widths between your main layouts, because that is where rigid columns and overly specific breakpoints often show their weaknesses.
Common responsive layout problems and fixes
- The page is tiny on a phone. Check that the viewport metadata is in the document head and that it sets
width=device-width. A wide virtual viewport can make a narrow device render the page as if it had more room. - The page scrolls sideways. Find the element wider than its container, such as a fixed-width column, oversized image, or long unbroken string. Make that content able to shrink, wrap, or fit the available width rather than hiding the symptom by disabling overflow across the whole page.
- Columns become unreadable before the breakpoint. Move the breakpoint to the point where the content needs to stack, or make the columns more flexible. Do not preserve a multi-column layout just because it fits at one named device width.
- Text or controls overlap after zooming. Remove rigid heights and widths where content needs to grow, allow text to wrap, and test the page again with enlarged text. Keep user zoom enabled.
- The image fits but looks wrong. Check whether it needs a different crop at smaller widths. Use responsive source selection when resolution or crop should vary, instead of relying only on scaling the same image.
- Keyboard navigation seems out of sequence. Compare the DOM order with the visual layout. Change the source order where appropriate, or avoid visual reordering that makes focus movement confusing.
Or skip the browser setup
If you need screenshots to review how a page renders at a chosen URL, ScreenshotNeo provides a website screenshot API and MCP server. Its clean-shot options accept cookie or consent banners like a visitor and remove more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each step can be turned off. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and responses identify the page verdict and billing status in headers. AI agents can use its MCP tools to take screenshots, get page information, or capture a PDF.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteOne GET request returns an image or PDF. For a simple capture, use cURL:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com -o shot.webpReplace YOUR_API_KEY with your key and https://example.com with the page to capture. See the ScreenshotNeo API documentation for response formats and capture options. You can also call the API from Python or Node.js:
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://example.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://example.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);The service can capture PNG, JPEG, WebP, or PDF and offers controls including viewport and device presets, full-page or CSS-selector captures, custom CSS and JavaScript, wait conditions, and request blocking. It can help you inspect rendered pages, but a screenshot is not a substitute for testing keyboard order, zoom, text resizing, or responsive behavior across widths.
ScreenshotNeo is at screenshotneo.com. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000. Sign up for the free plan to try it.
Frequently Asked Questions
Do I need a separate page for every screen size?
No. A responsive page uses flexible layout and media that adapt to available space; it does not require a page for each device model.
Can a page be responsive without a media query?
Yes. Flexible content and layout may be enough. Add a media query only when a change in conditions solves a real layout or usability problem.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
