Couple of things to note here - the performance tab constantly updates, so every time you perform an action or render new elements to the screen then the scoring changes.
If your app is making 83 queries on load (ie without any user interaction) then that's something you should look at investigating right away.
eg If you've pressed a "save" button 80 times then I wouldn't be too concerned.
I'd first recommend you refresh your app and see what the performance score is before interacting with it.
Second is the slowness of the queries. Anything over a few seconds for a very complex query is something you should seek to investigate and remove/resolve.
20+ seconds for your get queries sounds very slow - I'd try to optimise those queries, simplify them where possible and load only what's needed, investigate the database itself and look at adding indexes, I'd also look at what could be cached too.
In terms of implications this will have a very negative effect on user experience if the app feels slow/unresponsive. You'll likely get complaints or people won't use it or they'll click randomly to make it work faster and cause more problems.
Lastly, I wouldn't put too much faith in the Performance number itself - it's a guide to help you optimise you app and identify where the slowest queries are and biggest performance bottlenecks are.
Ultimately you should be testing this with your users to get their feedback and understanding their expectations in terms of what good performance looks like to them.