There are two main causes for so little data in Google Search Console:
You need to wait
Google Search Console often takes a week or two to show data when you first create a property. Even once a property is up and running, new data sometimes takes several days to become visible.
Your traffic isn't on that property
You may have added https://example.com
to Google Search Console, but Google is actually sending traffic to https://www.example.com
. Subdomains don't "roll up" in GSC, nor does HTTP to HTTPS. If you are missing traffic you should add all your variations as separate properties:
http://example.com
http://www.example.com
https://example.com
https://www.example.com
If you have other subdomains such as a blog, you will need to also add them separately: https://blog.example.com
For more information on this practice of adding many properties for your site, see Should I submit https:// and https://www in webmaster tools? and How do the combinations of http/https and naked/www in Google Search Console work?
Once you have all these properties added, you can create a single view in GSC that combines all of them. This is called a property set. Property sets will show most of the combined data from your individual properties, however some reports are not available against property sets.
Another way to get around the problem is to canonicalize your URLs. Choose a preferred version of your site and redirect all the other variations to it. Once you do so, Google will start sending all traffic to your preferred URL within a few weeks. Here are some instructions for various server configurations:
You could also use rel canonical link tag rather than redirects if it would be easier.
I don't think it is related to your problem, but you say you use <meta name="fragment" content="!">
. That is part of Google's AJAX crawling scheme which Google deprecated years ago. You should switch to normal crawling for your AJAX content now because Googlebot now ignores that meta tag. Googlebot is trying to crawl your content and render the JavaScript now anyway.