Last updated: March 27, 2026
About Website Monitoring
The Websites Monitoring section gives you a curated, opinionated view of your frontend health — combining user behavior metrics, Core Web Vitals, and session-level detail in one place.
The visualizations offer high-level insights into page loads, user sessions, and web vitals, while flexible filters let you quickly narrow down by browser, location, route, or user. With rich contextual data, such as session traces, custom events, and performance metrics, you can pivot to related views and uncover root causes from multiple angles.
Each instrumented website gets its own card on the landing page and its own detail view with three tabs, shown above, Overview, Web Vitals, and Sessions.
If you're looking for a conceptual overview of how Dash0 captures real user sessions, Core Web Vitals, and frontend-to-backend traces using OpenTelemetry, see the Website Monitoring with OpenTelemetry and Dash0 Guide.
The Websites Monitoring section is organized into the following areas:
Global Controls
- Filter — narrows data across all tabs by Path, Environment, Deployment Name, or Deployment ID. More here...
- Command Menu — provides quick access to common actions and navigation. More here...
- Time Picker — sets the time range for all views. More here...
Website Detail Tabs
- Overview — a high-level dashboard showing traffic volume (Sessions, Page Views, Users, Bounce Rate, Backend Requests, Errors), Core Web Vital scores, top visited pages, and a session geography map. More here...
- Web Vitals — a per-vital deep-dive with p75 scores, Good/Needs Improvement/Poor gauges, performance-over-time charts, and a page-level breakdown table for each of LCP, INP, and CLS. More here...
- Sessions — a searchable, filterable list of individual user sessions with summary charts, and a detail panel that shows the page flow and events for each session. More here...
Website List
- Website cards — each card on the landing page shows the website name alongside its top-level KPIs: Sessions, Requests, LCP p75, INP p75, and CLS p75. Values that exceed their threshold are highlighted in red.
Relationship to Web Events
Websites and Web Events relate to each other the same way Services and Traces do. Websites provides a structured, high-level experience — pre-built dashboards, web vital gauges, and session timelines — built on top of the raw browser.* events collected by the Web SDK. Web Events gives you direct access to that underlying event stream for custom filtering, grouping, and correlation with backend telemetry. More here...
Core Web Vitals
Websites surfaces three Google-defined performance metrics at the p75 percentile — meaning 75% of real user experiences are at or below the displayed value. The supported vitals are:
- LCP — Largest Contentful Paint — measures how long it takes for the largest visible element (image or text block) to fully render. Good: < 2.5 s.
- INP — Interaction to Next Paint — measures how quickly the page responds to user input. Good: < 200 ms.
- CLS — Cumulative Layout Shift — measures how much page content shifts unexpectedly during load. Good: < 0.1.
Google uses these metrics to rank pages in search results, so improving them benefits both user experience and SEO. Reference: Web Vitals (web.dev)
Further Reading
-
Monitor Website Overview. Explains the Overview tab — how to read the traffic KPIs, interpret the web vital gauges, use the Top Visited Pages chart, and understand the Sessions by Geography map.
-
Analyze Web Vitals. Covers the Web Vitals tab in detail — including how to read the p75 gauge, interpret the Performance by Page Loads chart, identify the worst-performing pages from the per-vital pages table, and drill into sessions with poor scores.
-
Investigate Sessions. Describes the Sessions tab — how to read the session list, filter by path or error state, open the session detail panel, follow the page flow timeline, and navigate to the full session in Web Events.
-
Understand Web Vitals. Reference page covering the definition, thresholds, and measurement methodology for LCP, INP, and CLS — including why p75 is used instead of the median or maximum.
