What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Make a website mobile-friendly by giving it a device-width viewport, replacing rigid widths with flexible layouts, and checking that content reflows and controls work at narrow screen sizes. Start with the page that matters most, fix what breaks on a phone, then test the actual content in browsers and on representative devices.
1. Find what breaks on a narrow screen
Inspect the existing page at a phone-sized width before changing its layout. Look for horizontal scrolling, columns that become too narrow, clipped images, navigation that no longer fits, small text, and buttons or links that are difficult to tap. Test with real page content: long headings, large images, forms, tables, and embedded media often expose problems a blank layout will not.
Google describes responsive design as its preferred configuration because it is the easiest design pattern to implement and maintain. It uses the same URL and HTML while the presentation adapts to the available space. Google’s mobile-sites guidance also describes dynamic serving and separate mobile URLs as alternatives.
Choose an implementation that fits the site
| Configuration | How it works | What to weigh |
|---|---|---|
| Responsive design | Same URL and HTML; CSS adapts the presentation. | Google recommends it for ease of implementation and maintenance. It keeps URLs consistent and avoids having to maintain separate mobile markup. |
| Dynamic serving | Same URL, but the server returns different HTML according to the device. | Can fit an existing architecture, but serving different content or metadata can create consistency risks. |
| Separate mobile URLs | Different URLs serve mobile and desktop versions. | May be constrained by a legacy system; keeping content, headings, and metadata equivalent across versions requires care. |
These are configurations, not phone-versus-tablet breakpoints. For most existing sites, improve the current layout responsively unless the architecture gives you a concrete reason to choose another approach.
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 matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstall#1 Best Overall
2. Set the viewport
Add this element inside the document’s <head>:
<meta name="viewport" content="width=device-width, initial-scale=1">width=device-width makes the page layout use the device’s CSS-pixel width; initial-scale=1 sets its initial display scale. Without an appropriate viewport declaration, a phone may lay out the page as though it were a wider desktop page and then shrink it to fit. See Digital.gov’s mobile guidance.
3. Replace fixed widths with flexible layout
Rigid page and column widths can overflow narrow screens and leave wasted space on wide ones. MDN describes responsive web design as an approach rather than a separate technology: combine flexible layout, responsive media, and CSS rules that adapt presentation to the available space. MDN’s responsive design guide explains the approach.
Use flexible sizing and let content wrap
Prefer fluid widths and layout systems such as CSS Grid or Flexbox over a page shell with a fixed pixel width. Let columns wrap or stack when they cannot fit comfortably. Set sensible maximum widths where they improve readability on large screens; flexibility does not mean stretching every line across the whole monitor.
.page {
width: min(100% - 2rem, 72rem);
margin-inline: auto;
}
.content-layout {
display: grid;
grid-template-columns: minmax(0, 2fr) minmax(14rem, 1fr);
gap: 1.5rem;
}
img, video, iframe {
max-width: 100%;
}
img, video {
height: auto;
}
@media (max-width: 48rem) {
.content-layout {
grid-template-columns: 1fr;
}
}This is an illustrative starting point, not a universal breakpoint or a complete stylesheet. Adapt selectors and widths to the site. The minmax(0, ...) columns help prevent long content from forcing a grid wider than its container. For embedded media, also check its intrinsic dimensions and whether the embed can adapt inside its parent.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Choose breakpoints where the content needs them
Use media queries when a layout stops working—for example, when a navigation row wraps awkwardly or two columns make the text too cramped. Pick the breakpoint from the content’s behavior, not from a supposedly universal phone or tablet boundary. MDN covers using CSS media queries.
4. Make reading and interaction work at phone widths
Check reflow at 320 CSS pixels
For ordinary content read horizontally, W3C’s WCAG 2.1 Reflow guidance uses an equivalent viewport width of 320 CSS pixels. At that width, readers should generally be able to read lines without scrolling horizontally. Content that requires a two-dimensional layout—such as some data tables—has exceptions. This is guidance for the stated content and criterion, not a rule that every page element must fit into one narrow column. See W3C’s Reflow understanding document.
Rank #4
Keep text comfortable to read
Check actual text at narrow widths and with browser zoom. Avoid shrinking text just to preserve a desktop arrangement; rearrange the layout instead. Digital.gov cites at least the browser-default line-height as a readability recommendation and gives 1.2 as a practical figure. Treat that as guidance, not a standalone accessibility pass/fail threshold. Digital.gov’s guidance also discusses mobile reading.
Give touch controls enough size and separation
WCAG 2.1 Success Criterion 2.5.5 is Level AAA and specifies pointer targets of at least 44 by 44 CSS pixels, subject to exceptions. It is not a blanket requirement that every link meet that size. Separately, Digital.gov cites Android guidance of at least 48 CSS pixels in width or height and 32 CSS pixels between targets. These figures come from different guidance; do not treat them as interchangeable thresholds. Check buttons, form controls, and navigation on the rendered page. See W3C’s Target Size understanding document and Digital.gov’s mobile guidance.
5. Preserve the content people and search engines need
If Google Search visibility matters, keep primary content accessible on mobile and make important resources crawlable. Google recommends keeping core content equivalent across mobile and desktop. Avoid making essential text available only after an interaction that Google may not perform to load it. If separate mobile URLs or device-dependent HTML are already in use, check that content, headings, and metadata remain equivalent. Google’s guidance covers mobile-first indexing and mobile site configurations.
A responsive redesign can improve usability, but the guidance cited here does not establish a guaranteed ranking increase from redesigning a site. Treat search visibility as a reason to preserve accessible, equivalent content—not as a promise of a particular result.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.6. Check the finished page, then fix the remaining failures
- Set the viewport: confirm the viewport meta element is in the page head.
- Check fit: inspect narrow widths for overflow, clipped content, cramped columns, and oversized media.
- Check reflow and zoom: review ordinary reading content at an equivalent width of 320 CSS pixels and try browser zoom.
- Check touch interaction: tap navigation, buttons, and form controls; check target size and spacing against the guidance that applies to your project.
- Check important mobile content: verify that primary text and resources are available without relying on an interaction that must be triggered to reveal them.
- Recheck in browsers and on representative devices: responsive previews are useful, but they do not replace checking the rendered page and real interaction.
- Use a page-checking tool as one input: PageSpeed Insights is one option, but a score alone does not prove that a page is usable or accessible. The Google article introducing it is dated 19 May 2014; its usability point that users expect vertical rather than horizontal scrolling is best treated as a design principle, not a current ranking claim. Google’s PageSpeed Insights article.
Common problems and practical fixes
| Symptom | Likely cause | What to check or change |
|---|---|---|
| The page looks tiny on a phone. | The page may be rendered as a wide desktop layout and scaled down. | Check that the viewport meta element is present and correctly written. |
| The whole page scrolls sideways. | A fixed-width container, unwrapping navigation, oversized media, or long unbroken content may exceed the viewport. | Inspect the overflowing element; make containers flexible, allow appropriate wrapping, and constrain media to its container. |
| Columns or cards look cramped. | The layout keeps too many columns at a width where their contents no longer fit. | Let items wrap or use a media query to stack them when the content stops working. |
| Buttons are difficult to tap. | Controls may be too small or too close together. | Increase their usable target area and spacing; assess the applicable target-size guidance and its exceptions. |
| Mobile users or crawlers cannot find key content. | Mobile content may differ from desktop content or depend on an interaction to load. | Make primary content available on mobile and check equivalence and crawlable resources. |
7. If you use a CMS, start with its theme
If your CMS does not let you modify the current theme readily, Google notes that you may need a mobile-friendly theme. Look for a responsive theme for the CMS you already use, then check your real content at narrow widths rather than relying only on a theme demo. The guidance cited here does not compare specific theme vendors or establish their current prices.
Or skip the browser setup
For a repeatable screenshot check while you work through those layout changes, ScreenshotNeo is a website screenshot API and MCP server for developers. A single GET request can return a PNG, JPEG, WebP, or PDF. Example cURL request:
Quick Recap
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the ScreenshotNeo API documentation for setup and options. The service accepts cookie or consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each of those steps 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. Its MCP server provides take_screenshot, get_page_info, and capture_pdf for Claude, Cursor, and other MCP clients. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 shots. Sign up for ScreenshotNeo’s free plan.
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.
