Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Opinion] Is SSR still necessary? #1558

Closed
WiktorKa opened this issue Mar 5, 2018 · 4 comments
Closed

[Opinion] Is SSR still necessary? #1558

WiktorKa opened this issue Mar 5, 2018 · 4 comments

Comments

@WiktorKa
Copy link

WiktorKa commented Mar 5, 2018

Google announced that it is using Chrome 41 engine to render sites -
https://developers.google.com/search/docs/guides/rendering . I wonder if this means that there is no longer need for server side rendering (or soon wont be)? What do you think?
@frenzzy
Copy link
Member

frenzzy commented Mar 5, 2018

Take a look this video: Server-side Rendering with JavaScript Frameworks

@koistya
Copy link
Member

koistya commented Mar 5, 2018 •
edited
Loading

If you're building a public site, at a very least you need to do partial SSR - make sure that you pre-render <head> section on the server with all the meta tags (title, description, Open Graph etc.). Also, in order to improve the initial page load time, you would want to embed the list of application chunks used on the page, serialized data that can be dehydrated on the client (avoiding fetching data via Ajax on the initial page load), and ideally pre-render at least the layout of the page (background, header/toolbar), this way users will see something while application chunks are being loaded instead of a blank screen or a loader icon. Here is an example: https://firebase.reactstarter.com

Without full SSR you will also need to be extra careful not to introduce some fancy ES2017 syntax or language feature that Googlebot cannot understand. Otherwise, it will nullify all or some of your indexed pages degrading SEO. Surprisingly, Googlebot doesn't use the latest version of Chrome for rendering.

On the other hand, if you're building an admin panel, CRM dashboard or something like that, you don't need SSR.

@WiktorKa
Copy link
Author

WiktorKa commented Mar 5, 2018

I'm building a public site with full SSR based on this project, but recently I got into conversation with my friend who is also working on a public site with ReactJS and he claims that SSR is not really necessary anymore - so that's why I was interested in your opinion on that matter. Thanks for all the resources - they are helpful!

@langpavel
Copy link
Collaborator

langpavel commented Mar 9, 2018 •
edited
Loading

SSR is still good for some use cases:

  • Google is not the only search engine
  • Prerendered HTML can be displayed immediately, it's usually much smaller and content can be displayed much faster to the client, especially on first visit
  • There are much more positive side effects that can be hard to be spot at first… 🙂 (development, architectural and UX too)

This was referenced Apr 13, 2022
Open
Open
@lamo2k123 lamo2k123 mentioned this issue Apr 29, 2022
Open
@hajjiTarik hajjiTarik mentioned this issue Apr 29, 2022
Open
@hajjiTarik hajjiTarik mentioned this issue Jun 29, 2022
Open
@lamo2k123 lamo2k123 mentioned this issue Jul 1, 2022
Open
@snyk-bot snyk-bot mentioned this issue Jul 1, 2022
Open
@hajjiTarik hajjiTarik mentioned this issue Oct 6, 2022
Open
@hajjiTarik hajjiTarik mentioned this issue Nov 27, 2023
Open
@hajjiTarik hajjiTarik mentioned this issue Dec 20, 2023
Open
@hajjiTarik hajjiTarik mentioned this issue Mar 22, 2024
Open
@lamo2k123 lamo2k123 mentioned this issue Mar 28, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@langpavel @koistya @frenzzy @WiktorKa