Or just do it the old fashioned way - have the server keep an access log, then use something like GoAccess (https://goaccess.io/) to produce reports from it. It’s not real-time reporting, but then you probably don’t need real-time reporting for your personal site anyway.
Alas, I don’t control my server, but if I did I would say you might not even need this. If you’re using Google Analytics right now it’s probably better than that, though.
I too don't controll my server, but it turned out that my hosting provider (one.com) has pretty nice access analytics, e̶v̶e̶n̶ ̶f̶o̶r̶ ̶t̶h̶e̶ ̶p̶r̶o̶j̶e̶c̶t̶s̶ ̶I̶ ̶h̶a̶v̶e̶ ̶w̶h̶e̶r̶e̶ ̶o̶n̶e̶.̶c̶o̶m̶'̶s̶ ̶o̶n̶l̶y̶ ̶r̶o̶l̶e̶ ̶i̶s̶ ̶D̶N̶S̶ ̶r̶e̶d̶i̶r̶e̶c̶t̶ ̶t̶o̶ ̶a̶ ̶c̶h̶e̶a̶p̶ ̶V̶P̶S̶ (Edit:Nope it does not, how could it). When I discovered this I dropped GA for most of my projects. I have one remaining project that still uses GA but only bcs I haven't gotten around to fix it. Maybe your hosting provider has analytics too? I had to poke around in the dashboard for one.com to find it.