Visitor Monitor
No polling, no scheduled checks - real visitors report your site is working, as they use it.
Every other monitor type pings your site from Kawze's own infrastructure on a schedule. A Visitor Monitor works the other way round: a small JS snippet embedded on your page reports page-load time, response status and any JavaScript, resource or fetch/XHR errors straight from real visitor traffic - so you find out about a broken checkout button or a failing third-party script the same way your customers experience it.
How it works
- Create a Visitor Monitor for your site and copy the generated script tag onto your page, just before the closing </body> tag.
- The snippet reports page-load time, TTFB, DNS/connect/TLS timing and the document response status on every real page view.
- It also watches for uncaught JavaScript errors, unhandled promise rejections, failed resource loads (images/scripts/stylesheets) and failed fetch/XHR calls - and keeps reporting them for as long as the page stays open, not just at load.
- If no beacon arrives within a grace period you set, Kawze flags the monitor as down - the same reasoning as heartbeat monitoring, just driven by visitors instead of a cron job.
- Optional rate-based alerting fires if resource, fetch or JS errors cross a count-in-a-window threshold you configure, separate from the down/up state.
Why it matters
- Catches problems only real visitors hit - a broken script on one browser/CDN edge, a third-party widget failing, a JS error that only fires after login.
- No server-side polling needed - nothing to configure about check intervals or regions.
- Same email/SMS/Slack alerting and dashboard as every other monitor type, plus a check-strip and response-time chart driven by real visits.
- Origin-restricted to the site it was set up for, so a copied snippet can not be pointed at an unrelated site to pollute your stats.
Frequently asked questions
Does the Visitor Monitor track individual visitors or sessions?
No - it deliberately does not do session or user-level tracking. It only records the narrow set of reliability signals described above (timing, status, errors), not analytics.
What happens if my site gets no traffic for a while?
The monitor is flagged down once no beacon has arrived within the grace period you set - configurable per site, since a low-traffic site's normal gap between visitors can be hours, not minutes.
Will ad blockers or extensions cause false alarms?
Resource and fetch error tracking are both independently toggleable, and connection-related failures (offline, aborted requests) are filtered out automatically, so blocked tracking pixels or ad scripts are not counted as your site being broken.
Is there a limit on how much visitor traffic this can handle?
Each plan includes a monthly cap on recorded beacons - once reached for the month, the monitor keeps working for up/down detection, it just stops recording detailed stats until the next month. See the pricing page for plan limits.
This capability lives on Kawze's visitor monitor - see that page for the full feature list and pricing for that uptime monitor type.