Of course, you could embed the JS-based client’s timestamp and send it back to another request, but it’s completely unreliable since the user can set the time of his client to whatever he wants and requires that a second request, which could be slightly offensive, or technically inconvenient to provide. Many implementations will do this by fire and forgetting the AJAX request for a text file or adding a single empty pixel image to a page.
You can try to get a similar metric based on the first queries, and geolocation of the IP location and timestamp in time giving you local time - but it can be expensive if you do not already have an IP / Geo database :)
source share