Hey Mike,

This might be too simplistic, but a ping from the command prompt at your user's PC might shed some light. (That's what the kids do on their gaming PCs lol...)

It's not about the bandwidth.  The metrics that matter are latency, jitter, and packet loss.  You could have as little as 1mbps download speed and as long as the latency, jitter, and packet loss are great numbers it will perform really well.  When doing large downloads like video then the bandwidth matters, which is not the case for PB apps.

Run this tool: https://speed.cloudflare.com/

Ideally, you want the latency and jitter to be 60ms or less and zero packet loss.

Here are the numbers I'm getting on my Internet connection over WiFi.  Using ethernet cable should be even better.

Would it help to add a ping like option in the web api that just returns 'Success'. The client could track the time in milliseconds.

I use the following to track milliseconds:

Function ulong timeBeginPeriod ( ulong uPeriod ) Library "winmm.dll"
Function ulong timeEndPeriod ( ulong uPeriod ) Library "winmm.dll"
Function ulong timeGetTime ( ) Library "winmm.dll"

ULong lul_BeforeTime, lul_Elapsed

timeBeginPeriod(1)

lul_BeforeTime = timeGetTime()

... do stuff

lul_Elapsed = timeGetTime() - lul_BeforeTime

timeEndPeriod(1)