EDGE Speed tests, As promised.
Sorry..a bit late on this as i had some Real Life stuff to tend to.
Anyway...here we go.
First, the test environment:
These tests were done from a fixed location within 50 Miles of Washington, DC, over ATT's EDGE Data Network, via a tethered Samsung Blackjack locked to the 850 Mhz GSM Band.
All web tests were done from cache cleaned cold single run and loads of Safari 3 beta on 10.4.9. When i say cache cleaned. I mean it. There was no Safari cache on the disk; safari had to create the cache folders for every site. After each site was loaded, I quit safari, erased the safari caches via the finder, and emptied the trash.
Nothing was "turned off"; these are fully loaded sites...all the crap flash, the ads, javascripts etc.
So with all that out of the way...some numbers:
Apple.com 17 seconds
Apple.com 19 seconds <- so nice, i had to do it again. They do great HTML!
yahoo.com 20 seconds
nytimes.com 47 seconds <--full of ads and flash crap. what is going on there?!
digg.com/apple 27 seconds
Additionally, I ran the Speakeasy Speedtests:
http://www.speakeasy.net/speedtest/
Washington DC
Download Speed: 238 kbps (29.8 KB/sec transfer rate)
Upload Speed: 81 kbps (10.1 KB/sec transfer rate)
NY, NY
Download Speed: 169 kbps (21.1 KB/sec transfer rate)
Upload Speed: 77 kbps (9.6 KB/sec transfer rate)
Atlanta
Download Speed: 134 kbps (16.8 KB/sec transfer rate)
Upload Speed: 68 kbps (8.5 KB/sec transfer rate)
Chicago
Download Speed: 216 kbps (27 KB/sec transfer rate)
Upload Speed: 74 kbps (9.3 KB/sec transfer rate)
Dallas
Download Speed: 185 kbps (23.1 KB/sec transfer rate)
Upload Speed: 22 kbps (2.8 KB/sec transfer rate)
LA
Download Speed: 224 kbps (28 KB/sec transfer rate)
Upload Speed: 74 kbps (9.3 KB/sec transfer rate)
San Fran
Download Speed: 213 kbps (26.6 KB/sec transfer rate)
Upload Speed: 78 kbps (9.8 KB/sec transfer rate)
Seattle
Download Speed: 166 kbps (20.8 KB/sec transfer rate)
Upload Speed: 75 kbps (9.4 KB/sec transfer rate)
Latency is a factor often in speeds...so lets look at some numbers there. people like...numbers:
Ping latency to apple.com
PING apple.com (17.254.3.183): 56 data bytes
64 bytes from 17.254.3.183: icmp_seq=0 ttl=241 time=693.804 ms
64 bytes from 17.254.3.183: icmp_seq=1 ttl=241 time=414.703 ms
64 bytes from 17.254.3.183: icmp_seq=2 ttl=241 time=332.706 ms
64 bytes from 17.254.3.183: icmp_seq=3 ttl=241 time=315.609 ms
64 bytes from 17.254.3.183: icmp_seq=4 ttl=241 time=312.536 ms
64 bytes from 17.254.3.183: icmp_seq=5 ttl=241 time=374.499 ms
64 bytes from 17.254.3.183: icmp_seq=6 ttl=241 time=315.511 ms
64 bytes from 17.254.3.183: icmp_seq=7 ttl=241 time=312.466 ms
^C
--- apple.com ping statistics ---
8 packets transmitted, 8 packets received, 0% packet loss
round-trip min/avg/max/stddev = 312.466/383.979/693.804/122.083 ms
google.com
PING google.com (64.233.167.99): 56 data bytes
64 bytes from 64.233.167.99: icmp_seq=0 ttl=243 time=359.067 ms
64 bytes from 64.233.167.99: icmp_seq=1 ttl=243 time=300.974 ms
64 bytes from 64.233.167.99: icmp_seq=2 ttl=243 time=319.822 ms
64 bytes from 64.233.167.99: icmp_seq=4 ttl=243 time=258.598 ms
64 bytes from 64.233.167.99: icmp_seq=5 ttl=243 time=278.440 ms
64 bytes from 64.233.167.99: icmp_seq=6 ttl=243 time=298.387 ms
64 bytes from 64.233.167.99: icmp_seq=7 ttl=243 time=359.281 ms
64 bytes from 64.233.167.99: icmp_seq=8 ttl=243 time=319.170 ms
64 bytes from 64.233.167.99: icmp_seq=9 ttl=243 time=298.159 ms
^C
--- google.com ping statistics ---
11 packets transmitted, 9 packets received, 18% packet loss
round-trip min/avg/max/stddev = 258.598/310.211/359.281/31.642 ms
yahoo.com
PING yahoo.com (66.94.234.13): 56 data bytes
64 bytes from 66.94.234.13: icmp_seq=0 ttl=46 time=378.373 ms
64 bytes from 66.94.234.13: icmp_seq=1 ttl=46 time=356.381 ms
64 bytes from 66.94.234.13: icmp_seq=2 ttl=46 time=376.343 ms
64 bytes from 66.94.234.13: icmp_seq=3 ttl=46 time=359.245 ms
64 bytes from 66.94.234.13: icmp_seq=4 ttl=46 time=336.109 ms
64 bytes from 66.94.234.13: icmp_seq=5 ttl=46 time=357.052 ms
64 bytes from 66.94.234.13: icmp_seq=6 ttl=46 time=357.953 ms
64 bytes from 66.94.234.13: icmp_seq=7 ttl=46 time=377.831 ms
64 bytes from 66.94.234.13: icmp_seq=8 ttl=46 time=356.776 ms
^C
--- yahoo.com ping statistics ---
9 packets transmitted, 9 packets received, 0% packet loss
round-trip min/avg/max/stddev = 336.109/361.785/378.373/12.917 ms
digg.com
PING digg.com (64.191.203.30): 56 data bytes
64 bytes from 64.191.203.30: icmp_seq=0 ttl=237 time=378.475 ms
64 bytes from 64.191.203.30: icmp_seq=1 ttl=237 time=320.362 ms
64 bytes from 64.191.203.30: icmp_seq=2 ttl=237 time=316.230 ms
64 bytes from 64.191.203.30: icmp_seq=3 ttl=237 time=360.066 ms
64 bytes from 64.191.203.30: icmp_seq=4 ttl=237 time=355.990 ms
64 bytes from 64.191.203.30: icmp_seq=5 ttl=237 time=357.879 ms
64 bytes from 64.191.203.30: icmp_seq=6 ttl=237 time=357.027 ms
64 bytes from 64.191.203.30: icmp_seq=7 ttl=237 time=334.989 ms
^C
--- digg.com ping statistics ---
8 packets transmitted, 8 packets received, 0% packet loss
round-trip min/avg/max/stddev = 316.230/347.627/378.475/20.182 ms
Wow.
So really, there is a lot of hyperbole...a lot of exaggeration.
I suppose next to your fancy cablemodem speeds, this might seem "like dialup"...but dialup is in fact MUCH slower than this. Its been so long since most tech saavy people have USED dialup that i think they forget how slow it *really* is
Hopefully this is helps