Skip to content

Count page views and project clicks with PostHog (EU servers)? It loads only if you choose Allow. Privacy

Latency Test live preview
All projects

Latency Test

See real client-side latency, not just server-side benchmarks.

Choosing deployment regions needed latency data, but most tools measured from the server, not from an actual user's browser.

Tech Domain · Book Dev|Published|Evidence: Live|Next.js, TypeScript

A public deployment is available to try.

Case Study

Before

Choosing deployment regions required latency data, but existing tools focused on server-side testing and didn't show the client-side experience.

After

The page shows round-trip times from your own browser to any http(s) target you choose, with failed requests excluded from the stats.

How it's solved

Built a browser latency probe, now at /latency-test in the Devtools Workbench suite: enter a URL or path, send a timed fetch (no-cors for cross-origin targets), and keep a session log of up to 12 runs with average, median, min, and max.

Trade-offs

One target per probe, with no region map or stored history. Times include connection setup and reflect the testing device's own network, not a controlled benchmark.

Related Articles

Further reading on related topics from the blog

Related Projects

More in Tech Domain · Book Dev