Performance is always a loaded topic to discuss, if you're not using a common and agreed measurement approach. I recommend you start with this great article in Smashing Magazine
from Paul Irish & Paul Lewis (both in the Google Chrome team), as background material for that discussion.
It sounds to me as though you are probably quite early in your product development?
If so, I strongly recommend avoiding technical decisions like "which client side framework" for as long as possible, because client-side frameworks make it much easier to create technical debt that hurts you down the track. They seem easy to work with for trivial applications, but quickly develop unwieldy complexity in the hands of developers who have not previously built a complex app with the chosen framework.
Your user-validation needs can be much faster addressed using high-fidelity prototypes. (The new GV book "Sprint" is a fantastic testament to the power of prototyping... everyone in this forum should read it!) Make your prototype's data rich and meaningful, and get it in the hands of real users quickly. That will help you refine your UX/UI much faster than if you try to code it up.
Look at using the brand new Adobe XD
tool for early-stage product development. It will help you to very quickly get a clickable, high fidelity prototype into potential users' hands, and iterate your design fast. It's very easy to learn, quick to use, and makes it easy to generate mobile, tablet and desktop web-hosted prototypes for testing.
A good, well-tested prototype will also help you determine the framework that best suits the style of information architecture and general UX that you want to provide (if indeed a framework is really required!).
One last note: if you're not developing native mobile apps to begin with, then give serious thought to the disadvantages of the heavier client-side frameworks on a mobile phone (speed, maintenance). You may find it's faster to get to "beta" using a well-understood server-side framework that can easily be swapped out for client-side UI in the future (eg. Rails, MVC.net
). Server-side apps can still perform very well, and the reduced development overhead will keep your burn rate lower. And on less-powerful mobile devices, a single page load (with everything in-lined, which any server framework or decent build chain can do these days), will be MUCH faster than a client-side experience that has not been carefully crafted.
Hope that helps!