If your app starts with a loading spinner, then fetches content via Ajax, the crawler will not wait for you to finish. Unified mental model: you get to use the same language and the same declarative, component-oriented mental model for developing your entire app, instead of jumping back and forth between a backend templating system and a frontend framework.īetter SEO: the search engine crawlers will directly see the fully rendered page.Īs of now, Google and Bing can index synchronous JavaScript applications just fine. This generally results in improved Core Web Vitals metrics, better user experience, and can be critical for applications where time-to-content is directly associated with conversion rate. In addition, data fetching is done on the server-side for the initial visit, which likely has a faster connection to your database than the client. ![]() 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. Why SSR? Ĭompared to a client-side Single-Page Application (SPA), the advantage of SSR primarily lies in:įaster time-to-content: this is more prominent on slow internet or slow devices. However, it is also possible to render the same components into HTML strings on the server, send them directly to the browser, and finally "hydrate" the static markup into a fully interactive app on the client.Ī server-rendered Vue.js app can also be considered "isomorphic" or "universal", in the sense that the majority of your app's code runs on both the server and the client. ![]() By default, Vue components produce and manipulate DOM in the browser as output. Vue.js is a framework for building client-side applications.
0 Comments
Leave a Reply. |