If one of them was better and faster, why would the other two exist and be used?

Maybe the world is not this simple and there isn't one that's better for "a large scale website"...

Hello One Hat2,

Is the question 'Best and Fast' for,

1. Developers and development cycle? Or,
2. For Users as a web application running on Browsers?

If it is for #1,

• I would go for ReactJs as the learning curve is lesser and fundamental JavaScript Concept wins over some Framework's proprietary. It means, a developer with fair knowledge of JavaScript fundamentals can develop, maintain application with ease and can resolve bugs with lesser ambiguities.

If it is for #2,

• I wouldn't go for either of them simply because of the fact that, all uses DOM Diffing as the mechanism to find what has changed and update it accordingly at the Runtime. This itself cause a worry that, it is possibly not the best way to serve the fundamental of Reactive Programming.
• Not upsetting the reactjs lovers(including myself) but, it is acceptable that,
  twitter.com/dan_abramov/status/1025801430668664833
• There are thought processes to address this and we are already hearing the buzz like, SvelteJs. It helps doing thing at the build time than the runtime. Worth giving it a try and read about the thought of doing it differently.

[X] None of them.

First of all, did you check your requirements against the problems solved by these frameworks / libraries and how they work? All of them are made for dynamically creating components and manipulating the DOM at runtime. Do you need to do so? For a website, the answer is NO most of the time. They are useful for web apps, though.

For websites, you usually want to support people, who disabled JS, people with screen-readers, bots which cannot use JS, etc. - there might even be legal requirements to support accessibility! Also, you usually want high performance and most likely low costs and low battery drainage on mobile. As a conclusion, write a static website, which is assembled at build-time, not at run-time (either on server or client). Reduce the client-js and try to keep the server from doing any calculations. Optimize all resources, which is way easier with static resources. Then upload your site and enjoy. It's greener, too, btw 🌻

Even for a big-scale website, going static is very viable and does not mean that you have to write out everything by hand and repeat your code like it's the early days of the internet. For example, if you need templating, I recommend using pug or handlebars, which can be used by most packers and results in the correct static html.

React js is fast as compare to AngularJS . I didn't work on VueJS so I don't have much idea .