Suggest an editImprove this articleRefine the answer for “What is FID (First Input Delay)?”. Your changes go to moderation before they’re published.Approval requiredContentWhat you’re changing🇺🇸EN🇺🇦UAPreviewTitle (EN)Short answer (EN)**FID (First Input Delay)** is a Core Web Vitals metric that measures the delay between a user's first action on a page (click, tap, key press) and the moment the browser actually starts reacting to it. **Key point:** FID shows whether the user feels "lag" during the first interaction, and this metric is now gradually being replaced by the more precise INP (Interaction to Next Paint).Shown above the full answer for quick recall.Answer (EN)Image**FID (First Input Delay)** is a Core Web Vitals metric that measures **the delay between a user's first action on a page (click, tap, key press) and the moment the browser actually starts reacting to it**. In simpler terms: FID shows **whether the user feels "lag" during the first interaction**. If a person clicks a button and the page "freezes" for a fraction of a second, that's a bad FID. --- ### **What FID actually measures** - not the page's overall speed, - not the loading speed, - but **the interface's first reaction to a user's action**. --- ### **Google's norms** - Good: **< 100 ms** - Needs improvement: 100-300 ms - Poor: **> 300 ms** --- ### **Why a bad FID happens** The main culprit is **heavy JavaScript**, which: - runs for too long, - blocks the browser's main thread, - prevents the page from reacting quickly to a click. --- ### **Why this metric matters** FID reflects **the feeling of a site's "responsiveness."** Even if a page loaded fast, but a button doesn't react, the user feels irritated, and this worsens behavior, conversions, and SEO. > FID is now gradually being replaced by the more precise **INP (Interaction to Next Paint)** metric, which measures responsiveness not only of the first, but also of subsequent interactions.For the reviewerNote to the moderator (optional)Visible only to the moderator. Helps review go faster.