Dan Romero
@dwr.eth
Curious if React folks here have strong thoughts on SSR vs. SPA?
16 replies
0 recast
0 reaction
borodutch @ lunchbreak.com
@farcasteradmin.eth
ssr is plain stupid users have supercomputers in their hands do not outsource computing to centralized machines also makes cdn's less effective (as opposed to serving lightweight spa) crawlers run js now, for the ones who don't you can use prerender libs
2 replies
0 recast
0 reaction
Dan Romero
@dwr.eth
Your favorite prerender lib? Does Google really not care about the page needing to load? Would imagine that impacts SEO somewhat? cc @zachroth.eth
4 replies
0 recast
0 reaction
zach roth
@zachroth.eth
prerender.io I've used use a lot, they're getting better about it. As google tends to do. The best thing ever is having those super lightweight, ssr versions of pages cached for googlebot to hit. Butter all the way down.
0 reply
0 recast
0 reaction
Stas
@stas
https://docs.netlify.com/site-deploys/post-processing/prerendering/ It's been in beta for over a year kek
0 reply
0 recast
0 reaction
davisshaver.eth
@davisshaver
Google penalizes render-blocking JS, so there’s some inherent risk with this approach, although it’s not the case that your content would be undiscoverable anymore. JS-reliant sites also index more slowly than ones with HTML response w/ page content from server
0 reply
0 recast
0 reaction
borodutch @ lunchbreak.com
@farcasteradmin.eth
the impact is insignificant (until proven otherwise) react-spa-prerender is good enough :)
0 reply
0 recast
0 reaction
