Skip to main content

LCP by acquisition channel

LCP by acquisition channel without noise

Georgi avatar
Written by Georgi
Updated over 3 weeks ago


What is LCP by acquisition channel

LCP by acquisition channel shows the Largest Contentful Paint (LCP) value across different acquisition channels (e.g. newsletter_april). This lens helps you identify which acquisition channels deliver a slower experience for your users.

The list shows only acquisition channels that generated traffic to your website during the selected period.

LCP is the most popular vital from the Core Web Vitals and represents the loading time of the largest element on the page.



Healthy LCP by acquisition channel sample


Should you worry

A healthy LCP by acquisition channel lens looks all green. Some acquisition channels may be greener than others, but as long as there's no yellow or red, it’s considered healthy. The greener the acquisition channel, the better.

Unhealthy LCP by acquisition channel sample

In the example below, LCP by acquisition channel shows that direct is both most popular and the slowest acquisition channel. This often leads to a higher bounce rate, more exits, and lower conversion rates.

Resolving unhealthy LCP by acquisition channel

Go-to action plan to resolve an unhealthy LCP by acquisition channel:

  1. Ask Uxi to analyze your LCP by acquisition channel values and suggest improvements.

  2. Use Filters to focus on the slow acquisition channel in your LCP by acquisition channel, then look across the other LCP lenses to find which ones show the slowest LCPs with the most pageviews.

  3. Simulate LCP of the suspected lens to see if fixing it will resolve the slow LCP by acquisition channel. If yes, this is where the resolution focus should be.

  4. Use an automated LCP optimization tool like Navigation AI to improve your LCP by acquisition channel values.

  5. Once you’ve improved LCP, set an alert to be the first to know if it starts worsening again.

Try it yourself

Discover how your website performs with real user data.

Did this answer your question?