Netflix: Removing client-side React.js improved performance by 50%
1–10 of 172 posts
Re: Netflix: Removing client-side React.js improved performance by 50%
#2Wow, this is crazy. As a huge vue.js fan I'd argue that the percentage value would be much lower with vue. But, I’m not totally sure.
Re: Netflix: Removing client-side React.js improved performance by 50%
#3Duh.
Re: Netflix: Removing client-side React.js improved performance by 50%
#4> ...improvement on our landing page
React on a landing page sounds like an overkill to begin with.
Re: Netflix: Removing client-side React.js improved performance by 50%
#5> ...improvement on our landing page React on a landing page sounds like an overkill to begin with.
In the talk they say they are still using react server side to make this mostly static page. I suppose with some cache in front of it though.
Re: Netflix: Removing client-side React.js improved performance by 50%
#6From the slides, it looks like the performance metric in question was TTI (Time to Interactive).
Re: Netflix: Removing client-side React.js improved performance by 50%
#7Sounds like form the comments they still use React they just defer loading it until after the page is otherwise usable.
I think this is a fairly common use case for server-side rendering in React and I wonder how much of this improvement they would have seen just by SSRing the page and putting the React scripts at the end instead of the header (or using defer). This is the strategy I use with any React marketing type pages.
Edit:
Just to give more detail incase anyone is wondering, usually marketing pages are relatively the same for every user (unless you are doing identity based personalization or a/b testing) so often you can get away with pre-rendering all the HTML generated by the React. Then you don't even need to load React server side, you just serve up a static file.
Re: Netflix: Removing client-side React.js improved performance by 50%
#8I like how the people in replies to the top tweet seem to get angry at someone implying that React is not great.
Re: Netflix: Removing client-side React.js improved performance by 50%
#9> ...improvement on our landing page React on a landing page sounds like an overkill to begin with.
In the talk they say they are still using react server side to make this mostly static page. I suppose with some cache in front of it though.
So basically they write React in front-end, then use react-renderer to generate static HTML and then serve it from back-end?
Seems like with this speed JS frameworks are going full-circle back to back-end rendering soon enough.
Re: Netflix: Removing client-side React.js improved performance by 50%
#10Today we learned: Removing an advanced library from a simple project increases performance.
Sorry for being sarcastic but don't you also find this too obvious?