Challenge 2: Explain FID vs INP — Possible Solution
====================================================================

WHY A GOOD FID SCORE COULD STILL FEEL SLUGGISH
----------------------------------------------------
FID (First Input Delay) only measured ONE specific moment: the delay
between a user's very FIRST interaction with the page (their first
click, tap, or keypress) and the browser actually beginning to process
that interaction. Once that single measurement was taken, FID had
nothing further to say about the rest of the user's session.

This creates an obvious gap: a page could respond quickly to that one
very first interaction (a good FID score) while every SUBSEQUENT
interaction — a second button click, typing in a search box, opening a
dropdown menu — could each take much longer to actually update the
screen, without any of that ever being reflected in the FID metric at
all. A user scrolling and clicking around a page for two minutes could
experience dozens of laggy, unresponsive interactions after that first
one, and FID would remain blind to every single one of them.

WHY INP WAS INTRODUCED TO CATCH THIS GAP
--------------------------------------------
INP (Interaction to Next Paint) measures the responsiveness of EVERY
interaction throughout the page's entire lifetime, not just the first
one — and specifically, it measures the full round trip from the user's
input to the browser actually PAINTING the next visual update in
response (not just when processing merely began, which is all FID
tracked). This directly targets the exact blind spot FID had: a page
that's fast on its first interaction but sluggish afterward will now
show a poor INP score, since INP is effectively looking at the worst (or
a high-percentile) interaction across the whole session, not a single
early sample.

WHY THIS WORKS AS AN EXPLANATION
------------------------------------
The core distinction is BREADTH of measurement: FID sampled a single
early data point and declared the page's "responsiveness" based on
that one moment; INP evaluates responsiveness continuously across the
user's actual usage of the page. This is precisely why the chapter
frames INP as measuring "the full lifecycle of a user interaction, not
just first input delay" — INP was designed specifically to close the
measurement gap that let a genuinely sluggish page still report a
seemingly good score under the old metric.