liveBook · Manning

Performance panel

As explained in Fast by Default

A browser developer-tools interface that records and displays runtime activity and timing relevant to page responsiveness.

The performance panel is a browser developer-tools interface for inspecting what happens after a page loads: JavaScript execution, style calculation, layout, painting, and responsiveness. It immediately reports local Core Web Vitals, including Largest Contentful Paint (LCP), Cumulative Layout Shift (CLS), and Interaction to Next Paint (INP). section 7.1.2

Use the panel as a focused measurement workflow:

  • Enable CPU throttling before recording; the 4x setting roughly simulates JavaScript performance on a mid-range phone. section 7.1.2
  • Profile a page load by clicking reload, or profile an interaction by recording only the specific action being measured. section 7.1.2
  • Keep interaction traces short and focused: a two-second button-click recording is more actionable than ten seconds of general browsing. section 7.1.2
  • Read the flame chart from the widest bars downward: wide bars identify expensive work, while nested bars reveal the functions responsible. section 7.1.2
Table 7.1 Web profiling concerns, tools, and diagnostic patterns
Concern
Primary tool
What to look for
Loading performance
Network panel
Large bundles (over 200KB compressed), long dependency chains, render-blocking resources, and missing cache headers
Runtime behavior
Performance panel
Long tasks (over 50ms), layout thrashing, expensive paints, and poor Core Web Vitals scores
Memory stability
Memory panel
Growing heap size across navigations, detached DOM nodes, and event listeners that accumulate

Use the profiling map to distinguish runtime problems from loading and memory problems, then select the appropriate developer-tools panel. section 7.1

Finding layout thrashing

A news-site engineer records article scrolling with 4x CPU throttling. The flame chart exposes a 180ms long task triggered whenever a social widget enters view. Repeated Recalculate Style and Layout blocks indicate that JavaScript is forcing layout to be recalculated repeatedly. section 7.1.2

How Fast by Default covers it

How deep it goes
Provides a recording workflow and flame-chart interpretation, stopping short of prescribing fixes for each detected bottleneck.
Examples
Uses a news-site scrolling trace, a social-widget long task, focused button-click recordings, and forced-reflow flame-chart markers.
What it assumes
Assumes a browser page and basic developer-tools access while distinguishing runtime analysis from loading and memory profiling.
What you can do after
Diagnose runtime bottlenecks by recording focused traces, simulating slower devices, and locating expensive call paths.
How it connects
Connects runtime profiling with Core Web Vitals, CPU throttling, flame charts, layout thrashing, and Network and Memory panels.

Also explained in

Compare how 2 books explain performance panel →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Fast by Default. The section links point to the parts of the book it draws on.