Skip to content
Performance

Price the experience

An error rate only means something next to the revenue in the same segment.

Status codes from the edge sit beside client-side failures from the beacon: 5xx from the origin, 4xx from stale URLs and broken links, timeouts, and requests that fail mid-checkout. Each is grouped by route, and each group carries the conversion rate of the visits that hit it.

Errors

  • 4xx and 5xx trends by route
  • Client-side error capture
  • Errors ranked by affected revenue
  • Timeout and origin failure tracking

How it helps

What Errors gives you

1

Not every 404 matters

A missing page that only crawlers request is noise. A missing page between a paid campaign and a cart is a leak. Errors are ordered by the traffic and revenue behind them, not by raw count.

2

The failure the visitor saw

A 200 response with a JavaScript exception that blocks the form looks healthy in server logs. The beacon reports the exception, the edge reports the status, and together they describe the request as the visitor met it.

3

Spikes read against origin latency

Status codes share a timeline with origin response time and deployment markers. A wave of 502s with origin latency climbing ahead of it has the shape of a saturated origin; the same wave with latency flat points somewhere else entirely.

Connect 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