Field note · October 31, 2026 · Jay Fan
Wi-Fi versus Ethernet is a protocol, not a result we are sitting on.
Readers ask for a wired-versus-wireless verdict as if this site had already run one in a living room. It has not. The only retained collection, filed on August 19, used Ethernet under a tunnel the entire time. It cannot tell you whether your access point is the problem. This note is the worksheet and the rules for a comparison you run yourself.
A throughput score answers a different question
A speed test fills a pipe toward a nearby test server and reports how much bulk data moved. Game traffic is small, frequent and aimed at whatever host the matchmaker chose. A high throughput number can coexist with a radio link that pauses, retries or waits behind a video call. A low throughput number can coexist with a perfectly steady game if the game never needed that throughput.
The comparison that matches the complaint is narrower. Keep the game, the selected server or realm, the device and the time of day as still as you can. Change only the last hop inside the house: wireless, then a cable, or the reverse. Write down the game's own signal, not the speed-test grade.
If you cannot get a cable to the PC, the honest version is a same-room wireless pass versus the usual couch or bedroom, still one change. Moving rooms and also pausing an upload is two changes. The log below has a column for that, because spoiled runs are data of a different kind. They are not a secret win for the cable.
Freeze these, or the cable did not get a fair trial
- The game session context. Valorant needs the Riot server name and whether you were in a party. WoW needs the activity, not just the realm. Genshin needs the account server and solo versus co-op. Tarkov needs the map. A note that only says "wired felt better" cannot be repeated.
- The device. A phone and a desktop are not a Wi-Fi test. Thermal behavior, power mode and a different radio stack travel with the device. Compare the same machine if the question is the link.
- The other traffic. Cloud sync, a stream, a console update and a video call are uploads and downloads that fill a queue. Pause them for both the wireless pass and the wired pass, or let them run for both. Do not pause them only after you plug in.
- The clock. Evening congestion on the wider path can change between a 7 p.m. wireless run and a 10 p.m. wired run. Keep the passes close together. The evening-queue note is the page for "it only happens after dinner," which is not the same question as "the radio is noisy."
- One direction of change. Do the worse link first if you already know which one feels bad, then change once. A third pass back to the original link is how you notice that the game simply handed you a calmer server.
Blank log for two passes
Leave the measurement cells empty until you have the session. Example text in the first row is a label, not a published household test. Command syntax for a gateway echo and a public control lives on the methodology page. Copy the steps from there when you are on Windows. This note does not restate them, because restating them into every guide was how the site started to sound like one template.
| Pass | Link | Game context held still | Other traffic | In-game signal | Symptom in words | Void? |
|---|---|---|---|---|---|---|
| Shape of a row | Wireless or cable | Server, realm, map or co-op host | Paused, or the same upload left running | What the game displayed | Spike, loss mark, hitch, or calm | Yes if two things changed |
| Pass A | ||||||
| Pass B | ||||||
| Return to A |
Four ways the pair can come back
Both the game signal and a public control look calmer on the cable. The local link is a real lead. It still does not name a defective antenna or a defective driver. It says the wireless condition you wrote down was involved. Repeat on another evening before you replace hardware. A single calm cable pass during a quiet house is weaker than the same pattern when the house is busy.
The game feels calmer on the cable, and the public control does not change. Be careful. The game may have placed you on a different host. Check the server, realm, data center or raid context before you congratulate the cable. This is the failure mode of "I plugged in and the next match was fine."
The public control looks calmer and the game does not. The wider path or the test destination moved, and the game did not care. Go back to the game's own region, party and service status. A router purchase aimed at the public-control number misses the complaint.
Nothing visible changes. That is a result. Wireless was not the variable this time. Distance to the selected server, an upload queue, a client frame hitch or a one-off match are still open. Do not keep reseating the cable hoping the fourth match will confess.
Throw the comparison out when any of these happened
- You joined a party, changed a Riot or matchmaking region, or zoned into a different WoW instance between passes.
- A game update, shader compile or launcher repair ran on only one of the passes.
- You switched from a laptop on battery to the same laptop plugged in, and you also switched links. Power state is its own experiment, especially in Genshin on a phone, where this whole Windows-shaped protocol may not apply at all.
- Someone started or stopped a large upload halfway through.
- You compared a wireless phone to a wired PC and called it proof about the access point.
A void run can stay in the notebook with the reason filled in. Deleting it is how people invent a clean story. The diagnosis tool is still the short way to name the symptom before you spend an evening on passes. It does not complete this log for you.
What a cable is not allowed to mean
Ethernet does not move you closer to a distant Riot region, a WoW realm on another continent, or a Genshin account server you are not supposed to treat as a dial. It does not render a Tarkov frame the CPU did not finish. It does not repair a match that only one raid suffered. If the in-game network graph was already flat and the picture was the thing hitching, you are in a client problem. The cable can only add a new variable you will then misread.
Guides that already speak this language in their own terms: Valorant, when the packet-loss graph moves on wireless, Genshin, when the phone and the PC disagree, WoW, when Home and World climb together, Tarkov, when you are about to blame the router for one raid.
Editorial log
October 31, 2026. First publication. Jay Fan. Written because local-link instructions were being repeated inside game guides. This page is the long form. No Wi-Fi versus Ethernet measurement from this desk is included, and the August 19 file must not be cited as one. Corrections: redmedia24@yeah.net.