I am left wondering: Why not just measure/compare the response time of the single request that fetches the (presumably) HTML response, and leave all of the anc

I am left wondering: Why not just measure/compare the response time of the single request that fetches the (presumably) HTML response, and leave all of the ancillary asset delivery and script execution as an aside? If this is about Go versus Python, all I care about is the portion where those are actually involved. And it would be easy to see in the network panel of the developer tools window in Chrome or Firefox. Of course, the hosting environment also changed, so... there's that still.