Photo by Mathew Schwartz on Unsplash
This is the story of our homepage make over to reach a solid lighthouse score. If you want to read how we mad...
For further actions, you may consider blocking this person and/or reporting abuse
Very minor nit: You probably want to wrap
hydrateRootinstartTransitionso the hydration becomes concurrent (improves INP, see slide 27)Yeah this is great - I almost forgot about it. I guess the main reason is that we potentially (see conclusion) replace React anyway at runtime with Preact (which has
startTransition, but it's only a stub invoking the callback immediately).I just tried it and the INP goes from ~50ms to ~5ms (in most cases it's just flat 0). So yeah, definitely worth doing!
Great slides!
Thank you! Really appreciate it.
Great article! Thanks!!!
Literally anything to make react faster I'm sure will be welcomed by the world.
But if this article interests you, read some about using nearly any other framework. 😜
Hehe one thing I missed in the article is that we looked into a migration to Astro, which we use for a couple of other websites. It would fit very well here. However, as the underlying component lib uses React the migration would need to be done here first - which is out of scope.
So I guess you miss the point of the article. If the article interests you, you might not look into React for doing web dev, but you rather have a page using React and want to speed it up (and a migration might be out of scope, too).
Web development is doomed!
Why does it have to be overcomplicated to deliver simple sites?
After almost 6 years in React, I plan to start over with much simpler tools than this. Stockholm syndrome forces us to do crazy gymnastics...
The best solution for a high-performance site is not to use React! 🤣
Abandoning React is one option to consider. This is the choice made by the Microsoft Edge development team, for example, with an HTML-First approach.
The font used in this article makes it very difficult to read on my phone. 😥
Are you sure that's not a problem with your configuration? The article (like any other on dev.to) cannot change the font of dev.to.
I'm using Safari and now I know why...