Course contentsShow
← Web Development
Lesson 1916 of 2,98235. Web Performance FundamentalsFree lesson

Chrome DevTools Performance Panel Basics

Learn to record and analyze performance traces in Chrome DevTools.

Chrome DevTools Performance Panel Basics

What you'll learn: How to record and analyze performance traces in Chrome DevTools to identify bottlenecks and optimize your web application's runtime behavior.

Understanding the Performance Panel

Think of Chrome DevTools' Performance Panel as a flight recorder for your web page—it captures everything happening under the hood while your site runs, creating a detailed timeline you can analyze frame-by-frame. Unlike static metrics you've seen (like LCP or CLS scores), this tool shows you why your metrics are what they are by revealing what code ran, when, and for how long.

Recording a Performance Trace

To capture a trace:

  1. Open Chrome DevTools (F12 or Cmd+Option+I)
  2. Navigate to the Performance tab
  3. Click the Record button (circular icon) or press Cmd+E
  4. Interact with your page (scroll, click, navigate)
  5. Click Stop to end recording

The panel generates a flame chart showing all browser activity during that window—network requests, script execution, rendering, painting, and more.

Analyzing the Trace

The timeline is divided into swim lanes:

  • Network: Shows resource loading (HTML, CSS, JS, images)
  • Main thread: Where JavaScript executes and rendering calculations happen
  • Frames: Visual markers showing whether you hit 60fps
  • Interactions: User inputs and their processing time

Look for long tasks (yellow/red blocks exceeding 50ms) on the main thread—these often cause poor FID/INP scores. Hover over any block to see which function ran and its duration. Tall flame chart "mountains" indicate deeply nested function calls that may need optimization.

Key Takeaway: Chrome DevTools Performance Panel records a detailed timeline of browser activity, letting you pinpoint exactly which operations slow down your page—essential for diagnosing issues behind poor Core Web Vitals and overall sluggish performance.