Skip to content

Hydrate clientside #828

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.

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

Merged
merged 2 commits into from
Nov 3, 2017
Merged

Hydrate clientside #828

merged 2 commits into from
Nov 3, 2017

Conversation

BookOfGreg
Copy link
Member

Fixes #808

Benchmarked on my companies private project and it's significantly faster for us!
Measured using 3 runs of Chrome Lighthouse Audit

I also felt cheeky enough to add myself as an author on the Gem if that's OK.

Rendering Server-side + React.Render (prerendering) faster at Perceptual Speed as it renders server-side but slower at First Interactive as the page is larger

  • 4.0s First Interactive
  • 2.3s Perceived

Rendering Client-side (no pre-rendering) faster at First Interactive but slower Perceptual Speed as lots of JS used to re-render over the top of more DOM

  • 3.0s First Interactive
  • 2.7s Perceived

Rendering Server-side + React.Hydrate wins at Both! Faster First Interactive and faster Perceptual Speed as page has content and much less JS to complete it.

  • 2.7s First Interactive
  • 2.4s Perceived

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant