Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Make a website responsive by starting with a fluid, single-column layout, allowing content to shrink and grow, and adding Flexbox, Grid, or media queries only when the content needs a different arrangement. Keep images inside their containers, declare the mobile viewport, and test continuously at narrow and wide widths. Responsiveness is a layout strategy—not a separate stylesheet for every phone.
What responsive CSS actually means
Responsive design makes one page adapt to the space and conditions available to it. A narrow phone, a wide desktop monitor, a zoomed browser, a touch device, and a user who prefers less motion can all receive an appropriate presentation from the same HTML and CSS.
The strongest foundation is flexible content. Fixed-width page wrappers often create horizontal scrolling on small screens and excessive empty space on large ones. Normal document flow, relative units, Flexbox, and Grid solve many changes without a media query. Add a query only when the content needs a genuinely different treatment.
Start with a fluid, narrow-screen baseline
Write the smallest useful layout first. Let text wrap naturally, let blocks fill the available width, and avoid locking the page to a wide pixel value.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
#1 Best Overall
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>Responsive page</title>
<link rel="stylesheet" href="styles.css">
</head>
<body>
<main class="page">
<h1>Project dashboard</h1>
<div class="content-grid">
<article>Main content</article>
<aside>Related information</aside>
</div>
</main>
</body>
</html>*,
*::before,
*::after {
box-sizing: border-box;
}
body {
margin: 0;
font-family: system-ui, sans-serif;
line-height: 1.5;
}
.page {
width: min(100% - 2rem, 70rem);
margin-inline: auto;
}
.content-grid {
display: grid;
grid-template-columns: 1fr;
gap: 1.5rem;
}
img,
picture,
video {
max-width: 100%;
height: auto;
}box-sizing: border-box keeps padding and borders inside declared dimensions. The min() expression leaves a one-rem gutter on each side while capping the reading area on wide screens. The viewport declaration tells mobile browsers to use the device width instead of laying the page out on a much wider desktop-like canvas and shrinking it.
Choose the layout method that matches the content
| Method | Use it when | Responsive behavior |
|---|---|---|
| Normal flow | Content is primarily a vertical sequence | Blocks naturally expand to available width and wrap |
| Flexbox | Items form one row or column, such as navigation or a toolbar | Items can grow, shrink, wrap, and redistribute free space |
| Grid | You need rows and columns or a page-level arrangement | Flexible tracks can add or remove columns as space permits |
Flexbox for a wrapping navigation
.nav-list {
display: flex;
flex-wrap: wrap;
gap: .75rem 1rem;
padding: 0;
margin: 0;
list-style: none;
}
.nav-list a {
display: block;
padding: .5rem .75rem;
}This lets links move to another line rather than forcing a horizontal scrollbar. If the links become hard to scan, change the arrangement at a content-driven breakpoint instead of adding a query for every device model.
Grid for cards that fill available space
.cards {
display: grid;
grid-template-columns: repeat(auto-fit, minmax(min(100%, 16rem), 1fr));
gap: 1rem;
}auto-fit creates as many tracks as fit; minmax() prevents a card from becoming unusably narrow while allowing it to grow. This intrinsic behavior may eliminate a media query entirely.
Add breakpoints where the design starts to fail
Resize the page gradually. Note the exact point where a navigation row wraps awkwardly, a paragraph becomes too wide, controls collide, or a two-column layout leaves one column cramped. Put the breakpoint there. Breakpoints describe content needs, not a universal list of phone, tablet, and desktop widths. Relative units such as rem are preferable to device-specific pixel assumptions.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitches@media (width >= 48rem) {
.content-grid {
grid-template-columns: minmax(0, 2fr) minmax(14rem, 1fr);
}
}The value above is illustrative; your text measure, controls, and sidebar determine the appropriate threshold. A mobile-first stylesheet keeps the base rules usable when a query is unavailable or the viewport is very narrow.
Use queries for more than width
Media queries can respond to environment features and user preferences, not only viewport width. For example, reduced-motion support should make nonessential animation shorter or absent for people who request less motion.
@media (prefers-reduced-motion: reduce) {
*,
*::before,
*::after {
scroll-behavior: auto;
animation-duration: 0.01ms;
animation-iteration-count: 1;
transition-duration: 0.01ms;
}
}This is an accessibility adaptation, not a requirement to remove every visual transition for every user. Preserve essential feedback while avoiding decorative movement.
Make images and video fit without wasting downloads
max-width: 100% prevents an image or video from escaping its containing block. height: auto preserves its intrinsic ratio. This solves overflow, but CSS scaling does not choose a more efficient source file. If a phone should download a smaller image, or a banner needs a different crop, use responsive image HTML.
<img
src="photo-1200.jpg"
srcset="photo-480.jpg 480w, photo-800.jpg 800w, photo-1200.jpg 1200w"
sizes="(width >= 48rem) 50vw, 100vw"
alt="A city street at sunset">
<picture>
<source media="(width >= 48rem)" srcset="wide-banner.jpg">
<img src="tall-banner.jpg" alt="People entering the museum">
</picture>srcset and sizes let the browser select an appropriate resolution; picture can select a different crop or art direction. Give every meaningful image useful alternative text and keep decorative images empty-alt when appropriate.
Control text, controls, and overflow
- Use relative sizing for spacing and typography where practical so zoom and user settings remain effective.
- Keep paragraphs at a readable measure rather than stretching them across an entire ultrawide display.
- Allow long words, URLs, and code to wrap or scroll within their own block instead of making the whole page wider.
- Give buttons and links enough space to identify and activate, and let button labels wrap when necessary.
- Prefer intrinsic sizes such as
min(),max(), andclamp()over rigid width and height values.
.article {
max-width: 70ch;
}
pre {
max-width: 100%;
overflow-x: auto;
}
.hero-title {
font-size: clamp(1.8rem, 5vw, 3.5rem);
}Do not hide overflow on the page as a quick fix: it can conceal broken content and make controls unreachable.
A repeatable responsive-development workflow
- Build the semantic HTML. Use headings, navigation, lists, forms, and landmarks before styling. Content order should make sense with CSS disabled.
- Add the viewport declaration and fluid base. Apply the box-sizing rule, a flexible page wrapper, normal flow, and contained media.
- Choose Flexbox or Grid per component. Start with intrinsic wrapping and flexible tracks.
- Resize continuously. Drag the viewport from narrow to wide rather than checking only named device presets.
- Record failure points. Add a relative-unit media query only where the current arrangement becomes cramped or awkward.
- Check real content. Test long headings, translated labels, empty states, large text, keyboard focus, and error messages.
- Test preferences and overflow. Enable reduced motion, zoom the page, inspect horizontal scrolling, and check images, tables, menus, and forms at both extremes.
Troubleshooting common responsive failures
The page scrolls sideways
Inspect the widest element. Typical causes are a fixed-width wrapper, an image without a maximum width, a long unbroken string, or a grid track that cannot shrink. Replace rigid widths with flexible sizing, add the media rule shown above, use minmax(0, 1fr) for shrinkable grid tracks, and allow code or URLs to scroll inside their own container.
The layout looks like a tiny desktop page on a phone
Check that the document head contains <meta name="viewport" content="width=device-width, initial-scale=1">. Without it, a mobile browser can use a wider layout viewport and scale the result down.
There are too many media queries
Remove queries that only compensate for fixed widths. Revisit normal flow, Flexbox wrapping, Grid’s auto-fit, relative units, and intrinsic functions first. Keep a query when the content genuinely needs a different ordering, navigation treatment, or column relationship.
Cards become impossibly narrow
Set a meaningful minimum with minmax(), or let the cards remain one column until the available space supports another. The minimum should come from the card’s text and controls, not from a device category.
An image fits but loads slowly
Containment and download efficiency are separate problems. Keep the CSS limit, then provide srcset, sizes, or picture sources so the browser can select a more suitable file or crop.
Animation still bothers users
Verify that the reduced-motion media query is active and that transitions are not being reintroduced by a more-specific rule. Keep essential state changes understandable without motion.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Or skip the browser setup
If you need screenshots of responsive states for documentation, previews, or visual checks, ScreenshotNeo captures a URL through one request instead of requiring you to configure a browser. It accepts consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each cleanup step can be disabled. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and response headers identify the page verdict and billing result.
Use the documented API options at https://screenshotneo.com/docs/ to set a viewport or device preset, retina scale, full-page capture, a CSS selector, dark mode, custom CSS or JavaScript, waits, blocked resources, headers, cookies, timezone, geolocation, image resizing, a chosen cache TTL, PDF output, bulk jobs, or signed links. Its MCP server provides take_screenshot, get_page_info, and capture_pdf tools to Claude, Cursor, and other MCP clients.
cURL
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpPython
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)Node.js
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);The Free plan includes 1,000 screenshots each month with no card. Starter is $5 for 3,000; Growth $15 for 15,000; Pro $39 for 60,000; Scale $99 for 250,000; and Business $249 for 1,000,000. Yearly billing gives two months free, and every feature is available on every plan. Create a free ScreenshotNeo account to begin.
Verify before publishing
- No horizontal scrollbar appears at narrow widths unless a component intentionally provides its own scroll area.
- Columns, navigation, forms, and tables remain usable while resizing through the transition points.
- Text remains readable when zoomed and when labels become longer.
- Images and video stay inside their containers, and responsive sources or crops are used where one file is unsuitable.
- The viewport declaration is present, keyboard focus is visible, and reduced-motion behavior works when enabled.
Frequently Asked Questions
Do I need a media query for every phone size?
No. Use flexible flow, Flexbox, Grid, and relative sizing first. Add a breakpoint only where your content becomes cramped or needs a different arrangement.
Recommended Free Tools
Is responsive design the same as making a mobile stylesheet?
No. Responsive design covers the full range from narrow phones to wide displays, plus conditions such as zoom and reduced-motion preferences.
Can CSS alone choose a smaller image download?
No. CSS can contain and scale an image; use HTML srcset, sizes, or picture when source resolution or crop should change.
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.
