Closed gustaveWPM closed 3 months ago
I'm testing this hypothesis...
https://github.com/Tirraa/dashboard_rtm/commit/28fc13629f79ab67b03c0c1a65ee23e410f690ac
Will benchmark this URL: https://dashboard-rtm.vercel.app/en/blog/patch-notes/dashboard/post-05
This does not seem to fix the hydration TBT stress...
Closing for now. :(
Well... Since the v1.1.0 will be released in several months... I'll just reopen it and praise that the conditional hydration will be improved.
Now that the SSG came back (https://github.com/Tirraa/dashboard_rtm/issues/115)...
Disabling SSR, for real, (https://github.com/Tirraa/dashboard_rtm/commit/1ed6789eb37f7be6e4ed512dd95e729d3a10a057) is even worse: in addition to the TBT, we now have CLS (<MDX>
is first rendered as null
, then populated... Even worse.)
Enabling SSR (https://github.com/Tirraa/dashboard_rtm/commit/89e8d406e2613c5e1952e4ed331d322035296787) doesn't change anything.
Wait & see...
Nogo. This problem is not replicated in https://tailwind-nextjs-starter-blog.vercel.app/
So it comes from something in the codebase. It's not due to Contentlayer, nor to Next, and it doesn't require to be "Workaround-ed".
Just a side note... Dunno if it would reduce the hydration overhead on pagespeed insights for big blog articles/pages/landing pages...