Price the experience
Latency is an engineering number until you can price it.
Performance measures the experience from both ends: what the browser rendered, and what your origin took to answer behind the edge. Those measurements sit on the same timeline as deployments, errors and conversions, so a regression can be read against the conversions and revenue in the same segment and window, with the correlation stated.
Why it matters
What Performance is for
Speed charts do not get budget
A chart of milliseconds has to argue for itself, and it usually loses. Performance puts a conversion and revenue difference for the affected segment alongside the millisecond change, reported as a correlation — the form the argument has to take to win engineering time.
Two vantage points, one timeline
The edge times your origin on every proxied request; the beacon measures what the browser actually rendered. A slow server and a slow front end are different faults with different owners, and only both together say which one you have.
Timing is evidence, not proof
A metric that moves shortly after a release is a correlation, and every comparison here says so, with its window, its segment and its traffic volume on show. A claim you can defend in a meeting is worth more than one you cannot.
What's included
Inside Performance
Each capability is its own surface, and all of them read the same four data layers under one set of metric definitions.
Core Web Vitals
LCP, INP and CLS from real visits, cut by the segments that matter.
Learn moreOrigin Latency
Edge-measured response times from your own servers, with no browser script involved.
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 moreThe platform
The rest of the engine
AI Overview
Opens with a written briefing: what changed, why it matters, what to check.
5 capabilitiesAsk AI
Plain questions become governed metric queries. Every answer arrives with the definition behind it.
5 capabilitiesAcquisition
Channels, campaigns, referrers and AI assistants, sorted by revenue rather than traffic volume.
6 capabilitiesConnect 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