Discussion starter: a technical SEO question, posted with an answer from Niraj Raut to open the thread. If you have dealt with this on a site, reply with what you saw, especially where it differs.
- Technical SEO
Most INP problems on a publisher site come from third-party tags. Has anyone shown a traffic effect from fixing INP alone, separate from UX gains?
Disclosure: Niraj Raut, who posted this answer, runs the SEO consultancy linked at the end of it.
1 reply
-
adminAdmin
There is no convincing public evidence of a meaningful search traffic gain from fixing Interaction to Next Paint alone, and Google has consistently described Core Web Vitals as one part of page experience, with relevance and helpful content carrying much more weight. For a publisher, the stronger case for fixing third-party tag problems is everything else they cause: slower, janky pages, lower engagement, fewer pages per session, and often worse ad performance. Those effects are measurable and usually larger than any ranking change. If you want to know whether INP fixes move traffic on your site, you can test it by section, but set expectations for a small effect at most.
What INP measures and why tags hurt it
INP measures how quickly a page responds to user interactions such as taps, clicks and key presses, across the whole visit. Third-party scripts, including ad libraries, analytics, consent tools, recirculation widgets and social embeds, often run long tasks on the main thread, which blocks the page from responding. On publisher sites with many tags, a tap on a menu or a “read more” button can wait noticeably while scripts finish. That is exactly what INP captures.
Where the benefits of fixing it show up
Outcome Likelihood of measurable change Field INP in Chrome UX Report and Search Console High, if the fixes are real Engagement: pages per session, scroll, return visits Moderate to high Ad viewability and revenue per session Often positive, but depends on which tags were changed Search rankings and traffic Low; small if any Common fixes for tag-heavy publisher pages
- Audit every tag. List what each does, who owns it and whether it is still needed. Remove the ones nobody can justify.
- Load non-essential scripts later, after the page is interactive, or on interaction.
- Limit ad refresh and heavy ad formats that run continuous work on the main thread.
- Review the consent tool, which on some sites is itself a major source of long tasks.
- Consider moving third-party scripts off the main thread where tools support it, testing carefully for breakage.
- Replace heavy embeds with lightweight placeholders that load the full embed on click.
- Set a performance budget for tags, with approval required for anything new.
If you want to test the search effect
Pick two comparable sections of the site, fix tag behaviour on one, and leave the other unchanged for a few months. Compare search clicks and impressions between them, alongside field INP. Because field data takes weeks to update and search effects, if any, are small, the test needs time and matched sections. Expect the engagement and revenue differences to be clearer than the search difference.
Hypothetical example:
A news publisher’s mobile INP is poor on article pages. A tag audit finds 60 third-party scripts, a dozen of them from vendors no longer under contract, plus an aggressive ad refresh and a consent tool loading synchronously. The publisher removes unused tags, delays social embeds until tapped, lowers ad refresh frequency and loads the consent tool more efficiently. Field INP moves into the good range over the next month. Pages per session and ad viewability improve noticeably, and revenue per session rises despite fewer ad refreshes. Search traffic shows no change that can be separated from normal news-cycle variation.
Watch for this:
Selling an INP project internally as a search traffic project risks it being judged a failure when traffic does not move. Present it as an engagement and revenue project with possible search benefits, and measure it on the outcomes it is most likely to change.
Look at the whole visit, not just the first page
INP is measured over the entire visit, and on publisher sites the worst interactions often happen after the first page: opening the menu on the second article, dismissing a late-loading overlay, tapping through a gallery. Lab tests that load a single page miss these. Use field data by template and, where you can, real-user monitoring that records which interactions are slow and which scripts were running at the time. That usually points to a small number of culprits, often an ad refresh cycle, a sticky video player or a recirculation widget, and fixing those few delivers most of the improvement. It also gives the ad operations team specific evidence rather than a general complaint about performance.
Keep it fixed
Tag problems return, because new vendors and campaigns add scripts continuously. Put tag approval into a process with performance checks, monitor field INP by template, and review the tag inventory quarterly. Publishers that fix INP once and do not govern tags usually find themselves back where they started within a year.
Fix third-party tag problems for engagement and revenue, expect little or no direct search traffic gain, test by section if you need evidence, and put tag governance in place so the gains last.
Need help with this on your own site?
Niraj Raut works with businesses in Nepal, Australia, the UK, Europe and the US on technical SEO, ecommerce SEO, local SEO and AI search.
Add a reply Cancel reply
Replies are open to approved members. Log in or apply to join.