Google is coming up with a new responsiveness metric that could replace First Input Delay. In a recent HTTP Archive Almanac article about CMS use across the globe, the author mentioned that almost all platforms score great on the First Input Delay (FID), a Core Web Vital metric.
Every year the HTTP Archive publishes several articles on the state of the web in which one chapter is about CMS. This article raised an interesting point about how the First Input Delay metric has lost its meaning and talked about Google developing a new metric. The best app development companies are closely monitoring this development.
First Input Delay
Core Web Vitals are a group of user experience metrics that provide a glimpse of how well web pages perform for users, and FID is one of them. It determines how fast a browser can respond to user interaction with a website, such as the response time when a user clicks a button on a website.
How everyone wins an FID trophy
The article throws light on how most CMS score well on FID. The platforms that score less manage to get relatively high scores that lag behind just by five percentage points.
The author even wrote that FID is excellent for most CMSs on desktop, with all platforms scoring a perfect 100 percent. Most CMSs also deliver a good mobile FID except Bitrix and Joomla.
What has happened to FID is that it is a metric where everyone is a winner, which means there really isn’t much a reason for the metric to exist. Right?
The article also mentioned how Google is busy creating a new metric for measuring response latency and responsiveness.
This article is even more interesting because it reveals Google is working on a new input delay metric. Learning about this metric can make top mobile app development companies in India prepare for the future.
The main point to understand about this metric is that it isn’t based on a single interaction. Still, it measures a group of individual interactions that compose a user action.
Another article highlighted the importance of responsiveness of all user inputs and how capturing each event’s entire duration, not just the delay, can help.
Group events together that take place as part of the same user interaction and define that interaction’s latency as the maximum duration of its events.
It will create an aggregate score for all interactions that take place on a single page throughout its complete lifecycle.
Now the aim is to design a metric that better captures the end-to-end latency of individual events and offers a comprehensive picture of the overall responsiveness of a page.
This new metric aims to capture the full event duration, from initial user input till the next frame is painted after all the event handlers have run. So, interactions will be measured rather than individual events in the future.
The article also explained that Chrome engineers are exploring two new approaches for measuring interaction latency. The first is Maximum Event Duration and, the second is Total Event Duration.
So, FID is going away?
It is possible that FID could be a part of Core Web Vitals, but its relevance may decline. The Chrome team is taking feedback on various approaches to measuring interaction latency, so many new updates can be expected soon.
Meanwhile, you can reach out to us if you are looking for progressive web app development and other mobile app development services. We will keep you updated on the Core Web Vitals.
