PC 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 & 11Outdated 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 matchChrome DevTools is built into Google Chrome and helps you connect a visible problem to the evidence behind it: use Elements for the rendered page and styles, Console for messages and JavaScript, Sources to pause code, and Network to investigate requests and loading. Open the panel closest to the symptom, reproduce the issue, and follow the evidence into another panel when needed.
Open DevTools at the problem
Right-click the page and choose Inspect to open DevTools with the relevant element selected in Elements. To turn on Inspect mode with a keyboard shortcut, use Ctrl+Shift+C on Windows, Linux, or ChromeOS, or Cmd+Option+C on macOS. To open Console directly, use Ctrl+Shift+J on Windows, Linux, or ChromeOS, or Cmd+Option+J on macOS. Shortcuts and interface details can vary with Chrome versions.
As an Amazon Associate I earn from qualifying purchases.
If DevTools opens in a narrow panel, you can resize or reposition it to make the relevant details easier to read. Start with the panel that matches the failure rather than inspecting every panel in sequence.
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 minuteChoose a panel based on the symptom
| Symptom or question | Start here | What it can show |
|---|---|---|
| An element looks wrong, is missing, or is in the wrong place | Elements | The rendered DOM node, its styles, and computed appearance |
| A click or other interaction fails, or an error appears | Console | Logged messages, errors, and results of JavaScript expressions |
| Code behaves unexpectedly and logs are not enough | Sources | Execution paused at a breakpoint so you can inspect what happens around a line |
| A page or resource does not load as expected | Network | Requests and their headers, payload, response, initiator, and timing |
| A layout breaks at a mobile viewport size | Device Mode and Elements | A simulated viewport and the page layout at that size |
Inspect an element and its styling
- Select the visible element. Right-click it and choose Inspect, or enable the Inspect picker and click the element on the page. DevTools highlights the corresponding DOM node in Elements.
- Follow the DOM structure. Expand nearby nodes to see whether the content is present in the document, nested where expected, or absent altogether.
- Review Styles and computed appearance. Check which rules apply and whether a rule is overridden. Change a declaration temporarily in DevTools to see whether it explains the visual result; a temporary edit is not a change to your source files.
- Use the picker tooltip as a clue. It may show dimensions, foreground and background colors, font properties, padding, margin, accessibility name and role, keyboard focusability, and text contrast for headers. This is useful for debugging but is not a full accessibility audit.
Read Console messages and test JavaScript
Open Console to see logged messages and errors, and to evaluate small JavaScript expressions in the page context. Begin with the first relevant error and note when it occurs: on initial load, after a click, or after another action. A Console message can point you toward a script problem, but a failed network request or a CORS issue may need further inspection in Network or Issues.
If you need to reload to reproduce a problem, enable Preserve Log in Console first. Otherwise, messages may be cleared when the page reloads. Use the Console for focused checks; for behavior that depends on the execution path or changing values, a breakpoint in Sources can provide better evidence than adding more log statements.
Pause execution in Sources
When a script reaches an unexpected result and Console messages do not explain why, use Sources to pause execution with a breakpoint. Reproduce the problem and inspect what happens around the failing line while execution is paused. This lets you examine the code path and relevant values at the point where behavior diverges, rather than inferring everything from output after the fact.
Trace page and resource loading in Network
- Open Network before reproducing the issue. Network records requests while DevTools is open; opening it after a failure will not show the earlier activity.
- Reproduce the load or interaction. Reload the page or repeat the action that triggers the missing or delayed resource.
- Filter the request list. Narrow the list to the kind of resource or request you are investigating.
- Select a request and inspect its details. Check Headers, Payload, Preview or Response, Initiator, and Timing as relevant. These can help distinguish a request that was never made from one that was made but returned unexpected content or took longer than expected.
- Compare conditions when needed. Check cache behavior or apply network throttling to investigate whether the issue depends on loading conditions. Treat a throttled or cached reproduction as a diagnostic condition, not necessarily the same as a user’s actual connection.
For example, if an image is absent, inspect the DOM to confirm the image element exists, then look for its request in Network. If a request appears, its response and timing may clarify the next step; if it does not, inspect the code or page state responsible for initiating it.
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 →Check a responsive layout with Device Mode
Use Device Mode to simulate a mobile viewport, then inspect the layout at the relevant size. This is a useful first check for responsive issues, but viewport emulation should not be treated as proof that every behavior matches every physical device. If the problem only occurs on a particular phone or depends on device-specific behavior, verify it on that device as well.
A practical debugging sequence
- Write down what is wrong and what action produces it.
- Open DevTools before reproducing the problem.
- Use Elements for a rendering or layout symptom, Console for runtime messages, Sources for an execution-path question, or Network for a loading question.
- Reproduce the failure once and note the first relevant evidence, including when it occurs.
- Follow the evidence into a second panel when needed: for example, trace a Console error to a request in Network, or trace a visible layout problem to the node and rules in Elements.
- Change one condition at a time, such as a CSS declaration or network throttling setting, so you can tell which change affects the symptom.
Common debugging problems
The request is missing from Network
Network logging starts while DevTools is open. Open it, reproduce the action, and check again. If the request still does not appear, investigate whether the action or page state actually triggers it.
Console messages disappear after reload
Enable Preserve Log before reloading so messages remain available across page loads.
The page looks wrong, but the CSS rule seems correct
Use Inspect mode to select the exact visible node, then review its applied and computed styles. Check for an unexpected ancestor, a different node than the one you intended, or an overriding rule before editing source code.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →A Console error does not explain the failure
Reproduce the error and inspect related requests in Network. Console network or CORS messages can point to relevant request details or Issues information; the message alone may not show the full cause.
A mobile emulation check does not reproduce the device issue
Device Mode simulates a viewport. Do not assume that it reproduces every behavior of physical hardware; confirm device-specific problems on the affected device when possible.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Performance, reliability, and cost considerations
DevTools is integrated into Chrome, so this workflow does not require a separate paid product. For useful evidence, open the relevant panel before reproducing the issue and keep the reproduction condition clear: normal loading, a cache comparison, throttling, or a simulated viewport. Network details describe the requests recorded in that session, while Device Mode provides a viewport simulation rather than a guarantee of identical physical-device behavior.
Or skip the browser setup
If you need a screenshot rather than an interactive debugging session, ScreenshotNeo is a website screenshot API and MCP server. One GET request can return an image or PDF. For example, this cURL request saves a WebP screenshot of Stripe:
Recommended Free Tools
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 documentation for API options. Cookie banners, popups, and chat widgets are removed before the shot; bot checks, blank pages, and failed loads are never billed. Its MCP server lets AI agents take screenshots. The Free plan includes 1,000 screenshots a month with no card, and paid plans start at $5 for 3,000.
Sign up free for ScreenshotNeo.
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.
