Traffic looked normal, so nobody noticed checkout had broken. Cronitor tracks JavaScript errors and conversions next to traffic. Compare errors with conversion rates to see when they move together. Add a conversion with one line: cronitor('track', 'Checkout').
Your laptop on office Wi-Fi isn't your customer on a mid-range Android over 4G. Cronitor measures load time and Core Web Vitals in your visitors' own browsers, from the median visit to the slowest 5%.
Before you can fix a slow page you need to know whose fault it is: your server, the network, or your JavaScript. Cronitor splits every page load into those three stages so you know where to start.
/checkout behaves nothing like /.The script sets no cookies, and Cronitor does not store visitor IP addresses. Sessions cannot be traced back to individual visitors, including by us. Known crawlers are dropped before data is stored.
A lab test runs your page on one controlled device, so it's repeatable. Field data is what real visitors' browsers measured, so it's what actually happened. You want both.
One async script in your <head>. It reports a pageview, the page-load timings, the web vitals and any JavaScript error, from every browser that loads the page. Client-side route changes are tracked automatically, so a single-page app needs no additional wiring.
Cronitor loads the page itself, on a schedule, from the regions you pick, and asserts against the response. Identical conditions every run, so a change in the number is a change in your site.
It can run before the release reaches anybody. It cannot tell you what your visitors got. → Checks
Real browsers report what real visitors measured, on the devices, networks and geographies they actually have. The distribution is your audience, not a reference machine.
It cannot run before release, and it needs traffic to mean anything. → Analytics
The two failure modes are different too. A check catches the page that stopped answering; analytics catches the page that still answers, still returns 200, and has quietly stopped converting.
See where visitors came from, down to the campaign, and whether this week beat last week.
Read load time and Core Web Vitals per page, country, device, and connection. The numbers for /checkout on mobile 4G are the ones that matter.
Is it only Safari? Only Germany? Only /checkout? Narrow any chart to the visitors having a bad time, across 16 dimensions.
Site alerts use the same escalation rules and 12+ integrations as your checks and jobs, so one on-call rotation covers all of it.
Track traffic, performance, conversions, and JavaScript errors without tracking cookies or adding a tag manager.
Sessions, pageviews, bounce rate and session duration, updated as visitors arrive.
Largest Contentful Paint and Cumulative Layout Shift, measured in your visitors' browsers.
Know whether slowness is your server, the network, or your JavaScript.
See the errors your visitors hit, without noise from their browser extensions.
One call, cronitor('track', 'Signup'), and conversion rate updates in real time.
Narrow any chart to a browser, country, device, or page.
One snippet across several domains, with sessions stitched instead of double-counted.
Keep staging traffic out of your real numbers.
Drop bots by default, and keep localhost and your office IPs out of your reports.
Assert on traffic, load time or error rate, and route it like every other monitor.
Pull the same numbers into your own dashboards and reports.