Google Is Creating A New Core Web Vitals Metric
In a recent HTTPArchive Almanac article about CMS use worldwide, the author mentioned that all platforms score great on the First Input Delay (FID), a Core Web Vitals metric and that Google is working on a new metric, which one might presume may replace First Input Delay (FID).
Every year the HTTPArchive publishes multiple articles about the state of the web. Chapter 16 is about content management systems (CMS). The article was written by a Backend Group Manager and Head of Web Performance Wix engineer and reviewed and analyzed by various Googlers and others.
The article raised an interesting point about how the First Input Delay metric has lost meaning and mentioned how Google was developing a new metric.
First Input Delay
Core Web Vitals are a group of user experience metrics designed to provide a snapshot of how well web pages perform for users and First Input Delay (FID) is one of those metrics.
FID measures how fast a browser can respond to user interaction with a website, like how long it takes for a response to happen when a user clicks a button on a website.
The thing about FID is that all major content management systems, like WordPress, Wix, Drupal and others all have lightning fast FID scores.
Everyone Wins An FID Trophy
The article first mentions that most CMS’s score exceptionally well for FID. And the platforms that score less well still have relatively high scores that lag behind by only 5 percentage points.
The author wrote:
“FID is very good for most CMSs on desktop, with all platforms scoring a perfect 100%. Most CMSs also deliver a good mobile FID of over 90%, except Bitrix and Joomla with only 83% and 85% of origins having a good FID.”
What’s happened to FID is that it’s basically a metric where everyone gets a trophy. If almost all sites score exceptionally well, if everyone gets a trophy, then that means there really isn’t much of a reason for the metric to exist because the goal of getting this part of the user experience fixed has been reached.
The article then mentions how Google (the Chrome team) is currently creating a new metric for measuring responsiveness and response latency.
The article continued:
“The fact that almost all platforms manage to deliver a good FID, has recently raised questions about the strictness of this metric.
The Chrome team recently published an article, which detailed the thoughts towards having a better responsiveness metric in the future.”
Input Response Delay Versus Full Event Duration
The article linked to a recent Google article published on Web.dev titled, Feedback wanted: An experimental responsiveness metric.
What’s important about this article is that it reveals that Google is working on a new input delay metric. Knowing about this metric can give a head start to preparing for what is coming in the future.
The main point to understand about this new metric is that it isn’t measuring just single interactions. It is measuring groups of individual interactions that are part of a user action.
While the article cited in HTTPArchive cited a November 2021 article that asks for publisher feedback, this new metric has been under development for awhile now.
A June 2021 Web.dev article outlined these goals for the new measurement:
“Consider the responsiveness of all user inputs (not just the first one)
Capture each event’s full duration (not just the delay).
Group events together that occur as part of the same logical user interaction and define that interaction’s latency as the max duration of all its events.
Create an aggregate score for all interactions that occur on a page, throughout its full lifecycle.”
The Web.dev article states that the goal is to design a better metric that encompasses a more meaningful measurement of the user experience.
“We want to design a metric that better captures the end-to-end latency of individual events and offers a more holistic picture of the overall responsiveness of a page throughout its lifetime.
…With this new metric we plan to expand that to capture the full event duration, from initial user input until the next frame is painted after all the event handlers have run.
We also plan to measure interactions rather than individual events. Interactions are groups of events that are dispatched as part of the same, logical user gesture (for example: pointerdown, click, pointerup).”
It’s also explained like this:
“The event duration is meant to be the time from the event hardware timestamp to the time when the next paint is performed after the event is handled.
But if the event doesn’t cause any update, the duration will be the time from event hardware timestamp to the time when we are sure it will not cause any update.”
Two Approaches To Interaction Latency Metric
Web.dev explains that the Chrome engineers are exploring two approaches for measuring the interaction latency:
- Maximum Event Duration
- Total Event Duration
Maximum Event Duration
An interaction consists of multiple events of varying durations. This measurement bases itself on the largest duration out of a group.
Total Event Duration
This is a sum of all the event durations.
FID Is Likely Going Away?
It’s possible that FID could remain as part of Core Web Vitals but what’s the point if ever site scores 100% on it?
For that reason, it’s not unreasonable to assume that FID is going away sometime in the relatively near future.
The Chrome team is soliciting feedback on different approaches to measuring interaction latency. Now is the time to speak up.
Citations
Feedback wanted: An experimental responsiveness metric
Towards a better responsiveness metric
You must be logged in to post a comment Login