The intent of Big Objects is not to be used as Transactional data. They are more intended towards holding very large data volumes. This excerpt below from trailhead explains it the best way:
Big objects allow you to store and manage a massive amount of data on the Salesforce platform. How massive, you ask?
A thousand records? No, think bigger.
A hundred thousand? Bigger!
A million? Not even close!
Big objects provide consistent performance for a billion records or
Also Big Objects do not support full SOQL commands, but only a subset of it.
You can query big objects using a subset of standard SOQL commands
Futhermore, if you look the same trailhead, it mentions:
To support the scale of data in a big object, you can’t use triggers, flows, processes, and the Salesforce app.
So that kind of summarizes that Big Objects are not to be used anything else than they are intended for.
You definitely should not be looking to consider Big Object for sake of VF performance considering what they are intended for and that what VF page is capable of, there's definitely no real connection here.
A VF performance has much more than data, it's how you design it. And there are resources for improving VF performance, which you can always refer to. You should look towards Query Plan tool to review any queries that you may be using on your VF and improve performance there as well.