https://http2.golang.org/gophertiles?latency=200 https://http2.golang.org/gophertiles?latency=200 and https://http1.golang.org/gophertiles?latency=200 https://h

https://http2.golang.org/gophertiles?latency=200 https://http2.golang.org/gophertiles?latency=200 and https://http1.golang.org/gophertiles?latency=200 https://http1.golang.org/gophertiles?latency=200 perfectly demonstrate the issue I'd be facing otherwise. 200ms latency from the US West Coast to Europe is realistic, and the number of subresources being requested is also realistic for my application. If you don't believe the latency, try services like these: https://cloudpingtest.com/digital_ocean https://cloudpingtest.com/digital_ocean and https://pingtestlive.com/digitalocean-ping https://pingtestlive.com/digitalocean-ping