Skip to content

EU-based RUM solution Other devs are already building with our MCP & API

Interaction Contentful Paint: what you (don’t) need to know

Alternatieven:

  • Interaction Contentful Paint: the missing link for LCP in SPAs
  • What you (don’t) need to know about Interaction Contentful Paint
  • Interaction Contentful Paint: not your next Core Web Vital
  • Interaction Contentful Paint: a new vital metric or just a browser detail?

Although Interaction Contentful Paint sounds like a combination of Largest Contentful Paint (LCP) and Interaction to Next Paint (INP), I can assure you it is not. Interaction Contentful Paint, or ICP for short, is not a new Core Web Vital either.

As a matter of fact, it is probably not something merchants, agencies or SEO teams need to monitor, let alone worry about. Which is probably a good thing, because the abbreviation alone can already get confusing when it appears next to LCP and INP.

Some Googlers already use iCP instead of ICP to make that distinction a bit clearer. So, for the sake of clarity, we will use iCP in this article when using the abbreviation.

About Interaction Contentful Paint

You could stop reading here. But if you are curious why Chrome needed this browser entry to solve the soft-navigation LCP puzzle, continue reading.

So why write about it?

Because Interaction Contentful Paint plays an important role in how browsers and RUM tools can measure LCP after soft navigations. In other words: it is one of those browser details that most teams do not need to work with directly, but that can still improve the data they rely on.

Why iCP exists

In our previous article about Soft Navigations and Core Web Vitals attribution for SPAs, we covered why Single Page Applications have been difficult to measure.

The short version: users can move through multiple page-like views without triggering a full page reload. For users, that still feels like navigating to a new page. For browsers and metrics, that used to be less obvious.

Soft Navigations help browsers recognize those client-side route changes as navigations. But that created a new challenge for LCP.

LCP was designed around the initial page load. Once a user interacts with the page, LCP is finalized. That works well for normal page loads, but it becomes awkward for soft navigations. Because a soft navigation usually starts with exactly that: a user interaction:

  1. A user clicks.
  2. The route changes.
  3. New content appears.
  4. But the original LCP has already stopped.

That is the gap Interaction Contentful Paint (iCP) helps fill.

What iCP actually is

Interaction Contentful Paint is not a user-facing metric or Core Web Vital. It is a browser performance entry.

That distinction matters.

It is not meant to become a new metric that everyone starts optimizing for. Instead, Chromium engineers introduced it as a building block for soft-navigation LCP: a way for the browser to connect contentful paints to the interaction that caused them.

For soft navigations, this is useful because the browser needs a way to determine the largest relevant paint after the interaction that started the navigation. That value can then be used as the basis for soft-navigation LCP.

So when you see Interaction Contentful Paint (iCP) mentioned, the practical translation is:

This helps Chrome and tooling calculate LCP-like data for soft navigations.

That is the part most teams should care about. Not the raw entry itself.

Why LCP needed something extra

INP and CLS can be split across soft navigations more naturally.

They are based on underlying events and layout shifts that can be grouped into different navigation windows once the browser exposes better navigation boundaries.

LCP is different

The browser finalizes LCP after the first user interaction. And since a soft navigation normally begins with a click, tap or keyboard action, normal LCP cannot simply continue as if a new page load started.

Earlier versions of the soft navigation work experimented with resetting LCP after a soft navigation. But that approach had its own issues.

iCP to the rescue

Interaction Contentful Paint is the alternative direction: do not reset normal LCP, but use a separate browser entry to identify the largest relevant paint after the interaction that started the soft navigation.

That makes it possible to keep normal LCP intact while still getting a meaningful LCP value for client-side navigations.

What not to do with iCP

Let's cover what you do not need to do with it. Because most teams do not need to:

  • collect interaction-contentful-paint entries manually;
  • add it as a separate KPI;
  • explain it in monthly performance reports;
  • optimize for it as if it were a new Web Vital;
  • compare it directly with INP, LCP or CLS.

That would make things more confusing than useful.

For most site owners, the useful metric remains LCP. The difference is that RUM tooling can now get better LCP attribution for soft navigations under the hood.

In RUMvision’s case, this logic is handled through the web-vitals library and our own attribution model. So customers should not have to think in terms of raw Interaction Contentful Paint entries.

They should simply get better data.

What it can improve

The value of Interaction Contentful Paint is mostly indirect. It can help RUM tools show whether the largest visible content after a soft navigation appeared quickly enough.

That matters for situations such as:

  • opening a product page inside an SPA;
  • moving from a listing page to a detail page;
  • navigating between checkout steps;
  • loading a new route after a menu click;
  • rendering client-side content after a filter or tab interaction.

Without this kind of browser support, these moments are harder to attribute correctly.

With it, RUM tools can better answer:

  • Did the new view become useful quickly after the user navigated there?

That is a much more practical question than:

  • What is our Interaction Contentful Paint score?

A browser detail

It's a browser detail, but an important one. Interaction Contentful Paint is a good example of something that is technically important, but not necessarily something every performance stakeholder needs to understand in detail.

That is not a bad thing.

A lot of the web platform works this way. Browsers expose lower-level signals. Libraries such as web-vitals turn those signals into something easier to collect. RUM tools then translate the data into dashboards, diagnostics and recommendations.

Interaction Contentful Paint sits near the bottom of that chain.

It helps make the measurement model better, so the end result becomes more useful.

Should you care about iCP?

Maybe a little. But surely not in the way you care about LCP, INP or CLS.

You do not need to treat Interaction Contentful Paint as your next performance KPI. You do not need to create a separate dashboard for it. And you probably do not need to explain it to every stakeholder involved in site speed.

What you should care about is what it enables:

  • better LCP attribution for soft navigations;
  • cleaner SPA route-level data;
  • fewer metrics being assigned to the wrong URL;
  • more useful RUM diagnostics;
  • better input for performance recommendations.

That is where the impact is.

In short

Interaction Contentful Paint sounds like a new metric. For most teams, it is better understood as a browser detail that helps make another metric better.

LCP remains the metric users and teams should recognize. Interaction Contentful Paint helps browsers and RUM tooling calculate a meaningful LCP value after soft navigations.

So no, this is probably not something you need to monitor directly.

But if you rely on RUM data for SPAs, it is one of the reasons that data can become more accurate.

Share