Ranked Chart: Finding the Slowest Components
You'll learn how to use the Profiler's ranked view to quickly identify which components consume the most render time, so you can prioritize optimization work effectively.
When profiling a React app, the flame graph shows the render hierarchy, but it can be overwhelming—like searching for a needle in a haystack. The ranked chart solves this by sorting components from slowest to fastest, making performance bottlenecks immediately obvious.
How the Ranked View Works
After recording a profile, switch from the flame graph to the ranked chart (usually a tab or button in the Profiler). Instead of showing parent-child relationships, this view lists every component that rendered during the selected commit, ordered by total render duration.
Think of it like a leaderboard of "most expensive components." The component at the top took the longest to render—that's where you should focus your optimization efforts first.
Why This Matters
When you have dozens or hundreds of components rendering, you don't want to waste time optimizing a component that renders in 0.5ms when another takes 150ms. The ranked chart immediately surfaces the high-impact targets.
Look for:
- Components at the top of the list with surprisingly long durations
- Components that render frequently and take substantial time
- Components you didn't expect to see rendered at all
Practical Use
Combine this with the commit information you learned earlier: click on a slow component in the ranked chart to see why it rendered. If a component appears slow but rarely renders, it might be fine. If it's slow and renders on every keystroke, that's your optimization target.
Key Takeaway: The ranked chart sorts components by render time, letting you identify and prioritize the slowest components instead of hunting through the entire component tree manually.