Why is vuejs.org not a SPA?

Question

Vue.js

I am learning vue.js. Naturally, imagining how I will always use SPA with server rendering from now on. But then I noticed that even the vuejs.org site itself is not a SPA.
In this regard, questions:
1. Why do you think vue.js.org was not made as a SPA? It's just a content site.
2. They say that SPA should not be used in online stores.
Why, if you can render on the server and indexing, in theory, should not suffer.
2. In what real cases is it worth doing a SPA, which ones are not worth it?
I don’t see any real reasons why not always write SPA

Answer 1

No matter how anyone tries to say that the search engines are friends with him - this is not so, not at all

Answer 2

Yes, we did a lot of shops at the SPA. The main problem is that the analytics and retargeting systems are buggy. Google Analytics and Metrica are losing referral sources, which is critical for partners involved in providing leads to an online store, because they usually take money for orders from store customers, and it is difficult for them to prove the source of the order (by utm tags). Also, a large load on a site with SSR (northern rendering) implies the organization of component caching, which is also not always easy.
If you have a regular content site, and there are no complex sales funnels, then you can use SPA, even without complex interfaces, since pages usually open faster (except for the very first one, if not SSR).

Answer 3

1. SPA is ( at the moment! ) user functionality after authorization: personal account, admin panel, statistics, etc.
2. Statics - for search engines with all the subtleties and their requirements for SEO.

Answer 4

Because there is a more productive solution for static content - generating a large number of static files

Answer 5

imagining how I will always use SPA from now on

Not spa alone. The spa niche is interfaces, where there is a lot of logic and Ajax.

Answer 6

It's simple, Google uses about 10 different engines for different cases. And they all behave strangely with large scripts (somewhere it even ran that the engine waits for about 10 seconds, and if the script does not finish its work, then it stupidly beats it) Here, for example, it is written that they, like, upgraded Googlebot to version 41
https:/ /www.google.com/amp/s/searchengineland.com/...
This is certainly good....but firstly, is it everywhere?)
And secondly, the crawler still does not like when the page is "rendered" after loading. This is the misfortune of most popular frameworks and the mistake of all novice programmers who, having studied some kind of framework, such as react, Vue, etc., sites start to bang and then it suddenly turns out that the page is not cached by the search engine ... and then they start shrugging their hands and chewing snot.

Answer 7

In Chrome, there is an Audits tab in the developer tools, where you can launch Lighthouse and check if your application is well recognized by the search engine, as well as get a lot of tips for improvement.

Answer 8

1. Why do you think vue.js.org was not made as a SPA? It's just a content site.

Here it is rather necessary to ask the question "why do it SPA?" The decoding of this abbreviation already has the answer.
"2. They say that SPA should not be used in online stores.
Why, if you can render on the server and indexing, in theory, should not suffer."
For this, the backend must be in js (as far as I know, there is no other solution without crutches yet). And this is not the best option and not suitable for everyone.
"2. In what real cases is it worth doing a SPA, which ones are not worth it?"
When you need interactive with dynamically changing content on the page (for which, in fact, this technology was invented).