Run the test above for at least 60 seconds. Here is what each
number means for this game specifically.
Jitter (the metric that decides your rotation)
The ability queue accepts an input in a narrow window near the end of the current action. Consistent latency means you learn where that window is and hit it every time. Jitter means the window moves, and a light attack you pressed at exactly the right moment arrives after it closed. This is the single most important number on this page for a DPS player.
Packet loss (silently dropped inputs)
A lost input packet is not retried by the game. The ability was never queued, the animation never plays, and there is no error - it looks exactly like a mistimed press. If a rotation you can perform reliably on a dummy falls apart at random, look for red on this chart before you blame your hands.
Ping (the megaserver reality)
ESO does not have individual realms - you pick a megaserver at login, and North America and Europe are separate worlds with separate characters. Your ping is therefore mostly a one-time decision rather than something to tune. Under 80 ms keeps weaving comfortable; above roughly 150 ms the timing windows get genuinely harder even when the line is clean.
What you see in game, and which number on this page explains it.
ESO's combat resolves on the server, and the client's job is to send inputs and play the animation the server confirms. To keep that responsive, the game accepts an input slightly before the current action finishes and holds it in a short queue. This is what makes the rotation feel fluid rather than stuttering, and it is also what makes the whole system latency-sensitive in a way that a simple cooldown-based game is not.
Weaving - slotting a light attack between every ability - exists because of that queue. It is not a bug that was left in; it is the direct consequence of a design where two actions can be queued back to back if their timing is right. The skill ceiling of the game is therefore, quite literally, a timing window, and a timing window is exactly the thing that an unstable connection destroys.
Here is the part that misleads players: the failure is silent. When an input misses the window or is lost outright, ESO does not tell you. There is no error, no queued indicator, nothing to distinguish it from having pressed the button too early. Players conclude that their execution is inconsistent and practise harder, when the actual variable is that their inputs are not arriving at consistent times.
The megaserver architecture sets the floor underneath all of this. There are no realms to pick from and no way to move a character between the North American and European megaservers, so the distance to your server is a decision you made at account creation and live with. That baseline is unavoidable. What is avoidable is everything stacked on top of it, and that is what the jitter and loss numbers on this page measure.
If the chart above shows packet loss or high jitter, work through
these in order.
Why do my light attacks not register in ESO?
Usually because the input arrived outside the ability queue window or did not arrive at all. Both are connection behaviour rather than mechanics: jitter moves the window, and loss removes the input entirely with no error message.
Does ping affect weaving?
Consistency matters more than the number. A stable 120 ms is easier to weave on than an unstable 60 ms, because you can learn a stable delay and cannot learn a moving one. That is why the jitter figure here is the one to watch.
Can I move my character to the other megaserver?
No. North America and Europe are separate worlds with separate characters and separate stores. Choosing the one closest to you is a decision made once, and it sets your baseline latency for everything you do afterwards.
Is Cyrodiil lag caused by my connection?
Almost never. Alliance War congestion is server-side and identical for everyone in the fight. Use this test outside Cyrodiil: a clean chart there means the campaign is the cause, and a dirty one means you have both problems.