The first two tests (Ookla and nPerf) run their tests multi-threaded by default, i.e. they typically make around 8 simultaneous connections to the test server to try to saturate the connection. Ookla has a lot of test servers within the ISP networks, so there is a good chance your test traffic is not leaving their network unless you manually choose another server.
To get a multithread test here on TestMy, click the "Multithread off" at the top-right to turn it on. Note that multithreaded tests don't realistically show what you would get streaming or downloading, which generally run over a single connection from the server.
Google's built-in speed test is a single connection speed test (not multithreaded), but uses the new TCP BBR congestion protocol. The TCP BBR congestion protocol is excellent at handling packet loss up to about 5% before it suffers significant speed loss. As web servers don't have BBR enabled (or installed) by default, most websites use the legacy TCP CUBIC congestion protocol. For this reason, TestMy does not use TCP BBR, apart from the Colorado Springs server at this time. A few major web hosts such as Google and Microsoft and CDNs such as Cloudflare are TCP BBR enabled.
As Google's speed test uses Measurement Lab's servers, you can see how your speed compares with the widely used TCP CUBIC congestion protocol that Measurement Lab uses on its own website test:
https://speed.measurementlab.net/#/
If the "Retransmission" figure is not zero, there is a some packet loss on your connection. If the speed is close to the 80Mbps what you got on Google, then your ISP may have congestion on its peering with international links as TestMy does not have any test servers in Italy.