Course contentsShow
← React
Lesson 2209 of 2,39649. Performance: Identifying ProblemsFree lesson

Reading the Flame Graph View

Understanding the flame graph: each bar is a component, width is render time, and color intensity shows relative cost.

Reading the Flame Graph View

What you'll learn: How to interpret the Profiler's flame graph to understand which components are expensive to render and where performance bottlenecks hide.

What the Flame Graph Shows

After recording a profile in React DevTools, the flame graph displays a visual breakdown of your render. Think of it like a performance heat map for your component tree.

Each Bar Represents a Component

Every horizontal bar in the flame graph is a single component that rendered during your profiling session. The bars are stacked vertically to show the component hierarchy—parent components appear above their children, creating a "flame" shape that flows downward through your tree.

Width = Time Spent Rendering

The width of each bar represents how long that component took to render. A wider bar means more time was consumed. This includes the component's own rendering logic plus all of its descendants combined.

Color Intensity = Relative Cost

The color of each bar ranges from light yellow (fast) to dark orange/red (slow). This color coding shows the relative rendering cost within your recorded session. The darkest bars are your performance bottlenecks—these components took the longest to render compared to everything else in the tree.

Reading It Like a Map

Start at the top of the flame graph. If you see a wide, dark-colored bar, that component and its children consumed significant render time. Drill down into its children to see if the cost is in the parent's logic or distributed among expensive children. Narrow, light bars? Those components rendered quickly—no optimization needed there.

Key Takeaway: The flame graph translates render performance into visual space: each bar is a component, width shows render duration, and color intensity reveals which components are the slowest relative to the rest of your app.