Skip to content
Performance

Price the experience

Some browsers convert worse — this shows whether vitals and errors move with it.

Device class, browser family and version, operating system, screen size and connection type are attached to every measurement, technical and commercial alike. One table holds vitals, error rate, conversion rate and revenue per visit for the same slice, so the comparison needs no joining by hand.

Device & Browser

  • Vitals and revenue in one table
  • Browser version-level grouping
  • Device, OS and connection segments
  • Segment history instead of site averages

How it helps

What Device & Browser gives you

1

A gap is not a problem

Mobile Safari converting below desktop Chrome is ordinary; intent differs by device. What matters is the gap moving, which is why each segment is read against its own history rather than against the site average.

2

Version boundaries show up first

Grouping by browser version catches a fault that appears on one release and nowhere else. That shape is usually a compatibility break, and it stays invisible in any chart that only splits mobile from desktop.

3

One segment definition, both sides

The browser version in the vitals chart is the same population as the one in the revenue column, because both are cut from one segment definition. Monitoring tools and analytics tools hold those halves apart, and a version-level comparison across them is guesswork.

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