INP Replaced FID in March. Most Law Firm Sites Still Fail It. Here Is the Fix List

Short answer: Interaction to Next Paint (INP) replaced First Input Delay as a Core Web Vital on March 12, 2024. It measures how long the page takes to respond to any tap or click, across the whole visit, and the passing threshold is 200 milliseconds. First Input Delay only measured the first interaction and almost every site passed it. INP is failed by most law firm sites we test, and the causes are the same four things: a chat widget, a tag manager full of third-party scripts, a page builder that ships everything on every page, and a hero slider.

What does INP measure?

The delay between a user interaction (tap, click, key press) and the next time the screen updates. Google reports the worst such delay on the page, ignoring outliers, and a page passes if 75 percent of visits come in under 200 milliseconds. Between 200 and 500 is "needs improvement"; above 500 is a fail.

Field data comes from Chrome users, so the number Google uses is the number real visitors experienced, mostly on phones. Lab tests on a fast laptop routinely pass pages that fail in the field.

Why do law firm sites fail it?

Because the main thread is busy when the visitor taps. Four causes account for nearly every failure we see.

Chat widgets are the worst offender by a distance. The vendors' own scripts are large, they load early, and they attach listeners to everything. If the firm gets fewer than five real chat leads a month, the widget is costing more than it returns.

How do you check the site?

Three tools, all free.

1. PageSpeed Insights. Enter the URL. The top section, "Discover what your real users are experiencing", is field data; that is what Google uses. If it says "no data" the site does not get enough Chrome traffic for a field score, and lab data is the fallback.
2. Search Console, Core Web Vitals report. Shows which URLs fail and groups them by cause. Check it monthly.
3. Chrome DevTools, Performance panel. Record a visit, tap a menu, look for the long task. This is where the specific script gets named.

Check the practice pages and the contact page, not only the home page. The home page is usually the best-tuned page on the site and the least visited.

What is the fix order?

By effect per hour of work:

1. Remove or defer the chat widget. One change, often the whole fix.
2. Empty the tag manager of anything not tied to a current campaign or a report someone reads.
3. Kill the slider. Static hero, one image, compressed.
4. Defer every non-critical script (defer or async attributes; most builders have a setting).
5. Reduce builder overhead by disabling modules, or plan the rebuild.

The first three take an afternoon and move most failing sites into the passing range.

Does it affect rankings?

Core Web Vitals are a minor ranking signal and Google has said as much repeatedly. A fast site does not outrank a slow one with better content. But the signal is a tiebreaker between similar pages, and in a map-pack-adjacent practice-area query the pages are often similar. More importantly, a page that takes half a second to respond to a tap on a phone loses the visitor before the ranking matters. The fix pays on conversion whether or not it pays on rank.

What does not work?

• Caching plugins alone. They speed up delivery, not interaction. INP is about what happens after the page arrives.
• A "speed optimization" service that adds another script to lazy-load the other scripts.
• Upgrading the hosting to fix a JavaScript problem. The server is not the bottleneck.

What should a firm do before the next core update?

Run PageSpeed Insights on five pages, fix the widget and the tag manager, and re-check in 28 days, which is how long the field data window is. That is inside the technical work in the law firm SEO service. The free visibility check includes a Core Web Vitals pass across the site's key pages, so the firm knows which pages fail and why before anyone quotes a rebuild. The wider technical checklist is in the Los Angeles law firm SEO guide.