[herpderperator]

Your Internet bandwidth is not relevant when talking about a compute-heavy backend like this. Wolfram|Alpha is not going to load any faster on a 1Gbps connection than it will on a 20Mbps connection, other than some static assets, but even that isn't going to be hugely noticeable if we're talking about 2ms RTT on fibre vs 8-20ms RTT on cable/DSL. If you're downloading a giant file off a nearby CDN, then sure, 1Gbps fibre is useful. I can max out my 1400Mbps cable connection downloading things this way (it's mind-blowing...), and my latency to my upstream gateway outside of my house is 8ms. But Wolfram|Alpha isn't going to load 40% faster for me than it will for you since it's I/O bound and your end-to-end latency is waiting for the backend to complete your request.

I will say, though, that Wolfram|Alpha could be "optimised" in the sense that it could do less fancy JS and be a simple box with a submit button, like SymPy Gamma.

[canadaduane]

I think that's the point. "My internet speed is fast enough that it is not the cause of slowness, so any delay is all on Wolfram|Alpha."

[tadfisher]

Throughput is not latency, though. 1gbps on a dedicated line is not the same as 1gbps on an oversubscribed residential node.

[vortico]

If I didn't include that note, someone would say "Is is slow because you're on 56kbps dial-up?"