Am I lagging or just bad? How to tell lag from a skill issue
UPDATED
Died behind cover, shot first and lost? A 5-step check to find out whether it was your connection, the server, or you. With numbers instead of feelings.
You peeked first, you clicked first, and you still died. Was it lag, or was it you? Most players answer that question with their feelings. Here is how to answer it with data.
1. Check the killcam against what you saw
If the killcam shows you standing in the open while on your screen you were already behind cover, your client and the server disagreed about where you were. A small difference is normal (that is lag compensation doing its job). A big one, repeatedly, points at latency or jitter.
2. Look at your in-game network stats
Every competitive game has a network display: ping, packet loss, sometimes a graph. Turn it on and leave it on for a few matches. What you are looking for is not the number itself but changes: spikes, loss warnings, or a ping that is much higher than usual.
3. Run a test while it feels bad
Run the Rekt-al Net test right after the match that felt laggy, not the next morning. It measures your ping, your jitter and your packet loss in about four seconds. Under 60ms ping, under 15ms jitter and no loss means your connection was fine.
4. Check whether it is only you
If the whole lobby complains, it is the server. If only you rubber-band, it is your connection. If nobody lags and you still lose every duel, keep reading.
5. Be honest about the other explanations
- Peeker's advantage: the player who moves into the fight sees you slightly before you see them, even on perfect connections. Holding a wide angle against an aggressive peek is a losing trade.
- Your frame rate: low or unstable FPS feels exactly like lag. If your frame time graph spikes, the problem is your PC, not your network.
- Your reaction time: about 200 to 250ms for most people. That is several times more than a bad ping.
The verdict
Bad numbers in step 2 or 3: it was lag, and the guides on lowering your ping and fixing lag spikes will help. Clean numbers everywhere: we are sorry. It was a skill issue.