I've commented a similar question elsewhere, but what is a page view?
Is it an HTML request? It would need to be, otherwise sites will just spam AJAX requests in the background. But if we make it an HTML request, will that work with SPA architectures? If you paginate an article between 5 pages, is each of those a separate view? What if the page itself triggers a redirect or a refresh? Does that count?
Will this work for video/audio content? If I have two videos on the same page, will they get charged separately, or do I need another HTML request between them? Does the length of the video matter? What if I have auto-play on a playlist? Then as a site operator, I'm triggering the refresh and play myself, same as above, so does that count? If not, how do we allow users to autoplay a playlist of songs/videos while still paying the site?
How does this work for games? If someone leaves Cookie Clicker open for 15 hours, should that count as a single page view?
You can build different systems that tackle these problems differently. But that's exactly the problem. The problem with standardization is that you need a solution that works for everyone. Micropayments are interesting. I have my doubts about them, but they might be worth experimenting with. Building them directly into a browser is a bad idea.
If we're going to standardize anything, we should standardize the payments themselves. The biggest barrier to sites setting up their own micropayment systems is that web payments are still a horrible pain for both site operators and users. Web payments are insecure, come with prohibitive fees that make it difficult to collect that problem, and then allow the community to try out different payment models on its own until we understand the problem better.