Enter a target URL to run three HTTP response-time samples. The clock always remains local.
A positive value moves the display ahead; a negative value moves it behind. The ±60-second offset also affects alarms.
Enter a target URL to run three HTTP response-time samples. The clock always remains local.
A positive value moves the display ahead; a negative value moves it behind. The ±60-second offset also affects alarms.
The display uses the system clock of the device running this browser and shows its milliseconds. Enable automatic date and time synchronization in your operating system for the best result. This page does not synchronize with a separate standard-time server.
If you know your device differs from a trusted reference, enter a manual offset in milliseconds. A detailed millisecond display does not by itself guarantee that the underlying device clock is accurate.
The browser sends three lightweight HEAD requests and reports the minimum, average, and maximum elapsed time until each response is received.
The result may include DNS lookup, connection setup, TLS negotiation, network conditions, and server processing. It is a browser measurement—not ICMP ping, a server-clock offset, or a prediction of when a click will be accepted.
Browsers often cannot read response headers from another origin because of CORS. An HTTP Date header is also generally limited to whole seconds and does not guarantee the time a service uses to accept transactions, so it cannot provide a millisecond-accurate target clock.
This tool does not use a CORS proxy and does not estimate server time. Response tests omit cookies, but they still send a normal network request to the target. Browser policy, mixed-content blocking, or the site's configuration may prevent a test even when the site is online.
To help you focus purely on the ticketing screen or "Refresh" button rather than staring at the clock:
Your browser may require one click or key press after opening the page before it allows sound. The manual offset also changes when these alarms occur.
Alarms work best while this page is visible and the browser is updating normally. A background tab, device sleep, or a busy main thread can skip the 58, 59, or 00-second frame, so do not rely on these sounds alone for a critical deadline.