Your speed here reflects the actual loading time of data within your browser. With it's instantly apparent if there is a congested route. So, if you have to multithread your connection to get your full speed, you should be asking why that is. Multithreading can show that you're able to max out your connection by combining the speed of concurrent connections but a great connection can max out without having to multithread. Omitting the worst portion of your test resulting in inflated scores that may make you feel warm and fuzzy but aren't going to help you see and resolve connection issues. They often display your maximum throughput not your throughput over the course of an entire upload or download. Multithreaded speed tests, like the majority out there, are designed to benefit the Internet provider not the consumer.

Remember, you shouldn't have to multithread your connection to pull your full speed. but testing that way will not clue you in that there is actually a problem along the route. If you open more than one connection through that pipe you'll be able to achieve a faster speed. For instance, imagine that you have a pipe along your route that's limiting you to 10 Mbps. Meaning that they open more than one connection to the host and combine the speeds. Ookla speed tests are also multithreaded. Multithreading makes your connection look better Ookla is huge, most of the speed tests online run their software. Isn't THAT the data that you're here to see?Īlso note this isn't only true for. Throwing away the fastest 10% and slowest 30% of the results in my opinion does not make for an accurate test.

The remaining data is averaged together to determine the final result.The fastest 10% and slowest 30% of your results are DISCARDED.I want to explain something that may help you understand why this is.Īccording to the Ookla Wiki the following is true about your tests taken at. The most common question that people ask us is why their results here differ from.

Online internet speed test ookla