Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Test responsiveness by checking how your page reflows and remains usable at many viewport widths—not just by opening one phone preset. Use Chrome DevTools’ Responsive mode to test your own CSS breakpoints just below, at, and above each threshold; check layout and interactions; then use Lighthouse and real devices to catch problems emulation cannot establish.
What responsive testing should prove
A responsive site adapts its layout and controls to the space available. The goal is not to make every screen look identical: it is to ensure content stays visible, readable and operable as the viewport changes. CSS media queries are a key part of that work, but a successful test also checks interactions, images and device-specific behavior.
Test the viewport—the browser’s content area—not only a device name. A preset can be a useful sample, but it will not necessarily land on the widths where your own layout changes. The most revealing checks are around the breakpoints in your CSS.
Build a repeatable responsive test
1. Define the width and state coverage
Write down the narrowest and widest supported widths, representative intermediate widths, and the breakpoints that change your layout. Include portrait and landscape if orientation affects the design. Also note relevant touch, resolution, or user-preference states when your CSS or interaction design responds to them.
Recommended Free Tools
#1 Best Overall
Use your actual CSS thresholds as test boundaries. If a layout changes at a particular @media condition, test immediately below it, at it, and immediately above it. This catches gaps, overlaps, and awkward transitions that a single preset can miss.
2. Open Chrome DevTools in Responsive mode
- Open the page in Chrome and open DevTools.
- Turn on Device Mode using the device toolbar button, or the keyboard shortcut shown in DevTools for your operating system.
- In the device toolbar, set the dimensions selector to Responsive.
- Enter an exact width and height, or drag the viewport edge to sweep through widths. Keep a note of the dimensions at which you find an issue.
Chrome’s documented convenient viewport samples include 320px, 375px, 425px, 768px, 1024px, 1440px and 2560px. Treat these as sampling points, not a universal device matrix: your breakpoints and audience determine which widths matter.
DevTools can show breakpoint bars for CSS media queries: blue for max-width and orange for min-width. Selecting a breakpoint changes the viewport to trigger it. Use those markers to find your rules, then test on both sides of each boundary rather than assuming the marker itself proves the transition works.
3. Inspect reflow, not just appearance
At each representative width and breakpoint boundary, inspect the whole page from top to bottom. Check whether columns stack or resize as intended, containers stay within the viewport, and text wraps without collisions. Look for unintended horizontal scrolling, clipped content, elements that overlap, and scrollable regions that are incorrectly sized. These are common small-viewport failure patterns noted in MDN’s responsive-design guidance.
Check headings, long words, tables, navigation, footers, fixed or sticky elements, and content loaded below the fold. A page can look fine at the top while a wide table or banner farther down forces the entire document sideways.
4. Exercise every important control
At narrow widths, open and close navigation, menus, dialogs, accordions, forms, date pickers and other key controls. Confirm that controls remain visible, reachable and usable, and that opening one does not leave the page trapped behind an overlay or an off-screen panel. Where touch is relevant, check that targets are practical to operate by touch.
Rank #2
Media queries can respond to more than width: orientation, input capabilities, resolution and user preferences can affect presentation. Test the states your site actually uses, including reduced-motion or dark-mode behavior if the design has rules for them. Device emulation is useful, but a physical device is a stronger check of touch and browser behavior.
5. Verify the viewport declaration
Inspect the document head for a viewport meta tag containing a width setting. The common mobile-first declaration is:
Free tools Windows power users keep installed
One-click scans. No signup required.
<meta name="viewport" content="width=device-width">Without a suitable viewport declaration, some mobile browsers use a wide virtual viewport—MDN describes an initial containing block typically around 980 CSS pixels—and scale the page down. That can make a desktop layout appear shrunk instead of allowing the intended narrow-screen layout to apply. MDN advises including the viewport meta tag in the document head.
6. Check images and video at representative widths
Resize through the widths you selected and confirm media stays inside its container and remains legible. If the page uses responsive image sources, check that an appropriately sized variant is selected rather than sending an unnecessarily large image to a small display. Also inspect video and embedded content, which can have fixed intrinsic dimensions or controls that do not fit a narrow column.
7. Run Lighthouse, then verify manually
Run Lighthouse with mobile-oriented settings and review viewport-width and image findings. Chrome’s content-width audit fails when window.innerWidth does not equal window.outerWidth; Chrome explains that content wider than the viewport can be scaled down and become difficult to read. The image audit compares rendered image size with the actual asset and can flag images materially larger than needed.
These audits identify specific conditions; they do not decide whether a menu is understandable, a dialog is usable, or a layout feels coherent. Treat an audit result as a lead to investigate and manually check the affected page state.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errors8. Confirm on actual devices and browsers
Emulation provides quick, reproducible viewport coverage. For high-value user journeys, also check at least one physical narrow-screen device and the browsers your audience supports. This is a practical quality-assurance recommendation, not a universal required device count: choose coverage based on your users and the risk of the page or flow.
Choose the right test method for the question
| Method | Best for | What it does not establish by itself |
|---|---|---|
| Chrome DevTools Responsive mode | Fast, precise viewport-width checks and testing around CSS breakpoints. | Real hardware, browser UI, or complete touch behavior on a physical device. |
| Lighthouse | Repeatable checks for documented viewport-width and image conditions. | Whether a control or visual arrangement is actually understandable and usable. |
| Physical device and supported browser | Confirming touch, browser behavior and hardware-specific details for important flows. | Efficient, precise coverage of every width and every breakpoint on its own. |
These approaches complement one another. Use DevTools for width precision, Lighthouse for repeatable audits, and real devices to validate the experience that emulation cannot fully reproduce.
Common problems and how to investigate them
The page looks like a tiny desktop site on a phone
Inspect the document head for a viewport meta tag with width=device-width. If it is missing or configured differently, the browser may lay the page out against a wide virtual viewport and scale it down. Confirm the declaration is present on the rendered document, not only in a template that the page does not use.
A horizontal scrollbar appears
Resize slowly and note the width where the scrollbar begins. Inspect wide images, fixed-width containers, tables, long unbroken text, and positioned elements. Compare widths just below and above your breakpoints; the overflow may come from a rule that only applies on one side of a threshold. Lighthouse’s viewport-width finding can help identify a mismatch, but inspect the element that extends beyond the viewport to find the cause.
Rank #4
- Used Book in Good Condition
A layout breaks only near one breakpoint
Use DevTools’ breakpoint bars to locate the relevant media query. Enter widths just below, at, and above its threshold. Check for competing min-width and max-width rules, and verify that intermediate widths are covered rather than only the intended phone and desktop endpoints.
Text, buttons or navigation overlap or disappear
Check wrapping, container constraints and the state of the menu or control at the failing width. Test the same interaction in a fresh page state: an open menu, modal or sticky header may have a different layout than the initial screenshot. Verify that the control is reachable and operable, not merely visible in a static frame.
The image audit flags an asset
Compare the image’s rendered dimensions with the delivered asset and review the responsive source selection. Supply appropriately sized variants where the implementation calls for them, then rerun the audit and inspect the image at the widths that matter.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Or skip the browser setup
For a capture at a chosen viewport, ScreenshotNeo provides a website screenshot API. One GET request returns an image or PDF; its API can set a viewport, and its parameters accept the names used by other screenshot APIs. See the ScreenshotNeo API documentation for available parameters and setup details.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com --data-urlencode width=375 --data-urlencode height=812 -o mobile.webpReplace YOUR_API_KEY with your key and https://example.com with your page. You can request screenshots at different widths to compare rendered results. A screenshot is a visual check, not a substitute for interacting with the page or running Lighthouse.
- Before capture, ScreenshotNeo accepts cookie or consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups and chat widgets; each step can be turned off.
- Bot checks or CAPTCHAs, blank pages, timeouts, failed loads and cache hits cost nothing; response headers report the page verdict and billing status.
- An MCP server offers AI-agent tools including
take_screenshot,get_page_infoandcapture_pdf. - The Free plan includes 1,000 screenshots per month with no card. Paid plans start at $5 for 3,000 shots; every feature is on every plan.
Sign up for ScreenshotNeo’s free plan to get 1,000 screenshots a month with no card.
Best Value
Keep a useful record of results
For repeat tests, record the URL or page, viewport width and height, browser, page state, and the result. Note whether the issue occurs below, at, or above a breakpoint, and include the interaction that exposes it. This makes a defect reproducible and helps distinguish a width-specific layout problem from a control-state or browser-specific issue.
Frequently Asked Questions
Are Chrome device presets enough to test a responsive site?
No. Use presets as samples, then test the site’s own CSS breakpoints and the widths around them.
Does a responsive screenshot prove the site works on mobile?
No. A screenshot shows appearance at a captured viewport; it does not prove controls work with touch or that the page behaves correctly in a physical browser.
Which widths should I test?
Cover the narrowest, widest and intermediate widths your site supports, with exact checks below, at and above each CSS breakpoint.
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.
