Private by design
No cookies, no PII, no user identifiers. We store performance timings and events on our servers, keyed to a site ID and nothing else.
RUM Monitor Real user monitoring, GDPR-safe
See what real visitors hit, without tracking them.
Add one async snippet and RUM Monitor records the JS errors, failed requests, layout shifts, long tasks and rage clicks your visitors run into. It uses no cookies, collects no PII and assigns no user identifiers.
No cookies or PII
One-line async install
Verified on first visit
RUM Monitor · yourbrand.com
Verified
Total events48.2k
JS errors312
Failed requests97
Avg session2m 41s
Events per dayEventsErrors
MonTueWedThuFriSatSun
Top JS errors
TypeError: Cannot read 'price' of undefined×148
ReferenceError: gtag is not defined×86
POST /api/cart → 500×41
Devices
Desktop56%Mobile39%Tablet5%
Sample dashboard for illustration
Collected from real visitors
JS errors
Failed requests
CLS & long tasks
Rage clicks
Why RUM Monitor
Staging looked fine.
Staging looked fine.
Production is where users are.
A lab test loads one page on one profile. RUM Monitor shows what happens to your actual visitors, on their own phones, laptops and flaky connections.
Frustration you can see
When someone clicks the same spot over and over, something is wrong. Rage clicks lead you to the broken button or the element that looks clickable but isn't.
Live in one line
Paste one async script tag into your site's <head>. Status changes from Pending to Verified as soon as the first visitor loads a page.
What it captures
Four views of real-user experience.
It all feeds a 7-day dashboard that keeps updating, covering everything from the errors people hit to how far down the page they scroll.
Errors
The top JavaScript exceptions and the top failed network and API requests. These are the errors users hit in production, which are rarely the ones you saw in staging.
409/ 7 daysSample errors + failures
- 148
TypeError: Cannot read 'price'
/checkout · Chrome, Safari
- 86
ReferenceError: gtag is not defined
Site-wide · blocked script
- 41
POST /api/cart → 500
Failed request · /product/*
- 33
GET /fonts/inter.woff2 → 404
Failed request · site-wide
Stability
Cumulative Layout Shift and long tasks that block the main thread, measured on real visits. It's field data for the same Core Web Vitals Google looks at.
0.21worst CLSSample · /blog/*
- 0.21
/blog/crm-guide
Layout shift · ad slot loads late
- 0.12
/pricing
Layout shift · web font swap
- 4.2
/checkout
Long tasks over 50ms per visit
- 0.03
/
Layout shift · stable
Frustration
Rage click coordinates show which element people keep hammering. Scroll depth tells you whether they ever get to the part of the page you care about.
23rage clicksSample · 7 days
- 12
#apply-coupon
Rage clicks · /checkout · mobile
- 7
.pricing-toggle
Rage clicks · /pricing
- 4
img.hero
Rage clicks · image looks clickable
- 62%
Avg scroll depth
How far visitors get down the page
Audience
Sessions, average session length, bounce rate, scroll depth and a device breakdown, all in the same 7-day summary.
6.9ksessionsSample · 7 days
Sessions6,920
Avg session2m 41s
Bounce rate38%
Avg scroll62%
Total events48.2k
JS errors312
Device breakdown
Desktop56%Mobile39%Tablet5%
Every number comes from real visits. None of it relies on cookies or personal data.
RUM vs PageSpeed
A lab test is an estimate. Real users are the record.
PageSpeed simulates a page load from Google's servers. RUM Monitor records what your visitors actually get. You want both, because they answer different questions.
compare --lab --field
PageSpeed
One test load from Google's servers.
1test profile
RUM Monitor
Every real visit, on real devices.
Everyvisit
Where the data comes from
Google's servers
Your visitors
Devices & networksWhat the measurement reflects
One profile
Real-world mix
JS errors in production
✕
Failed network & API requests
✕
Rage clicks & scroll depth
✕
SetupBefore you get data
None
One snippet
best for
Debugging a page's load before or after a release.
Run an SEO auditSeeing what visitors actually experience, every day.
Start monitoring
Getting started
Up and running in minutes.
STEP 01Site
Add your domain
Type your domain into RUM Monitor, say yourbrand.com, and it gets its own site ID.
STEP 02Install
Install the snippet
Copy the one-line script tag into the <head> of every page. It loads async, so your pages don't wait for it.
STEP 03Verify
Wait for the first visitor
Status switches from Pending to Verified when the first page load comes in. From there the 7-day dashboard starts to fill up.
Works on WordPress, Shopify and any site where you can edit the <head>Add your site →
Field notes
Checkout conversions dip, and staging looks fine.
Orders drop on a Thursday and staging looks fine, so you open RUM Monitor for the last 7 days. A new TypeError on /checkout started the same day, and #apply-coupon is collecting rage clicks on mobile. Your developer ships a fix that afternoon, and over the next few days the error count falls away.
- Check the 7-day error list the moment a metric moves
- Rage clicks show which element broke, not only which page
- Watch the same counts after the fix to confirm it held
Works better together
RUM shows what users feel. The rest of Linkstonic shows why.
Audit
SEO Audit
The lab side of the story: 14+ technical checks, PageSpeed and Core Web Vitals included, with an AI-written fix for each issue.
Explore SEO Audit
Analytics
BehaviorMind AI
Scores, written insights and a chat you can ask plain questions, all built on your GA4 data.
Explore BehaviorMind
GA4 · last 7 days
Audit
Competitor Analysis
Compare Core Web Vitals, on-page SEO and schema for your site and up to 3 competitors, side by side.
Explore Competitor Analysis
FAQ
Things people ask us.
Privacy, installation and what RUM Monitor measures.
Still have questions?
See which plans include RUM Monitor and how many sites you can add.
Compare plans →Is RUM GDPR compliant?
Yes. RUM Monitor sets no cookies and collects no PII or user identifiers. It stores performance timings and events on our servers, tied only to your site ID, so there is nothing that points back to an individual visitor.
What data does the snippet collect?
JS errors, failed requests, CLS measurements, long tasks, rage click coordinates, scroll depth, session duration and device type. That's the full list. It doesn't collect names, emails, IP-based identifiers or anything else personal.
Will the snippet slow down my site?
It shouldn't. The script tag loads asynchronously, so the browser keeps rendering your page while it downloads. Visitors see your content first, and the snippet starts recording once it has loaded.
How do I install the snippet on WordPress / Shopify?
In WordPress, add it to your theme's header.php or use a header and footer plugin. In Shopify, add it to theme.liquid in the <head> section. Any platform that lets you edit the page <head> works.
What's the difference between RUM and Google PageSpeed?
PageSpeed is a lab simulation run from Google's servers on one test profile. RUM shows what your actual visitors get on their own devices and networks, including JS errors and rage clicks a lab test never sees. Use both.
What's in the 7-day dashboard?
Total events, JS errors, failed requests, sessions, average session length, average scroll depth, bounce rate and a device breakdown. It covers the last 7 days and keeps updating as new visits come in.
How long until my site shows as Verified?
As soon as the first visitor loads a page with the snippet installed. On a busy site that usually means seconds. On a quiet one it can take a few minutes, or you can open the page yourself to trigger it.
Real user data, with nothing personal in it.
Add your domain, paste one line into your <head> and start seeing the errors and dead clicks your visitors hit from the very first visit.
No cookies
No PII
7-day dashboard