Loading…
A short voice session: one question, one follow-up, then instant feedback — up to 5 minutes.
Reproduce on realistic data and devices, measure interaction latency, use the React Profiler to find components that render often or slowly and why, check the browser Performance panel for non-React work, then fix and re-measure.
Define the slow interaction and measure it, ideally with field data such as INP, and reproduce it locally on a throttled CPU with production-like data. Record with the React DevTools Profiler to see which components rendered, how long they took and what caused each render, for example changed props, context or a parent. Use the browser Performance panel to check whether time goes to React rendering, layout, painting, long tasks from third-party scripts or garbage collection. Address the biggest cost first, whether that is narrowing state, memoizing, virtualizing or moving work off the main thread, then repeat the same measurement to confirm the improvement and add monitoring to catch regressions.