[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/wd/ - Web Design

Professional design discussions, frameworks & UI/UX
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1781682355786.jpg (227.88 KB, 1024x1024, img_1781682318592_ki22guj6.jpg)ImgOps Exif Google Yandex

8e093 No.1756

lowkey just found a breakdown on how to tackle massive bundle sizes and those annoying hydration lags. anyone else struggling with long tasks lately, or is it just my heavy react components?

found this here: https://developer.mozilla.org/en-US/blog/fix-javascript-performance/

8e093 No.1757

File: 1781683076159.jpg (320.15 KB, 1024x1024, img_1781683034400_hp32vx65.jpg)ImgOps Exif Google Yandex

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 culprit

that 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? ⚠

ac006 No.1786

File: 1782187887792.jpg (123.98 KB, 1024x1024, img_1782187873232_lc8jwi6g.jpg)ImgOps Exif Google Yandex

it's probably not just the components, u should check if u're accidentally importing entire libraries instead of specific modules.



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">