![]() Some visitors may get distracted more easily and stop browsing your page until they can quickly interact with the content.Īnd while the score differs for an individual’s interaction with the site, also not all visitors’ actions are considered relevant to the score. The First Input Delay score is unique for each visitor to your website. It can reduce the time it takes for the browser to register an event. It feels like the browser is stuck in a traffic jam that can be streamlined by minimizing JavaScript files. It can make the website feel unresponsive as the browser waits to determine the next steps, contributing to the long input latency. Why? Because the JavaScript code that is being loaded can change the subsequent actions of the browser. In particular, it applies to large JavaScript files the browser must execute before running any event listeners. Input delay occurs when page elements, like images or scripts, are loaded without a user request.Īccording to Google, one of the reasons behind long input delays is JavaScript execution. ![]() That’s because it would be easy for developers to game FID by separating the event handler from the task associated with the event. The actual processing or updating of the web page as a consequence of that interaction is not measured by FID. FID is a metric that helps you address that and ensure that loading those critical resources doesn’t make your website feel clunky and irresponsive. The first time a user interacts with your page is fundamental in their experience and perception of your web performance.įurthermore, most of the blocking of the browser’s main thread occurs in the first moments of a web page’s life cycle – that’s when critical resources are loaded. FID only measures the first user interactionįID is about first impressions, making it a user experience metric. This is because they often don’t run on the browser’s main thread and have different constraints. Continuous types of user interaction, like zooming or scrolling the page, can’t be accurately measured using this metric. The events that count as user input measured by FID must be discrete (finite). ![]() Technically speaking, this is because the browser’s primary thread is processing a different request. However, the hyperlink you clicked on might not respond immediately. Imagine visiting an online store and expecting a given element to open on the spot. In other words, FID reflects the latency between the user interaction (when you click or tap on something like a link or a button) and the time the browser responds to your action and starts processing it. The time between these two events is called input delay (also known as input latency.) 12.1 NEXT STEPS What is the First Input Delay (FID)?įirst Input Delay is a real-user web performance metric that tracks the time between the moment a user first interacts with a web page after entering it to when the browser can start processing that interaction (when the browser’s main thread is idle).
0 Comments
Leave a Reply. |