Measurement Details¶

Clicking on an individual measurement in any table opens its detail page. This page shows all information collected for that measurement.

General information¶

The top of the page displays the measurement type, timestamp, and status. If the measurement was aborted, the reason is shown.

The detail page includes information about:

• Client – Which client performed the measurement, with a link to the client detail page. Any tags assigned to the client are shown as well.
• Operating System and Browser – The operating system and browser (with version) of the client, if the client reported them. Native studies such as ping, DNS, or traceroute show "None" for the browser.
• ISP and Client IP – The ISP and public IP address of the client.
• URL – The target URL that was measured (if applicable).
• Metadata and notes – Any additional metadata or notes attached to the measurement.

On the right hand side you will find information about the study:

• Study – The study this measurement belongs to, including the subject, type, and study description. A link takes you to the full study detail page. This may show other measurements belonging to the same study.

Statistics and KPIs¶

The Statistics & KPIs section shows the computed KPIs for this measurement. Key metrics are highlighted at the top, with color-coded grades (from excellent to bad) indicating quality. Hovering over a value shows the thresholds used for grading.

Below the key metrics, all remaining KPIs are listed, grouped by category. For example, conferencing measurements show the Join Time (the time from clicking the join button until being in the meeting, in seconds) in the Meeting Join Time group. This KPI has no grade.

For speed tests, the download, upload, and ping values are only shown if the speed test returned them. An aborted speed test may therefore show no values.

For a full reference of all statistic values, see Statistic Values (KPIs).

Video Session¶

For video measurements, an additional section shows the session timeline with key events (e.g., buffering, resolution changes) and a visual representation of the video quality over time. This helps you understand how the quality evolved during the playback.

Lightweight Video Player Performance¶

Video measurements made with the Lightweight Video Player include a Lightweight Video Player Performance section. It summarizes how the video was delivered over HTTP:

• Request Outcomes – How many requests succeeded, failed, or were abandoned, and how many were retried. A request is abandoned when the player cancels a download to switch quality. This does not count as a failure.
• Reliability – The failure rate and retry rate.
• Request Breakdowns – Requests by kind (for example manifest or video segment), media type, HTTP status, HTTP version, and failure reason.
• Bytes Delivered – The total amount of data, by request kind and media type.
• Concurrency and Time Budget – How many requests ran at the same time, and how much of the measurement time had at least one request running (busy) or none (idle).
• Latency – Time to first byte, download time, and total request time, as ranges with median, mean, and 95^th percentile.
• Throughput – Average delivery rates, and the distribution of per-segment rates.

Hover over a value for an explanation. For a description of all fields, see the LightweightVideoPlayerPerformanceClientReport reference.

HTTP Probe Results¶

For measurements of the HTTP prober network study, the HTTP Probe Results section takes the place of the Statistics & KPIs section. Its header shows the probed URL and an overall status. Alerts at the top list how many problems (red) and warnings (yellow) were found, and why the probe was aborted, if it was.

A row of tiles summarizes each check: IPv4 / IPv6, Byte Range, Error Rate, User Agents, HTTP Compliance, and Protocol. Each tile shows whether the check found no issues, warnings, or failures, or whether it did not run. Hover over a tile for a description of the check.

Below the tiles, a section for each check shows the details:

• IPv4 / IPv6 Reachability – The status code, response time, and address over IPv4 and IPv6. A missing DNS record for one of the two is a warning. Different status codes over IPv4 and IPv6 are also a warning.
• Byte Range – The outcomes and response times of byte-range requests. A server that returns the full content instead of the requested range causes a warning.
• Error Rate – How many requests succeeded or returned client or server errors, the server error rate, and the number of cache hits.
• Protocol – The HTTP version, response time, a timing breakdown (DNS, connect, TLS, waiting, download), and any redirects.
• User Agents – The status code returned for each user agent. Different status codes for different user agents cause a warning.
• HTTP Compliance – The number of HTTP compliance violations, with a list of each violation.

Web QoE Score Breakdown¶

For the Web QoE Score, a breakdown section shows how the overall score was computed based on individual metrics, with gauges showing the contribution of each metric to the final score.

Web Domain Breakdown¶

For web measurements, when the sendNetworkPerformanceReports option in Surfmeter Automator was set, a domain breakdown section shows the performance metrics for each individual domain involved in loading the page. This helps identify which domains contributed most to the overall performance. For each domain, we show the slowest and fastest request, as well as overall statistics for that domain.

Connection Detail¶

If the measurement includes connection information (e.g., from mobile client with WiFi or mobile network), a connection detail section shows the connection type, signal strength, etc.

Geolocation¶

If geolocation data was collected for this measurement, a map shows the location where the measurement was taken. This can help identify geographic patterns in performance. Note that geolocation data is only collected if the client device supports it and the user has granted permission.

AI Explain¶

If the AI assistant is enabled, select AI Explain for an AI-generated analysis of the measurement. See AI Explain for details.