This is all explained earlier in the threas, but again:speedtest.net is hard to understand. I tested my iphone and on my macbook and ill get 13.01 on my iphone and 13.50 on download on mac. then ill get like 60 upload and 20 upload on my mac, but then it will vary sometimes on teh phone to 8. but the speed test app will start freezing. so idk is there another app.
When you run speedtest, the app randomly picks a server in your area. Some servers are much faster than others. In my area, there are three speedtest servers. One of these servers reliably returns 70+Mbps with 30-40ms pings. Another of these servers reliably returns 30-40Mbps with 100ms pings. The last of these servers returns anywhere from 0.5 to 5Mbps with 200-400ms pings. Thus, my results vary from 0.5Mbps to 70Mbs if I let the Speedtest app choose the server. I only get consistent results when I manually pick a server for each test. If your results are bad, pick another server.
Don't jump to conclusions about your Wifi performance before duplicating your results on multiple servers. Several people who thought their iPhone was defective found that performance was normal when they switched servers.
IMO, virtually all other WiFi issues mentioned in this thread are software and/or driver configuration setting issues on the iPhone5, and most people are returning perfectly fine, non-defective phones. I've beta tested a number of Wifi devices in the past and have observed very similar issues in the past caused by firmware/driver bugs, all of which were fixed by new software. Numerous members on this forum and others have resolved their Wifi issues by changing a setting on a router, rebooting or resetting their router, resetting their iPhone, and/or setting up from scratch without restoring an iPhone 4/4S backup, all of which provides further evidence that this is a software issue
I fully expect that Apple will figure out the common causes soon and fix/prevent the issue in IOS 6.0.1. If your phone is perfect in all other respects, consider giving Apple 2-3 weeks to address the issue.
Last edited: