How to measure the network performance

The following commands should be executed on the Indigo server and the destination should be the connected Devices. If there is any variation from a network point of view between the location of the various devices connecting to an Indigo Server, then they should be tested separately.
Windows
PS C:\Users\roland> ping -n 1000 -l 512 192.168.128.14

Pinging 192.168.128.14 with 512 bytes of data:
Reply from 192.168.128.14: bytes=512 time=1ms TTL=63
Reply from 192.168.128.14: bytes=512 time<1ms TTL=63
Reply from 192.168.128.14: bytes=512 time<1ms TTL=63
Reply from 192.168.128.14: bytes=512 time<1ms TTL=63
.
.
.
Reply from 192.168.128.14: bytes=512 time<1ms TTL=63
Reply from 192.168.128.14: bytes=512 time<1ms TTL=63
Reply from 192.168.128.14: bytes=512 time<1ms TTL=63

Ping statistics for 192.168.128.14:
Packets: Sent = 1000, Received = 1000, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 438ms, Average = 2ms
PS C:\Users\roland>

Linux
roland@roland-mbp1604:~$ ping -s 512 -v -c 1000 192.168.128.14
PING 192.168.128.14 (192.168.128.14) 512(540) bytes of data.
520 bytes from 192.168.128.14: icmp_seq=1 ttl=64 time=0.556 ms
520 bytes from 192.168.128.14: icmp_seq=2 ttl=64 time=0.407 ms
520 bytes from 192.168.128.14: icmp_seq=3 ttl=64 time=0.458 ms
.
.
.
520 bytes from 192.168.128.14: icmp_seq=998 ttl=64 time=0.395 ms
520 bytes from 192.168.128.14: icmp_seq=999 ttl=64 time=0.391 ms
520 bytes from 192.168.128.14: icmp_seq=1000 ttl=64 time=0.398 ms

--- 192.168.128.14 ping statistics ---
1000 packets transmitted, 1000 received, 0% packet loss, time 998997ms
rtt min/avg/max/mdev = 0.291/0.401/0.669/0.050 ms
roland@roland-mbp1604:~$

Assessment
There are two criteria that need to be evaluated from the results obtained.
Packet Loss – The percentage of lost packets between the devices and the Indigo server.
Maximum Latency – The Maxium Latency is the upper limit of 3 standard deviations (i.e. it will include 99.7% of all response times) from the average and can be calculated as
MaximumLatency=AverageLatency+(3"*" StandardDeviation)
The Average Latency is labeled as “avg” and the Standard Deviation is labeled as “mdev” in the ping results above.
For the Indigo Server to work reliably with the devices measured, the Packet Losses must be 0% and the measured Maximum Latency must not exceed 100ms. The lower the measured value of Maximum Latency, the more responsive and reliable the device will subjectively appear to be. Conversely the higher it is the worse the performance and the poorer the user experience.
Note that the sensitive data being sent from the Device through the Indigo server and to the iVeri Gateway is encrypted already and no benefit would be derived from running this data over additional VPN encryption. In fact, transporting the data over a VPN may increase latency by as much as 30% over and above the latency that would exist if a VPN was not used.