From be7d12d98d717c46092d564b4666d5d27397891f Mon Sep 17 00:00:00 2001 From: Sven Wagner Date: Mon, 8 Jun 2020 11:50:22 +0200 Subject: [PATCH] docs(ssr): add "better smo" as a reason --- docs/README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/README.md b/docs/README.md index f6d8406c..e5f80466 100644 --- a/docs/README.md +++ b/docs/README.md @@ -24,6 +24,8 @@ Compared to a traditional SPA (Single-Page Application), the advantage of SSR pr Note that as of now, Google and Bing can index synchronous JavaScript applications just fine. Synchronous being the key word there. If your app starts with a loading spinner, then fetches content via Ajax, the crawler will not wait for you to finish. This means if you have content fetched asynchronously on pages where SEO is important, SSR might be necessary. +- Better SMO, as the majority of social media crawlers do not execute JavaScript and therefore they do not see the fully rendered page. + - Faster time-to-content, especially on slow internet or slow devices. Server-rendered markup doesn't need to wait until all JavaScript has been downloaded and executed to be displayed, so your user will see a fully-rendered page sooner. This generally results in better user experience, and can be critical for applications where time-to-content is directly associated with conversion rate. There are also some trade-offs to consider when using SSR: