What is INP and how is it different from the old FID metric?
PICTURE THIS: DJANGO MVT
Simple meaning
INP looks at interaction latency throughout the page life, not only the first input.
WHY — Performance instead of guessing?
Why interviewers care about Performance:
who only read docs from people who shipped.
and tied to Frontend work.
Name the idea, why it exists, then one short example.
End with when you use it and one common pitfall.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 1INP looks at interaction
latency throughout the page life, not only the first input.
- 2Long tasks on the
main thread from hydration or big lists hurt it.
- 3I break up work,
use transitions, and defer non-critical JS to keep input snappy.
- 4Give an example
One tiny concrete case you can say aloud.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
INP looks at interaction latency throughout the page life, not only the first input. Long tasks on the main thread from hydration or big lists hurt it.