The rule: diagnose the layer before changing settings
Most bad fixes happen because the player starts at the wrong layer. A DNS change will not fix weak Wi‑Fi. A route optimizer will not fix upload bufferbloat. A new GPU will not fix packet loss. This checklist is built to identify the layer that fails first.
| Layer | Common symptom | Free check | Likely fix |
|---|---|---|---|
| PC performance | Stutter while ping stays stable | FPS/frame-time graph | Graphics settings, drivers, thermals, background apps |
| Wi‑Fi | Spikes vanish on Ethernet | Ethernet control test | Cable, 5 GHz/6 GHz, router placement |
| Router queue | Ping jumps when others upload | Waveform Bufferbloat Test | SQM/QoS or upload cap |
| ISP route | Same local network, bad path to one region | Traceroute/Globalping | ISP evidence, server change, route optimizer trial |
| Game server | Friends on different ISPs also lag | Community reports and in-game status | Wait, change region, avoid ranked during outage |
Ten-minute workflow
- Run PingKiller Live Test while the connection is idle.
- Run it again while another device streams or uploads.
- Repeat over Ethernet if you normally use Wi‑Fi.
- Open your game network graph and play one match.
- If FPS/frame time spikes without network spikes, solve PC performance.
- If packet loss or jitter appears only under load, test bufferbloat.
- If the local network is clean but one region is bad, test server recommendations and traceroute.
- Only trial a route optimizer when the evidence points to routing.
Evidence template
Save this in a note: game, region, ISP, connection type, time of day, median ping, worst spike, jitter, packet loss, loaded latency result and whether Ethernet changed the result.
A good diagnosis does not need perfect tools. It needs repeated tests under the same conditions and one variable changed at a time.