Skip to content

Commit 996935c

Browse files
Update content/tutorial/02-sveltekit/01-concepts/04-server-side-rendering/README.md
Co-authored-by: Rich Harris <hello@rich-harris.dev>
1 parent 78e3c89 commit 996935c

File tree

1 file changed

+1
-1
lines changed
  • content/tutorial/02-sveltekit/01-concepts/04-server-side-rendering

1 file changed

+1
-1
lines changed

content/tutorial/02-sveltekit/01-concepts/04-server-side-rendering/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,4 +4,4 @@ title: Server-side rendering
44

55
Server-side rendering (SSR) is the generation of HTML on the server. It's what SvelteKit does by default for the initial page load when a user visits your site.
66

7-
SSR is generally preferred for SEO (search engine optimization). While some search engines can index content that is dynamically generated on the client-side it may take longer even in these cases. It also tends to improve perceived performance and makes your app accessible to users if JavaScript fails or is disabled (which happens [more often than you probably think](https://kryogenix.org/code/browser/everyonehasjs.html)).
7+
SSR tends to improve performance and makes your app accessible to users if JavaScript fails or is disabled (which happens [more often than you probably think](https://kryogenix.org/code/browser/everyonehasjs.html)). It is also preferred for search engine optimization (SEO) — while some search engines can index content that is rendered in the browser with JavaScript, it happens less frequently and reliably.

0 commit comments

Comments
 (0)