Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 atFirst Interactive
as the page is largerRendering Client-side (no pre-rendering) faster at
First Interactive
but slowerPerceptual Speed
as lots of JS used to re-render over the top of more DOMRendering Server-side + React.Hydrate wins at Both! Faster
First Interactive
and fasterPerceptual Speed
as page has content and much less JS to complete it.