Sir, please allow me to say that an SPA’s fast first-page load is fully dependent on the developer and less on the technology.
I think it is needless to say that if this is mobile … desktop hits the 100%.
The concern is not how fast the first page comes up, there are so many tricks to tune that.
When you think Meteor speed you would normally ask these questions:
- Is my tech (virtual hardware) optimized for the number of users and data consumption. How much this costs me vs other tech. Is it fast for the buck?
- Did I write my code right and I don’t pull 1GB of data from Mongo to … send an email.
- Is my platform secure and I don’t have traffic leaks, exploits or DOS issues.
- Is my media optimized and cached to the max.
- Are all my methods effective and efficient.
- Do I pipe my data to the view efficiently.
- Did I cut down all unnecessary reactivity.
List can go one for some time…
It is useless to load a page in 1 second if your data comes in 5 or at times, never.
If you want to show your name in HTML, nothing is faster than … HTML. If you want infrastructure, full stack, DB, mobile etc wondering about the speed of the view layer is possibly less than 1% of the real speed concern.
If you are new to webdev, learning Blaze is like learning Papuan… You will get very good at it but you won’t find too many people to joke with or things to joke about. My personal opinion is that React is the most supported, fastest to learn, has huge NPM base of literally everything you might think of and involuntarily you learn React-Native.
To answer your question: Meteor is very fast. Especially when Node sits in the same cluster with Mongo and has global availability/replication. It is really fast if you don’t put 1000 users on a EC2 Nano and then run to the Meteor Forum to complain about how bad Meteor is and how your processors burn at 100% … and you … ask your money back from the people who pushed code to the Meteor version you’re running on. Ok … stop kidding now. It is fast. If you want to run a movie in a browser and refresh the DOM for every video frame at 60 fps and only display frames with beautiful ladies and out of those, only blondes then sort the frames by cup size right before they render … you might want to run a comparison between Blaze, Laravel and something else. Then do the comparison for mobile frameworks, browsers… native or hybrid, Iphone is the best but Huawei sells better than Samsung unless you want the Samsung Pay and you can let go that onscreen fingerprint scanner from some Nokia … and the pink case. Here I officially stop kidding.
It is fast.