See the difference.

Two views of the same site. The left is routed through the Yabby edge. The right is an origin baseline fetched by the demo harness. Page analytics require no JavaScript by default; an optional lightweight client measures SPA navigation.

Focus: Yabbified labFocus: origin baseline

Yabbified lab

Routed through the Yabby edge

LIVE

●https://lab.getyabby.com/↻　↗

Origin baseline

Direct origin fetch · no analytics transform

LIVE

●wp-lab.origins.getyabby.com↻　↗

Same origin, same content. The Yabbified view adds edge page analytics by default; the baseline skips analytics and HTML transformation.

Live aggregate

Privacy-safe signals from the Yabbified view · last 30 days

Auto-updates with traffic

Views

57Aggregate navigations

404s

0Broken-link requests

Origin latency <250ms

—24h latency buckets

Platform

WordPressAllowlisted signal

CTA exposures

43Experiment aggregate

CTA clicks

4Signed redirect aggregate

Privacy-safe by design.

No analytics identity cookie, no raw IPs, and no user-level data stored. An active experiment uses a separate daily assignment cookie that customers must assess and disclose.

JavaScript is optional.

HTML streams through the edge while aggregate counters update beside the response. Sites with client-side routing may enable a small same-origin client that sends only a redacted pathname.

Same origin, same content.

Only the network path differs. The comparison does not claim conversions, unique visitors, journeys, or legal compliance.