The Core Web Vitals (CWV) metrics evaluate page load time, responsiveness, and visual stability as part of Google’s page experience ranking. The Core Web Vitals are Largest Contentful Paint, First Input Delay, and Cumulative Layout Shift. CWV metrics are available in the following locations in Botify:

The following are required to access your CWV field data in Botify:

Field metrics are only available on your most visited URLs, and Botify queries the Google API to request CWV metrics based on your most clicked pages.

After submitting your Chrome UX Report (CrUX) API key into Botify’s project settings, the CWV metrics will be available in the “Web Vitals - Field Data” section within the Rankings category in Botify filters and columns. The following metrics are included:

The Interaction to Next Paint (INP) metrics replaced the First Input Delay (FID) metrics on 12 March 2024, but FID metrics remain available as filters for historical purposes. FID metrics are not included in ActionBoard guidance pages or the EngagementAnalytics dashboard.

In addition to the values from the CrUX, the scores and density are reported for each of the Core Web Vitals:

Botify retrieves the aggregate values, the lowest, and the highest aggregate scores for each CWV metric, as described below.

The aggregate value represents the 75th percentile of page loads collected during a rolling period of the previous 28 days. Here is a detailed explanation from Google on why they use the 75th percentile value of all visits to a page to classify the overall performance of that page or site.

Example: The Homepage in this example reports an LCP: Agg of 5.2s on Desktop and 5.8s on mobile. This means 75% of user experiences have an LCP slower or equal to 5.2s and 5.8s on desktop and mobile, respectively.

The lowest aggregate score for the selected dimension based on the previous 28 days of available data. Min demonstrates the best-performing score for CWV.

When looking at a URL without filtering by device, the Min will display the device type with the lowest aggregate score. If your data is segmented by another dimension, for example, by Pagetype, the Min score for a specific Pagetype will report the URL within that Pagetype with the lowest Min score. This can reveal how well the best page within that segment is performing.

Example: The Homepage in this example reports an LCP: Min of 5.3s. Since the LCP: Min score in this example is based on the individual URL dimension, the Min score is calculated based on the device with the lowest LCP: Min available, which is Desktop in this example.

The highest aggregate score for the selected dimension, based on the previous 28 days of available data. Max demonstrates the worst-performing score for CWV.

When looking at a URL without filtering by device, the Max will display the device type with the highest aggregate score. If your data is segmented by another dimension, for example, by Pagetype, the Max score for a specific Pagetype will report the URL within that Pagetype with the highest Max score. This can reveal how well the worst page within that segment is performing.

Example: The Homepage in this example reports an LCP: Max of 5.8s. Since this data is focused on an individual URL, the Max score is calculated based on the device with the highest LCP: Max available, which is Mobile in this example.

The CWV score is based on thresholds established by Google for each Core Web Vital metric, based on a page’s aggregate value, as follows:

Example: In the following example, the LCP score is "Need Improvement" for all devices because they range from 2.8 to 3.9 seconds. The URL with the "Good" score falls well below the 2.5-second threshold.

The density for each CWV is the ratio of user experiences with "Good", "Need Improvement", or "Poor" LCP scores.

Example: In the following example:

Core Web Vital metrics are only available on pages with enough traffic because Botify only ingests data from real users visiting your site (i.e., field data), not lab data.

CWV data is also available in RealKeywords.

You can create custom reports to track your site’s CWV performance on a trended basis. Monitor the KPIs and dimensions that matter to your company and easily send the data to key stakeholders at your preferred cadence.

A key advantage of analyzing your Core Web Vitals in Botify is the ability to cross-reference these metrics with other available dimensions and segment your data in many ways, as in the following examples:

Use the Segments Editor to create your custom-defined categories based on the URL path of a page. Pair these segments with CWV metrics to analyze and compare the page experience for specific areas of your site.

CWV metrics can vary drastically depending on the type of device with which a user visits your site. Since a device’s viewport dimensions and processing power can shift the performance of a page, it is beneficial to monitor the same page across multiple device types.

You can use HTML Extracts to isolate specific components and features of your site to understand better the impact these components may have on your CWV performance. This example demonstrates the HTML Extraction tool to check if a third-party vendor’s carousel exists on a page. You can then apply the extracted value to compare CLS performance across the pages and determine if there is a noticeable shift in CLS between the pages with and without the carousel.

See also: