This static version reads your device time directly. No server is needed, and the clock refresh loop restarts automatically if the browser pauses it.
Device time--:--:--
Last display resync—
Loop statusLive
No server time check in this static build. A future optional Cloudflare Worker can compare your device clock with network time using only a few pings on demand.
Why this matters
A clock page can be left open for hours. This build automatically restarts the update loop when the tab wakes, the device returns from sleep, or the browser throttles animation frames.
What this check can and cannot verify
This page checks your browser display refresh and device-clock behavior. TimeWithSeconds updates from your device clock and automatically resyncs the display when the tab becomes active again.
For official atomic accuracy, your operating system must be synchronized with network time. A browser-only static page cannot independently prove atomic-clock accuracy without an optional network reference.
What the accuracy check shows
It watches the browser clock display, reports when the display was last resynchronized, and lets you restart the display loop manually. It does not claim to measure an atomic clock by itself.
Where the time comes from
The page reads the clock already maintained by your device. If the operating system is synchronized with network time, the display follows that clock without continuous server requests.