Core Web Vitals
Core Web Vitals are a set of metrics created and promoted by Google to provide unified guidance for quality signals that are essential to delivering a great user experience on the web.
Go to the Core Web Vitals help center article to discover them more clearly.
Contentsquare (Core) Web Vitals collection is based on the Web Vitals library to ensure data consistency with market standard. This table references the updates of the underlying library or other changes that might affect your Web Vitals metrics in Speed Analysis RUM.
| Date of change | Change | Impact |
| 14.02.2024 | Update web vitals library from version 3.3.2 to 3.5.2 |
You can see the detailed changelog of these versions here. Here are a few items that might have an impact: |
| 01.06.2023 | Update web vitals library from version 3.1.0 to 3.3.2 |
You can see the detailed changelog of these versions here. Here are a few items that might have an impact - Defer CLS logic until after onFCP() callback (#297): fixing a bug introduced in v3.1.0 - Prevent LCP being reported for hidden prerendered pages (#326): fixing a bug introduced in v3.1.0
|
| 25.04.2023 |
Update web vitals library from version 2.1.4 to 3.1.0
|
You can see the detailed changelog of these versions here. Here are a few items that might have an impact - Report initial CLS value when reportAllChanges is true (#283) - Ignore TTFB for loads where responseStart is zero (#281) - [BREAKING] Report TTFB after a bfcache restore (#220) - Add support for pre rendered pages (#233) |
Largest Contentful paint replacing Load time
Once Speed Analysis RUM is enabled, the Contentsquare load time metric will be replaced by the Largest Contentful Paint (LCP) metric. LCP is an established Web Vitals metric meaning that the largest content of the page is loaded, it’s more meaningful to track it as the main loading metric.
FAQs
What browsers and devices are supported with Web Vitals in RUM?
- CLS: can only be tracked on browsers and devices that are based on the chromium engine. Chromium is a technology created by Google and used for some browsers such as Google Chrome, Edge, Opera, Samsung Internet, Brave, and a few others.
- LCP, FID: can be captured on Chromium based browsers and the Firefox browser.
- TTFB, FCP: can be capture on Firefox and Safari.
Can I track web vitals for navigations in a Single Page Application?
No, it is not possible. When a user navigates within a Single Page Application, they are not really loading a new page. SPA navigations are based on a dynamic refresh of the content of the page. It’s not a top-level page navigation.
However, that does not mean we won’t collect any data on a SPA-based website. For example, a user doing direct access to a landing page, or refreshing a page, is a top-level page navigation and Web Vitals will be collected for natural page views.
Are artificial pageviews supported?
We cannot track Web Vitals for Artificial Pageviews.