BROWSER FORENSICS

Input-to-Photon E2E Latency Analyzer

Measure absolute end-to-end system input lag without an NVIDIA LDAT. Record a 240fps slow-motion video of your mouse click and monitor flash, and drop it here for instant, 100% private client-side DSP analysis.

Click here to flash the screen (Record this area with your phone)

Drop 240fps Slow-Mo Video HereMP4/MOV files only • Processed 100% locally

How This Works (Zero Uploads)

This tool utilizes the bleeding-edge WebCodecs API and Web Audio API to perform forensic video analysis directly in your browser's memory. When you drop a video, it extracts the acoustic transient (the mechanical switch click) and the optical transient (the screen luminance change) to calculate your exact system latency. Zero data ever leaves your computer.

Technical FAQs & Helpful Content

Frequently Asked Questions

Everything you need to know about this diagnostic instrument, calibration procedures, and display technical standards.

01.What is End-to-End (E2E) System Latency?

E2E latency is the total absolute time it takes from physically clicking your mouse switch to the corresponding visual action (like a muzzle flash) appearing on your monitor's pixels.

02.How does this browser tool measure latency?

By uploading a high-speed slow-motion video (e.g., 240fps) of you clicking your mouse and the screen reacting, this tool uses WebCodecs and the Web Audio API to find the exact millisecond of the click and the flash.

03.Do I need an NVIDIA LDAT or Reflex Analyzer?

No. This tool Democratizes hardware forensics. Anyone with a modern smartphone capable of recording slow-motion video (120fps or 240fps) can test their true E2E latency for free.

04.Is my uploaded video private?

Yes, 100%. All video demuxing, decoding, and analysis happens entirely locally in your browser's RAM using WebAssembly and WebCodecs. Zero bytes are uploaded to any server.

05.Why is measuring software latency not enough?

Software latency tests (like generic click-speed tests) only measure browser API dispatch times. They completely ignore mouse firmware, USB polling, OS compositor delays, GPU render queues, and display pixel response times.

06.How should I record the slow-motion video?

Hold your phone sideways. Ensure both your mouse and your monitor are clearly visible in the frame. Point the camera so it can hear the mouse click clearly. Click the mouse to trigger a bright flash or action on screen.

07.Does this work on mobile browsers?

The analysis tool requires significant CPU processing and the WebCodecs API. It is heavily recommended to use a desktop browser (Chrome, Edge, or Safari 16.4+) for the analysis step.

08.What is a good system latency?

For competitive esports titles (CS2, Valorant), exceptional E2E latency is under 15ms. Good is 15-25ms. Average console or casual PC latency is often 40-80ms.

09.How can I reduce my system latency?

Enable NVIDIA Reflex or AMD Anti-Lag, ensure your monitor is set to its maximum refresh rate, use exclusive full-screen mode, disable V-Sync, and use a mouse with a 1000Hz+ polling rate.

10.Why is 240fps video recommended over 60fps?

A 60fps video only captures frames every 16.6ms, meaning your measurement could be off by up to 16ms. A 240fps video captures every 4.1ms, providing much higher precision for latency analysis.

Not sure which test to run next? Need troubleshooting advice?

Read Complete Diagnostic Guide →

INFO

AWAITING VIDEO

Analysis Status

--/ms

Privacy100% Local

EngineWebCodecs / WASM

Latency Telemetry

Timeline Milestones

DSP

Audio Click Time

--ms

Video Flash Time

--ms

True E2E Latency

--ms