Formlyy Journal

Form INP: guide to optimize your complex interactions

Apr 7, 2026 · 9 min read · By Arthur Goudard

Analysis of the performance of a complex web form on mobile

When a prospect hits "Next" and nothing happens for a second, they don't think "the main thread is blocked."

He just says: “this site is boring”.

And that's exactly the problem. The INP measures this concrete feeling, not a theory of performance.

On a qualification funnel, each slow interaction removes a little confidence. In the end, it's the conversion that pays the bill.

Why the INP has become a priority

Since INP was highlighted in Core Web Vitals, the objective has been clear: measure the real responsiveness of interactions (click, tap, keyboard), not just the initial loading. The official documentation web.dev on INP is very explicit on this point.

In acquisition, that changes everything. A form can load quickly and still be slow to use. And in this case, you lose leads after the click, not before.

The 4 most common causes of complex forms

1. JavaScript too heavy at interaction time

Synchronous validation, overloaded libraries, multiple listeners: everything goes to the main thread. The web.dev guide on INP optimization recommends precisely reducing and cutting up these treatments.

2. Validation that blocks the interface

When validating a field freezes the form for 300 to 800 ms, the user experiences latency even if the rule is "correct".

3. Third-party scripts that run at the wrong time

Chat widgets, analytics, AB testing: it's not their presence that kills the INP, it's their timing.

4. Too many visual updates after an entry

Each interaction that follows up too many components or CSS calculations increases the perceived latency.


INP prioritization grid to win quickly

Construction siteConversion impactEffortPriority
Cut blocking validationVery highMediumImmediate
Report non-critical third-party scriptsStudentLowImmediate
Simplify Heavy Field ComponentsStudentMediumHigh
Diagnose long tasksVery highMediumHigh

The API PerformanceLongTaskTiming from MDN helps to objectify these blockages on the navigation side.

Field method in 5 steps

1. Isolate critical interactions

On a lead gen funnel, I measure first: CTA click, first field focus, intermediate validation, submission.

2. Trace slow interactions

We capture interactions that exceed your internal thresholds to understand whether the debt comes from the front end, a third-party script or business logic.

3. Remove “false complexity”

Many rules can be rescheduled (local pre-check, server verification afterwards), as explained in this client vs. server validation comparison.

4. Protect the mobile version

The mobile absorbs CPU peaks less well. If you only have one priority this week, make this one. This is also a direct continuation of the slow forms article.

5. Couple performance and accessibility

A responsive and readable form advances better than a “technically compliant” but laborious form. This is the same logic as in our RGAA/WCAG accessibility guide.

What to aim for in practice

  • smooth critical interactions on real mobile;
  • absence of perceptible blocking after click/tap;
  • zero peak latency on essential qualification stages.

The goal is not to “win a score.” The objective is to maintain the salesperson momentum between the announcement and the appointment.

FAQ

Frequently asked questions

Does INP replace all other performance indicators?

No. He completes the reading. LCP and CLS remain useful, but INP is often the closest signal to actual form frustration.

Should we remove all third-party scripts to improve INP?

No. Above all, they must be loaded and executed at the right time, prioritizing user interaction above the rest.

Can we improve the INP without redoing the entire front?

Yes. Quick wins often come from slicing validations, reducing synchronous processing, and cleaning up field components.

About the author

Arthur Goudard

My name is Arthur Goudard. I share what I see in the field when a marketing strategy needs to turn warm interest into a useful conversation, then into a clear appointment.

View Arthur Goudard on LinkedIn

Sources

Keep reading

Read next

Continue reading

Back to blog