GPS & IP Geolocation Accuracy
Test position accuracy, altitude, and update speed.
Operations and parameters
Return data (Position)
Availability and Permissions
Event log (last 30 entries)
Tips
GPS Guide
Check permissions and acquire coordinates.
Check environment and permissions
Confirm HTTPS and view the location permission status.
Get a positioning
Use getCurrentPosition to quickly verify whether you can get the coordinates and accuracy.
Start listening and observe changes
Use watchPosition to observe movement, update frequency and logs.
FAQ
Have questions? We have the answer! The following is a collection of frequently asked questions about geolocation testing.
What can this page test?
It uses the browser Geolocation API to check whether positioning is available, and displays the permission status, whether it is a secure context (HTTPS), and the coordinates, accuracy, and timestamp returned by the positioning.
Why does it have to be HTTPS?
Positioning is a sensitive capability, and modern browsers generally only allow it in a secure context. Non-HTTPS pages are often rejected or downgraded outright.
Why do I get the message "Permission Denied" after I click "Get Once/Start Monitoring"?
This means that the site location permission has been denied by you. Please change the positioning to "Allow" in the site permissions/settings of the browser address bar, then refresh the page and try again.
Why is "Permissions API Unavailable" displayed?
Some browsers/modes (e.g. privacy mode) may not support the Permissions API and therefore cannot pre-read permission status. But you can still click "Get Once/Start Listening" to have the browser pop up an authorization prompt and return the result.
What is the difference between "get once" and "start listening"?
"Get once" calls getCurrentPosition and only returns the result once; "Start monitoring" calls watchPosition, which will continue to call back when the position changes or the system updates. It is suitable for observing update frequency, precision changes during movement, etc.
Is the smaller the accuracy (positioning accuracy), the better?
Generally speaking, the smaller the value, the smaller the estimation error, but it is affected by indoor/outdoor, GPS/Wi‑Fi/base stations, system power saving strategies, etc. It is more meaningful to do comparative testing on the same device.
Why is "data age (now - timestamp)" large?
It could be that the system returns a cache location (maximumAge allows caching), or the sensor is not updating/throttled by system power saving. You can try setting maximumAge to 0, increasing timeout, and retesting outdoors/by a window.
What is the impact of "high precision"?
enableHighAccuracy=true may trigger a more power-consuming but more accurate positioning path (depending on the device and system). There may be limited improvement indoors, but it will be slower or more power-hungry; it is recommended to do a control test with it.
Why does positioning time out (TIMEOUT)?
Common reasons are weak signal (indoor/obstructed), the system is saving power, or the browser/system service is temporarily unavailable. You can increase the timeout (for example, 15-30 seconds), or switch networks/turn off VPN/proxy, change browsers and try again.
Is privacy safe? Will my location be uploaded?
The page just calls the browser positioning interface and displays the results on the front end. This page does not need to upload the location information to the server (unless you manually copy/submit it).