Wi-Fi link speed vs internet speed: what Windows is showing

Windows can show Receive rate and Transmit rate values in Mbps that look much higher than a browser speed test or a file download. That difference does not automatically mean your internet service is failing. The Wi-Fi rate describes the radio link between your PC and router; a speed test reports data transferred between your device and a chosen test server across the whole route. They are useful clues, but they are not two readings that should match. This documentation-based guide offers a comparison method, not a Jitsumi measurement.

The Wi-Fi rate and the speed test measure different things

The Wi-Fi link rate is also called a physical-layer, or PHY, rate. It describes how quickly the Wi-Fi client and access point can exchange data over their radio link. A download or speed-test result is useful application data that made it through Wi-Fi, the router and the rest of the network. Wi-Fi overhead and retransmissions reduce the share available for that useful data, and the link rate itself can vary with the wireless mode, distance and interference. NETGEAR Support (2025/07), “WiFi Link Rate and Transfer Speed”

The speed-test number is not a direct reading of that radio link. A test sends data to its own server, and results can change with the server location and the test's method. For a fair comparison, use the same test service and, if it lets you choose, the same server each time. Cloudflare Blog (2025/10), “How does Cloudflare’s Speed Test really work?”

Units can add another apparent mismatch. Mbps means megabits per second; MB/s means megabytes per second. Eight bits make one byte, so a file transfer showing 10 MB/s is roughly 80 Mbps before accounting for how the app measures and reports its own transfer. This is a unit conversion, not a promise that a speed test should return the same number. NETGEAR Support (2025/07), “WiFi Link Rate and Transfer Speed”

Check the Wi-Fi link in Windows

On Windows 10 or 11, open Command Prompt and run this read-only command:

netsh wlan show interfaces

Microsoft documents netsh wlan show interfaces for listing wireless interfaces. In a typical connected interface report, look for State, Receive rate (Mbps), Transmit rate (Mbps) and Signal. Cisco's troubleshooting example shows these fields in a Windows output; driver and Windows versions can change how details are presented. Microsoft Learn (2025/10), “netsh wlan” ; Cisco Support, “Troubleshoot Wireless Speed Issues,” p. 2

Check that State says connected and that you are reading the Wi-Fi adapter you are using. Receive and transmit rates describe opposite directions and may differ. Treat them as connection details, not as the result a download must reach. A signal percentage is not a percentage of your internet plan; compare it only as one clue when the same PC changes location.

The output can also include your network name, access-point identifier and adapter address. Redact those details before sharing the report publicly.

Compare the readings without changing several things

1. Record your usual spot. Keep the PC where the slow result normally happens. Run the command and note the receive rate, transmit rate and signal. Then run your chosen speed test while other large transfers are paused. Record the download and upload results, test server and location.
2. Repeat in the same spot. Run the same test again, especially if the first result looks unusual. If results vary, look for a pattern across runs instead of drawing a conclusion from one reading.
3. Move closer to the main router. Keep the PC and speed-test service the same; change only its position. Run the command and test again. A stronger link and a higher test result together suggest that the wireless path or the room's conditions are contributing. They do not identify one exact cause.
4. If practical, compare with Ethernet. Connect the same PC directly to the main router, turn off Wi-Fi for the comparison, then repeat the same speed test. If Ethernet repeatedly gives a higher result, the wireless path is a plausible part of the difference. A cable connected to a mesh point that itself uses Wi-Fi still leaves a wireless segment in the route.

What the pattern can tell you

• Both the link rate and test result improve closer to the router: distance, obstructions or wireless interference may be affecting the connection. Check the router maker's guidance before changing channel or band settings.
• Wi-Fi tests are slower than a direct Ethernet test on the same PC: investigate the wireless connection and its location first.
• Wi-Fi and Ethernet tests are both similarly slow: the Wi-Fi link alone is unlikely to explain the result. Check the router's internet connection, the test server and your service provider's guidance.
• The link rate is high but the test result is lower: that gap by itself is expected to be possible. Compare test method and server, repeat the measurement, and use Ethernet or another device as a separate clue before buying equipment.

There is no reliable fixed percentage that every speed test should reach from the displayed Wi-Fi rate. Different layers and test conditions are involved, so an arbitrary “half the link rate” rule can send you toward the wrong fix.

If you are checking a game connection

This comparison is about data throughput. A high download result does not tell you whether a game has high latency, jitter or packet loss. If your issue is delayed or uneven play, use the game’s own network indicators and see Jitsumi’s guide to ping, jitter and packet loss .

Start by recording what changes: the Wi-Fi rate, the speed-test result, or both. That pattern is more useful than trying to make two different numbers match.

Sources and further reading

• Microsoft Learn (2025/10), “netsh wlan” , last updated 9 October 2025.
• NETGEAR Support (2025/07), “WiFi Link Rate and Transfer Speed” , last updated 7 July 2025.
• Cisco Support, “Troubleshoot Wireless Speed Issues” , Windows output example on page 2.
• Cloudflare Blog (2025/10), “How does Cloudflare’s Speed Test really work?” , published 27 October 2025.