I've been having a similar problem. I have a macbook pro and an imac wirelessly connected to an airport extreme. Wifi has been ridiculously slow. It's most noticeable when I vpn to my office.
I also have an Ipad which has no such problem.
I've also tested a windows 7 dell laptop which has no such problem.
When I ping sites on the internet from my os x based machines I get weird results:
22 packets transmitted, 22 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 40.611/44.454/57.633/3.972 ms
PING google.com (72.14.204.99): 56 data bytes
64 bytes from 72.14.204.99: icmp_seq=0 ttl=52 time=99.759 ms
64 bytes from 72.14.204.99: icmp_seq=1 ttl=52 time=86.335 ms
64 bytes from 72.14.204.99: icmp_seq=2 ttl=52 time=88.539 ms
64 bytes from 72.14.204.99: icmp_seq=3 ttl=52 time=91.235 ms
64 bytes from 72.14.204.99: icmp_seq=4 ttl=52 time=93.570 ms
Request timeout for icmp_seq 5
Request timeout for icmp_seq 6
64 bytes from 72.14.204.99: icmp_seq=5 ttl=52 time=2317.631 ms
64 bytes from 72.14.204.99: icmp_seq=7 ttl=52 time=362.760 ms
64 bytes from 72.14.204.99: icmp_seq=6 ttl=52 time=1363.402 ms
64 bytes from 72.14.204.99: icmp_seq=8 ttl=52 time=89.956 ms
64 bytes from 72.14.204.99: icmp_seq=9 ttl=52 time=86.357 ms
64 bytes from 72.14.204.99: icmp_seq=10 ttl=52 time=87.937 ms
64 bytes from 72.14.204.99: icmp_seq=11 ttl=52 time=87.338 ms
64 bytes from 72.14.204.99: icmp_seq=12 ttl=52 time=2773.686 ms
64 bytes from 72.14.204.99: icmp_seq=14 ttl=52 time=774.026 ms
64 bytes from 72.14.204.99: icmp_seq=13 ttl=52 time=1780.854 ms
64 bytes from 72.14.204.99: icmp_seq=15 ttl=52 time=90.377 ms
64 bytes from 72.14.204.99: icmp_seq=16 ttl=52 time=91.837 ms
64 bytes from 72.14.204.99: icmp_seq=17 ttl=52 time=86.873 ms
^C
But I accidentally stumbled on the culprit. It's Safari. When Safari is running the results are as above. When it is not running, and I'm using Chrome instead, they are normal. See below:
PING google.com (72.14.204.147): 56 data bytes
64 bytes from 72.14.204.147: icmp_seq=0 ttl=52 time=94.843 ms
64 bytes from 72.14.204.147: icmp_seq=1 ttl=52 time=90.850 ms
64 bytes from 72.14.204.147: icmp_seq=2 ttl=52 time=91.552 ms
64 bytes from 72.14.204.147: icmp_seq=3 ttl=52 time=89.295 ms
64 bytes from 72.14.204.147: icmp_seq=4 ttl=52 time=90.897 ms
64 bytes from 72.14.204.147: icmp_seq=5 ttl=52 time=88.600 ms
64 bytes from 72.14.204.147: icmp_seq=6 ttl=52 time=87.067 ms
64 bytes from 72.14.204.147: icmp_seq=7 ttl=52 time=91.147 ms
64 bytes from 72.14.204.147: icmp_seq=8 ttl=52 time=98.988 ms
64 bytes from 72.14.204.147: icmp_seq=9 ttl=52 time=86.064 ms
64 bytes from 72.14.204.147: icmp_seq=10 ttl=52 time=98.218 ms
64 bytes from 72.14.204.147: icmp_seq=11 ttl=52 time=89.104 ms
^C
--- google.com ping statistics ---
12 packets transmitted, 12 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 86.064/91.385/98.988/3.887 ms
I can replicate these results at will. Something is definitely wrong with Safari as installed on my macs. My solution is stop using Safari and make sure it is not running at all.
Maybe the same will work for you.
