Should I use SSR in React for blog sites?

Question

React

Good afternoon.

Based on recommendations from local gurus, I decided to look into React for building a server-rendered front.
The product is new for me and the following questions appear after reading the articles:

1. I believe that the load on the server grows noticeably in comparison with the return of traditional html without react and this will entail time costs before the first byte is rendered.
2. big weight of even a small page. The logic for extracting data from components becomes unreasonably expensive in terms of resources and coding time). You will have to unload all the same scripts, css, media - which are not in html and an object for redux - which is already present in html, as well as DOM elements generated by React. The size of the expanded data grows, perhaps by several orders of magnitude.
3. In fact, one application is reassembled several times - on the server and on the client.
4. In React, the renderToString method can be slow due to synchronism and single threading.
5. To speed up loading, you need to enable HTML caching / component caching.

For me, as a newbie in these matters, it is not yet possible to choose a rendering strategy in the React-Django bundle. It seems that if there is no special interactive, then there is no point in CSR either. Maybe for sites like blogs, it makes sense to use streaming server rendering or progressive rehydration? Or don't invent anything at all on the front side and leave jang's rendering of templates? In the latter case, you don’t need to bother with the front at all and don’t pre-install a bunch of libraries and don’t finish the djanga structure for the rest api?

Tell me, what is the benefit of connecting React SSR for writing a la blog, besides dynamism and SEO susceptibility?

Answer 1

Why do you need react for a blog?