Compare Wi-Fi and Ethernet on the same device and test mode. Look at upload, download, idle latency and loaded latency rather than assuming the connection with the higher download number is always better.
Control what you can
Use the same computer, router and approximate time window. Confirm that the computer actually switches to the intended connection; disable Wi-Fi for the cable run if necessary. Record the negotiated Ethernet link speed separately. A slow adapter or cable fault can constrain the wired result, while walls and competing wireless traffic can affect Wi-Fi.
A repeatable procedure
- Run the standard test on Wi-Fi at your normal location.
- Connect Ethernet, ensure that it is the active connection and repeat.
- Alternate the two conditions several times, saving each result with its connection label.
What the comparison does not prove
A consistent difference is useful troubleshooting evidence, but one test does not prove that all Wi-Fi is poor or that a new cable will fix the issue. This guide does not present a dataset of 1,000 tests; the earlier numerical study claim has been withdrawn because a reproducible dataset was not supplied.
Use the result without overstating it
Start with the DC SPEED connection test, choose the same mode for comparable runs and label the connection conditions yourself. The result panel separates idle latency from latency during download and upload. Its before-and-after view reports differences between compatible runs; it does not identify the cause automatically. History and CSV export let you keep a record without creating an account.
For a problem in a specific game, use the gaming diagnostic guide and the game own network statistics. Read the measurement methodology before comparing this tool with another service. These instructions are a troubleshooting workflow, not a report of laboratory experiments performed by the author.