Download and upload
Megabits versus megabytes, why upload is usually lower, and what your plan's advertised speed really promises.
Wi-Fi speed, measured properly
One fair test on cable and one on Wi-Fi answers most slow-connection questions. We explain how to run both, read the numbers, and fix the part that is actually slow.
What we cover
Megabits versus megabytes, why upload is usually lower, and what your plan's advertised speed really promises.
Why a 500 Mbps line can still feel slow on a video call, and which numbers matter for gaming and calls.
2.4 GHz, 5 GHz and 6 GHz, walls and distance: the physical reasons Wi-Fi loses speed.
Mesh nodes, wired access points, channel changes and bufferbloat settings, ranked by how often they actually help.
How to test
Plug a laptop into the router. That result is the ceiling your internet plan actually delivers.
Repeat on Wi-Fi in the same room. The gap between the two is what your Wi-Fi costs you at best.
Repeat in the problem room. A big drop here points at coverage, not at your provider.
Plans advertise the speed delivered to the router over a wired connection. Wi-Fi, device limits, busy hours and the test server all subtract from it.
Under about 50 ms to a nearby server is comfortable for most calls and games; steady latency with low jitter matters more than raw download speed.
Insights
Feature
Run a fair Fortify router speed test over Ethernet and Wi-Fi, compare VPN-on results, and identify coverage, device, or internet-path limitations.
Feature
Compare your phone and laptop fairly, check Wi-Fi bands and device limits, and find out whether the slowdown is coverage, software or your internet connection.
Feature
Compare quiet and busy Wi-Fi using throughput, loaded latency and jitter. Separate congestion gains from internet-plan limits and router marketing.
Most bad results come from how the test was run. Fix the method first, then fix the network.
Testing guide