See what every user actually experienced — not just the average.

It replaces the "guessing game" with a Session Receipt. Instead of asking the user for screenshots or their internet speed, you simply look up their ID in Witnes. You'll see an up to 30-day chronological history that proves if the lag was caused by their local Wi-Fi, a slow response from your server (API), or a frontend render issue.

No. While we capture deep technical data, we translate it for your Support team. We clearly label bottlenecks as "Slow Wi-Fi," "API Latency," or "Frontend Render" so anyone can identify the root cause of a ticket in seconds without escalating to engineering.

Most tools show you what the user did (video); Witnes shows you why the site failed them (data). We are a lightweight diagnostic tool focused on the technical evidence — network waterfalls, API timings, and device health — rather than just a video of a mouse moving.

Negligible. The w.min.js script is under 5kb and loads asynchronously. We use the PerformanceObserver API for passive monitoring and navigator.sendBeacon to transmit data. This ensures we capture every detail without ever blocking the main thread or impacting your Core Web Vitals. See Security & Trust for the technical privacy and transport model.

We pull raw data from the Resource Timing API for every interaction. By calculating the delta between requestStart and responseStart, we isolate TTFB (Server processing). We then compare this to the user's effective bandwidth and RTT to determine if the bottleneck is the user's connection or your infrastructure.

Yes, automatically. We intercept the browser's History API (pushState and replaceState). When a user navigates between "pages" in an SPA, Witnes detects the route change and captures a new performance snapshot after a brief "settle" period, ensuring soft-navigations are tracked just as accurately as full page loads.

No. Witnes does not use cookies, fingerprinting, or any form of cross-site tracking. We collect only performance metrics — no personal data is stored. Because we operate without cookies and don't process personal data under GDPR's definition, no consent banner is required. You get full analytics coverage without interrupting your users.

All data is stored exclusively on servers in Germany — it never leaves the European Union. We use daily rotating salt hashes so IP addresses are never stored in any identifiable form. Your data is yours. We never sell it, share it, or give access to third parties. Ever. You can read the full technical breakdown on our Security & Trust page.

Think of Witnes as GA with privacy built in from the ground up — plus performance analytics on top. You get the same traffic picture: page loads, unique visitors, channels, geography, devices, and campaigns. No cookies, no consent banner, no GDPR headaches. And unlike GA, every visit is connected to real performance data — load times, long tasks, and individual session diagnostics. So you don't just know someone visited, you know what they experienced when they got there. Our traffic analytics are currently in Beta and growing fast — but if you've been flying blind since dropping GA, this is your replacement.

Hotjar and LogRocket are great tools — they show you what users did through session replay and interaction tracking. Witnes focuses on a different question: not what they did, but what they experienced technically. Instead of recording screens, we capture the full performance evidence — network waterfalls, real load times, SPA transitions, long tasks, and individual session timelines. And because traffic, performance, and visitor diagnostics are all connected in one place, you get the complete picture without stitching together multiple tools. No screen recording, no cookie consent, no personal data stored. Just the technical story of every visit.