Consecutive skills under the same finger cannot overlap. The second one waits for the first to lift, which is exactly the delay that reads in game as "it did not cast".
Steam Your build has a rotation. Your hand may not.
Every guide publishes the order — curse, then the movement skill, then the big hit. None of them measure whether a human produces that order while holding movement down. This bench prompts your own rotation at your own cadence and reports which step arrives late, which one never arrives at all, and which two are fighting over the same finger.
Nothing leaves this browser Physical key codes, any layout Limits printed beside the result
KEYMAP / ROTATION BENCHLOCAL
—median step
Complete0/0
Cycles0/6
Weakest—
Declare it. Run it. Find the step that breaks.
Start by writing down the rotation you actually play and the key each skill sits on. The bench then drives it, and everything after that is evidence about your own hand: the move-and-cast check, the sustain meter and the reach map all feed the same report.
Describe how you move, not how a streamer moves.
Movement decides which hand is free. Cadence decides how hard the bench pushes. Neither is a recommendation — they are the conditions your result will be true under.
Two to eight skills, in the order you press them.
Click a key button to rebind it and press the real key — the page stores the physical position, so an AZERTY or QWERTZ keyboard is measured on the key your finger reaches rather than the letter printed on it.
Press the skill the page names, in the order it names them.
The bar under the prompt is the time you have. A step that arrives after it is late, a step that never arrives is missing, and both are recorded as what they were rather than smoothed away.
Press now — Press start to begin
Keep your move key held down the way you would in a map. The bench is measuring the rotation under that load, not in isolation.
Three things the rotation alone cannot tell you.
Whether every skill survives being pressed while you move, whether your click rate holds up through a pack, and where each bind sits relative to the hand that is already holding movement.
Move and cast
Hold your move input and press every skill in the rotation. Keyboards report a limited number of simultaneous keys; this names the binds that silently lose that argument.
Press start, then hold move and press each skill.
Sustain
An ARPG is a clicking game. Fifteen seconds at the rate you actually play, with any interval short enough to read as a double click counted separately.
Press start, then click in this pad.
Rate—
Clicks0
Paired0
Reach map
Green is the block a moving left hand covers without leaving the movement cluster; amber is a stretch; the ring marks the keys your rotation is bound to.
12345
QWERT
ASDFG
ZXCVB
What your hand did, and what to change first.
Every line below comes from a measurement on this page. Nothing is inferred from your build, your class or anyone else's settings.
Rotation fit — Out of 100, inside this model
Median step—
Completed—
Weakest step—
Move and castnot run
Sustainnot run
0 finding(s). Nothing on this page is uploaded; the export is a file you save yourself.
Why a rotation is a hand problem Two steps, one finger Movement is a held key Cadence is a choice, not a fact
The step you drop is not the step you would guess.
A build guide is written in the order the damage happens. A hand executes it in the order the fingers can reach, and those two are not the same list. Three things decide the difference, and all three are measurable in a browser.
With WASD, the hand reaching for skills is the hand holding the direction. A bind that is comfortable at rest can be a stretch while W is down, and a keyboard matrix may refuse the combination outright.
Any rotation lands if it is slow enough. The number worth keeping is the fastest cadence where completion still holds — and it belongs to your hand, not to the build.
Method and limits Measured Modelled Not claimed Repeatable
What is measured, and what is deliberately not claimed.
Whether the expected physical key arrived, whether it arrived in order, and the milliseconds from prompt to key. Simultaneous-key delivery while a move key is held. Click intervals during the sustain run.
Finger assignment and reach bands come from a stated keyboard model, not from your hand. They are a starting point for the findings, and the page names the model rather than hiding it.
Cooldowns, animation cancels, server tick, skill effectiveness and build quality. This page has no way to observe any of them and does not pretend otherwise.
Same rotation, same cadence, same keyboard should land within a few milliseconds of the same median. If it does not, something changed on the machine — which is itself worth knowing.
Before you rebind anything
Questions this bench gets asked
Does this read my Path of Exile 2 settings?
No. It cannot read game files and it does not try to. You type in the rotation you actually play — the skills, in the order you press them, on the keys they sit on — and the bench measures what your hand does with it. Nothing is imported, nothing is uploaded, and nothing about the result depends on your build being a good one.
Is a faster rotation always better?
No, and the page deliberately leaves the cadence to you. Any rotation lands if it is slow enough, so the number worth keeping is the fastest cadence where completion still holds above about ninety percent. Run the same rotation at two speeds and keep the one you could sustain through a map rather than the one you hit twice.
Why does it ask whether I use WASD or click to move?
Because it changes which hand is busy. With WASD movement the left hand holds a direction and reaches for skills with the same fingers, so a bind that is comfortable at rest can be a stretch mid-pack. With click to move the right hand is occupied instead and the mouse buttons stop being free. The same rotation costs different things under the two, and only one of them is yours.
My keyboard drops a skill while I hold W. Is that the game?
Almost never. Keyboards report a limited number of simultaneous keys, and the limit depends on which keys share an electrical group rather than on a number in a spec sheet. Holding a direction plus a skill is exactly the shape that gets refused, and the game receives nothing at all — from the inside it looks like a cast that did not go off. The move-and-cast check on this page names which of your own binds it happens to, and the repair is a different key rather than a different setting.
Does it know about cooldowns or animation cancels?
No, and the page says so rather than implying otherwise. It measures completeness, order and duration: whether the expected key arrived, whether it arrived in sequence, and how long it took. Those are facts about your hand. Whether Path of Exile 2 accepted the cast depends on a server tick and an animation state that neither of us can observe from a browser.
Where to go next
The bench reads your hand. These read the hardware underneath it.
Ghosting test Confirm the exact skill keys your keyboard refuses while a movement key is held. Open Double-click test An ARPG is a clicking game; a worn switch spends flask charges you never meant to use. Open BindIQ keybind optimizer Turn a failed rotation step into three explained layout plans rather than a guess. Open Other game labs The same treatment for the rest of the library. Open
