That was like Running maps locally. My first guess was it must be serving from some super local cdn cache. So tried looking for the data serving domain. It feel

That was like Running maps locally. My first guess was it must be serving from some super local cdn cache. So tried looking for the data serving domain. It feels even more awesome after looking at latency number. This is loading all data from maps.wikimedia.org. Tracing route to maps.wikimedia.org [103.102.166.240] over a maximum of 30 hops: 1 <1 ms 3 ms 2 ms 192.168.1.1 2 7 ms 6 ms 6 ms abts-north-static-076.220.160.122.airtelbroadband.in [122.160.220.76] 3 8 ms 5 ms 9 ms 125.17.2.173 4 7 ms 10 ms 6 ms 182.79.181.72 5 51 ms 51 ms 65 ms 182.79.149.237 6 47 ms 50 ms 47 ms 182.79.198.2 7 73 ms 73 ms 72 ms 182.79.224.181 8 73 ms 73 ms 72 ms 14907.sgw.equinix.com [27.111.228.186] 9 79 ms 79 ms 93 ms upload-lb.eqsin.wikimedia.org [103.102.166.240] Now Google Maps seems to be serving all data from root domain www.google.co.in. So here we go. Tracing route to www.google.co.in [172.217.167.35] over a maximum of 30 hops: 1 <1 ms 1 ms 1 ms 192.168.1.1 2 8 ms 5 ms 6 ms abts-north-static-076.220.160.122.airtelbroadband.in [122.160.220.76] 3 6 ms 6 ms 5 ms 125.18.20.57 4 10 ms 7 ms 6 ms 72.14.205.93 5 42 ms 44 ms 42 ms 108.170.251.113 6 8 ms 7 ms 14 ms 72.14.234.117 7 8 ms 7 ms 7 ms del03s16-in-f3.1e100.net [172.217.167.35] So even after getting additional latency penalty of ~60ms, it still feels snappier! Imaging it could be even more faster with local CDN nodes. 60ms = ~3 Frames on 60Hz Monitor refresh rate.