Ritim documentation

Install it

npm

npm install @ritim/browser-sdk

import { init } from '@ritim/browser-sdk';

init({ projectKey: 'P-ABC123' });

Script tag

<script async src="https://cdn.ritim.io/latest/rum.min.js" data-project-key="P-ABC123"></script>

That is the whole integration either way. The SDK detects navigations itself, decides when a measurement is ready, and sends it — no router plugin, and nothing to run per page.

Your choice above is remembered, so every sample in these docs shows the path you picked.

Core Web Vitals from real visitors

LCP, INP, CLS and TTFB as your users experienced them, at p75, split by route, device and country.

Nothing personal leaves the page

No cookies, no fingerprint, no persistent identifier — so no consent banner. See what the SDK never sends.

Every deploy is a release

Next.js and Nuxt builds are labelled automatically, so a regression points at the change that caused it.

Catch it before it merges

The GitHub Action audits your preview deployment and comments the numbers on the pull request.

Start reading

QuickstartFrom a new project to your first measurement, in about five minutes.

Installnpm or a script tag, and how to choose between them.

Next.jsA client component in the root layout, and what Next tells us about your build.

NuxtA .client.ts plugin, and the build id Nuxt already gives you.

ConfigurationEvery option, with defaults and precedence.

GitHub ActionMeasure a preview deployment on every pull request.

MetricsWhat is collected, how it is scored, and where the bands come from.

Plans and limitsWhat the free plan allows, and what happens at the ceiling.