it's rarely just the components though. you should check if you're actually profiling the
main thread usage or just guessing based on bundle size. if you have a massive dependency tree, even small components will trigger long tasks during the initial parse.
>the bundle size is the culpritthat assumption ignores how much
requestIdleCallback
and code splitting actually matter. i've seen tiny bundles with terrible performance because of poorly optimized
useEffect
loops or heavy watchers. have you run a trace through the devtools performance tab to see exactly which function is hogging the execution time? ⚠