Skip to content
Tutorials Center
My learning

Topics

Lesson 36 of 36 ยท Projects and Practice

Practice: A DevTools Debugging Checklist

Practice mapping symptoms to the right DevTools panel, work through scenario questions, and take away a checklist plus keyboard shortcuts for faster debugging.

Knowing every panel is not enough; under pressure you need to know which one to open first. This final lesson trains that reflex. You get a symptom-to-panel map, a set of scenarios to work through, a checklist you can paste into your team's wiki and the shortcuts that save the most time.

From symptom to panel

Symptom Open first Look for
Element is in the wrong place or wrong size Elements > Styles, Computed, Layout Overridden rules, box model, flex or grid overlay
JavaScript error or wrong value Console, then Sources Stack trace, breakpoints, Watch and Scope
Data missing or request failing Network Status, Headers, Payload, Response, Initiator
Page loads slowly Network, then Performance, Lighthouse TTFB, blocking resources, late LCP, long tasks
UI freezes or janks on interaction Performance Long tasks, forced reflow, INP phases
Page jumps while loading Performance > Layout Shifts Images or ads without reserved space
Memory grows over time Performance monitor, Memory Detached DOM, listeners, retained size
Stale content after deploy Application > Service workers, Cache storage Waiting worker, cached HTML
User keeps getting logged out Application > Cookies, Network > Cookies tab SameSite, Secure, expiry, blocked reasons
Poor accessibility or SEO score Lighthouse, Elements > Accessibility Contrast, labels, alt text, title

The stand-in below encodes this map as a tiny triage helper. Extend it with your own team's symptoms; writing your own map is one of the best ways to remember it.

JS Stand-in: symptom triage helper

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Scenario drills

Work through each scenario before reading the hint. Say out loud: which panel, which number, which fix.

  1. The hero image loads at 5 s. Hint: Network > select the image, check Initiator and Priority; Performance LCP breakdown shows the biggest phase.
  2. Clicking "Add to cart" takes 600 ms to respond. Hint: Performance, record the click; the Interactions track splits delay, processing and presentation.
  3. After navigating between views 20 times the tab uses 1.5 GB. Hint: Performance monitor to confirm; heap snapshot comparison, then retainers.
  4. The API works in Postman but fails in the browser. Hint: Console shows CORS; Network shows a preflight OPTIONS; the server lacks headers.
  5. A button is invisible on Safari-sized screens only. Hint: Device Toolbar with that size; Elements > Computed for display and overflow; check media queries in Styles.
  6. Lighthouse gives accessibility 82. Hint: open the failing audits, click each node; fix contrast and labels, then test by keyboard.

The next stand-in lets you check your answer against a "budget": it takes the measurements and prints which of the standard thresholds fail, so you can practice the habit of judging numbers rather than feelings.

JS Stand-in: judge your numbers against thresholds

Press Run (or Ctrl + Enter) to see the console output here.

No output.

The checklist

Copy this list and adapt it.

Before measuring

  • Incognito window, extensions off, correct device profile, CPU and network throttling.
  • Disable cache for cold loads; keep a second profile for warm loads.
  • Write down the exact steps to reproduce.

Debugging code

  • Read the first error in the Console, not the last; open the stack trace.
  • Set a breakpoint instead of adding console.log everywhere; use conditional breakpoints and logpoints.
  • Check Network for the data your code received, before suspecting the code.

Performance

  • Start from the metrics (LCP, INP, CLS, TBT), then find the cause: waterfall, long tasks, layout shifts.
  • Fix one thing, re-measure, keep numbers in a table.
  • Add budgets and field monitoring after the fix.

Storage and caching

  • Clear site data between tests; check service workers and caches when behavior is stale.
  • Check cookie attributes when authentication behaves randomly.

Quality

  • Run Lighthouse for accessibility and SEO; add keyboard and screen reader tests.
  • Test on a real mid-range phone with remote debugging (chrome://inspect) at least once.

Shortcuts worth learning

Shortcut (Windows/Linux) Action
F12 or Ctrl+Shift+I Open DevTools
Ctrl+Shift+C Inspect element mode
Ctrl+Shift+M Device toolbar
Ctrl+Shift+P Command menu (run any command)
Ctrl+P Open a file by name in Sources
Ctrl+Shift+F Search across all loaded files
Ctrl+E Start or stop recording in Performance
Esc Toggle the bottom drawer with the Console
Ctrl+\ Pause or resume script execution

On macOS use Cmd instead of Ctrl, and Cmd+Option+I to open the tools. The command menu is the most important of all: type any word, such as "screenshot", "coverage", "rendering" or "dark", and DevTools offers the matching command.

What next?

Keep a debugging journal: for every bug record the symptom, the panel, the cause and the fix. After a month you will see the same five causes again and again, and your reflexes will be faster than any checklist. To go deeper, pick a real site (your own, preferably), run the audit project again on a different page, and compare your findings with field data from the Chrome UX Report.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Users report that a page shows an old version after deployment. Which area do you check first?

    A waiting service worker or a stale cached response is the usual cause of old versions.
  2. 2. Which shortcut opens the command menu?

    Ctrl+Shift+P (Cmd+Shift+P on macOS) opens the command menu. Ctrl+Shift+M is the device toolbar.
  3. 3. Your tab's memory grows with every navigation. Which tools do you use, in order?

    Confirm the growth, then compare snapshots to find objects that keep accumulating and read their retainers.
  4. 4. Why record numbers in a table while fixing performance problems?

    Measurements before and after each change show which fixes work; without them you are guessing.

Summary

  • Match the symptom to the panel first: Elements for layout, Console and Sources for code, Network for requests, Performance for time, Memory for leaks, Application for storage, Lighthouse for audits.
  • Always measure under a fixed, realistic profile and write the numbers down.
  • Use a checklist, keep a debugging journal and learn the command menu and shortcuts.

Next: Back to the Chrome DevTools course