CPS Test – Check Your Clicks Per Second Online
Test and train your clicking speed with real-time CPS metrics, ripple click animations, multiple time modes, and reflex rank scoring.
Open ToolConvert milliseconds to seconds and minutes instantly with real-time 3-way synchronization and common timing benchmarks for programming and automation.
RunMacro.sleep(2500);// Sleep for 2.5s| Time Conversion | Milliseconds (ms) | Typical Automation Use Case | Action |
|---|---|---|---|
| 50 ms = 0.05 s | 50 ms | 20 CPS Ultra Fast Click / Spam | |
| 100 ms = 0.1 s | 100 ms | 10 CPS Fast Click / Combat Burst | |
| 250 ms = 0.25 s | 250 ms | Human Double-Click Interval | |
| 500 ms = 0.5 s | 500 ms | UI Animation / Modal Transition Wait | |
| 1,000 ms = 1.0 s | 1,000 ms | Standard Page Load / DOM Ready | |
| 2,500 ms = 2.5 s | 2,500 ms | API / Form Submission Response Delay | |
| 5,000 ms = 5.0 s | 5,000 ms | Heavy Script Export / File Download | |
| 60,000 ms = 60.0 s = 1.0 min | 60,000 ms | Scheduled Recurring Task Loop Interval |

Stop timing macros by trial and error. Inject calculated delays into execution loops to prevent desync and dropped clicks.
Enter your desired delay in Milliseconds (ms), Seconds (s), or Minutes (min). All other fields sync instantly.
Review practical automation benchmarks from 50ms fast click spam to 60s background loops.
Click Copy Command to grab the ready-to-use RunMacro.sleep(ms) snippet for your automation scripts.
Converting human time units into millisecond delays for automation loops and debounce timers.
Desired Delay: 2.5 minutes (waiting for large database export).Milliseconds: 150,000 ms | Seconds: 150.0 s | Code: RunMacro.sleep(150000);Real-time two-way bindings between milliseconds, seconds, and minutes.
How many seconds is 500ms or 100ms?
500ms = 0.5 seconds (half a second) and 100ms = 0.1 seconds.
Conversion formula: Seconds (s) = Milliseconds (ms) / 1000.
| Milliseconds (ms) | Seconds (s) | Minutes |
|---|---|---|
| 50ms | 0.05s | - |
| 100ms | 0.1s | - |
| 200ms | 0.2s | - |
| 500ms | 0.5s | - |
| 1000ms | 1s | - |
| 60000ms | 60s | 1 min |
Syntax mappings across popular automation engines and precision time conversion formulas.
| Language / Framework | Native Delay Command | Time Base Unit | 1 Second Delay Example |
|---|---|---|---|
| RunMacro Automation | RunMacro.sleep(ms) | Milliseconds (ms) | RunMacro.sleep(1000); |
| AutoHotkey (AHK v1 / v2) | Sleep, ms / Sleep(ms) | Milliseconds (ms) | Sleep(1000) |
| Python (time module) | time.sleep(seconds) | Seconds (float) | time.sleep(1.0) |
| JavaScript / Node.js | setTimeout(fn, ms) / delay(ms) | Milliseconds (ms) | await new Promise(r => setTimeout(r, 1000)) |
Understanding operating system thread sleeping precision.
Standard Windows thread sleep commands (Sleep(ms)) have a default scheduling quantum of ~15.6ms.
Typing in milliseconds, seconds, or minutes updates the other two units in real-time with sub-millisecond precision.
Curated list of standard delays for fast clicking (10-20 CPS), UI animations, DOM loading, and server calls.
Generates ready-to-paste RunMacro.sleep() code with explanatory comments matching your input.
Click on any reference benchmark row to instantly load that delay value into the active converter fields.
Clear answers about using this tool and automating workflows with RunMacro.
Computers execute operations at microsecond speeds. Milliseconds (1/1000th of a second) provide the fine-grained control needed to time clicks, keystrokes, and game actions without stutter.
For fast combat clicking, 50ms to 100ms (10 to 20 CPS) is standard. For web applications and checkout forms, 250ms to 500ms prevents input buffer congestion.
Multiply seconds by 1,000. 2.5 seconds × 1,000 = 2,500 milliseconds (ms).
RunMacro automatically captures natural human delays down to the millisecond, and lets you speed up, slow down, or customize delays across the entire macro with one slider.
Explore other helpful browser-based utilities in the same category.