Browser monitoring's PageViewTiming
event sends each data point as a separate event as soon as it is available. Because we do not restrict the timing, you can receive first paint or first interaction data regardless of when it fires. This document describes why and how to use PageViewTiming
and its attributes to query data about your site, component loading, and user performance metrics, both from visual and responsiveness standpoints.
Why use PageViewTiming?
If your application uses asynchronous or dynamic pages, you may need additional details about site or component loading. But pages can load content in many different ways, and users control when they interact with that content. This is why some user-centric performance metrics happen outside the standard window onload (page load time) in the Browser agent.
For example, users may become impatient and begin clicking as soon as content is on the webpage. Or, they may wait to use the page until long after content is loaded.
The PageViewTiming
event provides a more real-time delivery mechanism that does not have a dependency on any other event. The additional metrics can help you understand how users experience your site, both from visual and responsiveness standpoints.
Support for Google's Core Web Vitals
We now, with the release of agent version 1177, have full support for Google's Core Web Vitals for 2020. The metrics that make up Core Web Vitals will evolve over time. The current set for 2020 focuses on three aspects of the user experience—loading, interactivity, and visual stability—and includes the following metrics (and their respective thresholds):
Core Web Vitals metrics include loading, interactivity, and visual stability.
- Largest Contentful Paint (LCP): measures loading performance. To provide a good user experience, LCP should occur within 2.5 seconds of when the page first starts loading.
- First Input Delay (FID): measures interactivity. To provide a good user experience, pages should have a FID of less than 100 milliseconds.
- Cumulative Layout Shift (CLS): measures visual stability. To provide a good user experience, pages should maintain a CLS of less than 0.1.
For each of the above metrics, to ensure you're hitting the recommended target for most of your users, a good threshold to measure is the 75th percentile of page loads, segmented across mobile and desktop devices.
To learn more, watch our Nerd Days talk on perceived performance.
Detailed visual, interactivity, and responsiveness metrics
The BrowserInteraction
and PageView
events end their reporting when they receive the page window load (or window load and AJAX) timing. However, paint and interactivity metrics can happen at any time. PageViewTiming
delivers these metrics as a separate event to:
- Account for the variability in this timing.
- Avoid setting an arbitrary timeout.
- Prevent holding
BrowserInteraction
andPageView
events indefinitely.
Additional data | Comments |
---|---|
| The Using |
| This new metric, available with agent version 1163, In addition, we now report the cumulative layout shift (CLS) score attribute with LCP. This attribute is reported as Largest Contentful Paint is one of three metrics identified by Google as the Core Web Vitals. LCP values up to 2.5 secs are considered "Good", between 2.5-4.0 secs considered "Needs Improvement", and above 4.0 secs considered "Poor." |
| With the addition of The In addition, we now report the cumulative layout shift (CLS) score attribute at the moment of the user's first interaction. This attribute is reported as First Input Delay is one of three metrics identified by Google as the Core Web Vitals. FID values up to 100 ms are considered "Good", between 100-300 ms considered "Needs Improvement", and above 300 ms considered "Poor." For a more detailed explanation, see the Browser release notes. |
| Cumulative Layout Shift (CLS), available with agent v1177, is an important, user-centric metric for measuring visual stability because it helps quantify how often users experience unexpected layout shifts—a low CLS helps ensure that the page is delightful. This is one of three metrics identified by Google as the Core Web Vitals. Cumulative Layout Shift is one of three metrics identified by Google as the Core Web Vitals. CLS scores up to 0.1 are considered "Good", between 0.1-0.25 considered "Needs Improvement", and above 0.25 considered "Poor." |
| You can review different types of activities with the |
| This is the Id, if specified, of the |
| This is the reported size of the |
| The In addition, we now report the cumulative layout shift (CLS) score attribute with |
| The windowLoad event, available with agent v1177, is fired when the whole page has loaded, including all dependent resources such as stylesheets and images. Supporting documentation and browser compatibility for the Window Load event can be found in MDN docs. In addition, we now report the cumulative layout shift (CLS) score attribute with |
| The In addition, we now report the cumulative layout shift (CLS) score attribute with |
Compatibility and requirements
In addition to Browser's installation requirements, the PageViewTiming
event requires Browser agent version 1153 or higher and a Browser Pro subscription. Follow our Browser agent release notes to find out when new metrics are released.
These metrics are supported by the following browser versions. For unsupported browsers, no PageViewTiming
events will be recorded.
Metrics | Supported browser versions |
---|---|
|
|
|
|
|
|
| These metrics require the
|
| This metric is currently supported by all browsers on desktop and mobile. Compatibility matrix via MDN documentation. |
| This metric is currently supported by all browsers on desktop and mobile. Compatibility matrix via MDN documentation. |
| This metric is currently supported by all browsers on desktop and mobile. Compatibility matrix via MDN documentation. |
Query your event data
Here are some sample queries for the event data to help you get started.
その他のヘルプ
さらに支援が必要な場合は、これらのサポートと学習リソースを確認してください:
- Explorers Hubでは、コミュニティからのサポートを受けたり、ディスカッションに参加したりすることができます。
- 当社サイトで答えを見つけて、サポートポータルの使用方法を確認してください。
- Linux、Windows、およびmacOS向けトラブルシューティングツールであるNew Relic Diagnosticsを実行してください。
- New Relicのデータセキュリティとライセンスドキュメント をご確認ください。