Guides
Goal-driven walkthroughs for the things teams actually want to do with fastmon.
Each guide solves one specific problem. They assume you've already implemented the beacon and have data flowing.
Beacon Inspector
A DevTools extension that captures beacons as your page sends them and unpacks every field and Web Vital.
Compare releases
Tag deploys from CI/CD and answer 'did this deploy regress LCP?' in one query.
Filter internal traffic
Keep office and staff visits out of your real-user metrics.
First-party proxy
Relay beacons through your own server and keep geo and visitor counts accurate with a proxy secret.
Report Content Security Policy violations
Two response headers make the browser report every violation of your policy, so you can test one before it enforces.
Set up Network Error Logging
Two response headers make Chromium report every failed request to your site, including pages that never loaded.
Notification rules
Alert when a metric crosses a threshold or worsens against the previous window.
Track the Shopify checkout
Paste a custom pixel so the checkout funnel of a Shopify shop reaches past the cart.
Server-Timing headers
Emit Server-Timing headers and fastmon splits your server time into phases, cache status, and custom keys.
What's not here
Things that belong elsewhere:
- Setting up fastmon for the first time. See Implementation.
- Understanding a metric. See Web Vitals.
- Concept reference. See Concepts.
- API schema and endpoints. See API.
MCP server
Read your organization's real-user data from an AI client you run yourself (Claude, Cursor) over the Model Context Protocol. Read-only, opt-in per organization, connected with OAuth.
Beacon Inspector
A DevTools extension that captures fastmon's RUM beacons as your page sends them and unpacks every field, lifecycle mark, and Web Vital right in the browser.