Price the experience
The edge already times your origin, so nothing needs installing.
Every proxied request passes through the edge, which records how long your origin took to answer, whether the response came from cache, and which route it belonged to. That covers APIs, redirects, feeds and crawler traffic — requests no browser script ever runs inside.
Origin Latency
- Origin response time percentiles
- Cache hit and miss latency split
- Latency by route and region
- Timing for non-browser traffic
How it helps
What Origin Latency gives you
Server time, separated from network
Origin response time, edge processing and cache status are recorded separately. When a page gets slower, that split says whether your application changed or your cache hit ratio did — two problems with two different fixes.
Coverage a tag cannot reach
API endpoints, webhook receivers, feeds, redirects and bot requests are all timed, because the measurement happens in the request path. A tag cannot report on a response that no browser was ever there to receive.
The same origin, timed from everywhere
Origin timing is recorded at each edge location the request passes through. An origin that answers in 80 ms from Frankfurt and 400 ms from São Paulo points at routing and placement rather than the application. A single average response time hides that.
Performance
The rest of Performance
Core Web Vitals, origin latency and errors, read against conversions and revenue.
Core Web Vitals
LCP, INP and CLS from real visits, cut by the segments that matter.
Learn moreErrors
HTTP and client-side failures, ranked by the conversions behind them.
Learn moreDevice & Browser
Vitals, errors, conversions and revenue for the same segment, side by side.
Learn moreDeployment Impact
Automatic before and after comparisons around every release, scoped to changed routes, reported as correlation rather than cause.
Learn moreRevenue Impact
What a technical segment is worth in currency, with the caveat attached.
Learn moreConnect a site today. Read tomorrow's brief instead of building it.
Connect a site and the first brief arrives with the day's changes already explained — traffic separated from bots, conversions attached to revenue, and the evidence behind every sentence one click away.
Real people separated from bots Every answer shows its evidence Reveliqo runs on Reveliqo