First find which components rendered and how long they took, then ask why each one did. There are three tools:
- React DevTools Profiler (browser extension). Record an interaction; for each commit it shows a flame chart and a ranked chart of the components that rendered and their durations. A setting records why each one rendered: which props, state or hooks changed. Another setting highlights components on screen as they render.
- React Performance Tracks (React 19.2). Record in the browser's Performance panel and React adds a Scheduler ⚛ track (each update's priority, its Render, Commit and effects phases) and a Components ⚛ flame graph. In development, clicking a render shows its changed props, and an update shows which component's
setStatescheduled it. It sits next to the browser's own main-thread data. <Profiler id onRender>. Wrap a subtree and React callsonRender(id, phase, actualDuration, baseDuration, startTime, commitTime)after each commit. Use it to collect numbers in code: tests, dashboards, a before/after comparison.
The answer is one of the three render causes: the component's own state, its parent rendering, or a context it reads. "Parent rendered, props deeply equal" is the case memo or the React Compiler fixes; a new object each render shows up as a changed prop.
None of this runs in a normal production build. Development builds work but are slower (and Strict Mode renders twice), so use them to find which and why, and the profiling build (react-dom/profiling) for how long. Long tasks and responsiveness metrics outside React belong to browser profiling and web performance.