Component Render Count and Duration Totals
What you'll learn: How to use the React DevTools Profiler to see how many times a component rendered during a session and the total time it spent rendering.
The Performance Summary View
When you're profiling your app, you don't just want to see what rendered in each commit—you want to understand patterns over time. The Profiler's component view aggregates data across all recorded commits, showing you:
- Render count: How many times a specific component rendered during the profiling session
- Total duration: The cumulative time spent rendering that component across all renders
This is like reviewing a player's season statistics instead of just one game. A component that renders once for 50ms might not be a problem, but if it renders 100 times for 50ms each, that's 5 seconds of wasted work.
How to Access This Data
After recording a profile, click on a specific component in the flame graph or ranked chart. The right-hand sidebar displays detailed information including:
- Number of times the component rendered
- Total time spent rendering
- Average render duration
- Which commits included this component
This view helps you spot components that are rendering too frequently, even if each individual render is fast.
What This Reveals
A high render count often indicates:
- Missing memoization opportunities
- Props changing unnecessarily
- Context providers re-rendering too often
A high total duration combined with moderate render count suggests the component's render logic itself is expensive and might need optimization (virtualization, code splitting, or algorithm improvements).
Key Takeaway: The Profiler's component statistics show render frequency and cumulative duration, helping you distinguish between "renders often but fast" vs "renders occasionally but slow" performance issues.