Oh 😊
I hadn't look at the tests in awhile. Seems like they have gone from usesfull to adware. I'll have to look for better tests.
as tests ( we want to try to narrow down where the problem lays ) :
1) You could move your computer closer to the wifi router to see if that improves the situation. like right next too.
2) You could try an ethernet cable connection. This would show the effect of the wireless router.
You could try a simple ping test:
Macintosh-HD -> Applications -> Utilities -> Terminal
# ping google 20 time.
# you can vary the number. control + c to quit right now.
# you type in ping -c20 google.com
# then press return
# my packet loss is high!
mac $ ping -c20 google.com
PING google.com (74.125.113.104): 56 data bytes
64 bytes from 74.125.113.104: icmp_seq=1 ttl=53 time=29.563 ms
64 bytes from 74.125.113.104: icmp_seq=2 ttl=53 time=29.206 ms
64 bytes from 74.125.113.104: icmp_seq=3 ttl=53 time=29.252 ms
64 bytes from 74.125.113.104: icmp_seq=6 ttl=53 time=30.248 ms
64 bytes from 74.125.113.104: icmp_seq=7 ttl=53 time=30.481 ms
64 bytes from 74.125.113.104: icmp_seq=9 ttl=52 time=31.183 ms
64 bytes from 74.125.113.104: icmp_seq=11 ttl=53 time=29.200 ms
64 bytes from 74.125.113.104: icmp_seq=13 ttl=53 time=32.679 ms
64 bytes from 74.125.113.104: icmp_seq=14 ttl=53 time=31.073 ms
64 bytes from 74.125.113.104: icmp_seq=16 ttl=53 time=29.097 ms
64 bytes from 74.125.113.104: icmp_seq=17 ttl=53 time=30.461 ms
64 bytes from 74.125.113.104: icmp_seq=18 ttl=52 time=48.536 ms
64 bytes from 74.125.113.104: icmp_seq=19 ttl=53 time=31.683 ms
--- google.com ping statistics ---
20 packets transmitted, 13 packets received, 35% packet loss
round-trip min/avg/max/stddev = 29.097/31.743/48.536/4.961 ms
mac $
Robert