How Network Time Calibration Works
Understand server time, round-trip latency, device offset and uncertainty when reading a browser network-time test.
Updated: 2026-07-20
Why new Date() is not enough
new Date() reads the device system clock. If that clock is wrong, the page is wrong too. Calibration needs a time point from a trusted server.
Estimating network delay
The client records send and receive times and uses half of the round trip as a one-way estimate. Repeated samples and a low-latency result are usually more stable.
Understanding uncertainty
Upload and download delays are not necessarily symmetric. VPNs, congestion, mobile networks and background throttling all widen uncertainty.
When to correct the device clock
If several low-latency measurements show a persistent difference of seconds, check automatic time and time-zone settings. A web page cannot change the system clock.
Related tools
Worked example and limits
An HTTP Date reading of 12:00:00 carries only second resolution; it cannot establish a 20 ms device error. The tool estimates the interval center as 12:00:00.500. With an 80 ms round trip, uncertainty is about ±540 ms. This is a calculation example, not a measured network benchmark. Use operating-system time synchronization to correct persistent drift; the page cannot set the system clock.