Skip to content
Moga Digital

Field note · Search & AI Visibility ·  · 2 min read

Use Core Web Vitals to investigate customer friction

A visitor taps the enquiry button and waits. Nothing happens, so they tap again. Your analytics may record a visit with no enquiry, but that will not explain what went wrong. Performance measurements can show whether the page itself got in the way.

What Core Web Vitals measure

Core Web Vitals measure three parts of that experience. Google's guidance (opens in a new tab) sets a good threshold for each and says at least 75% of page loads should meet it, checked separately for mobile and desktop. One fast test on the office network does not show that visitors have a good experience.

Three measurements and their good thresholds

  • Loading: LCP

    Largest Contentful Paint is when the largest visible element, often the headline or main image, appears. Good is 2.5 seconds or less.

  • Response: INP

    Interaction to Next Paint is how quickly the page visibly responds when someone taps, clicks, or types. Good is 200 milliseconds or less.

  • Stability: CLS

    Cumulative Layout Shift is unexpected movement, such as a late banner pushing a button down. Good is 0.1 or less.

These describe how the page behaves. Sales and lead quality need their own measures.

Layout can shift after the page has loaded (opens in a new tab), while someone is using it, and reserving space for late content can prevent a particular shift.

Read a change against the customer journey

Suppose mobile responsiveness gets worse after a release and fewer visitors finish the enquiry form. That is a reason to look at the form on the affected devices. It is not yet proof that slow responses caused the drop. The same release might have changed form validation, or marketing might have changed where visits come from.

A useful report puts the performance change beside the customer action and the release date. Keep the page group, device type, and measurement window visible, and check there is enough real-visitor data before you conclude anything. Then reproduce the problem in a lab test.

Google says (opens in a new tab) its ranking systems use Core Web Vitals, but good scores do not guarantee a high position. The measurements answer a narrower question about how the page behaves.

Give the report an owner

Ask one person to review significant changes after each release and decide what to investigate. Write down each finding with its page and the fix you propose. After the fix, confirm the behavior improved, then watch the field data over its reporting window.

The fix has worked when the enquiry form responds as soon as a visitor acts, and field data from the devices people use confirms it. Keep enquiries and lead quality in the same report, so the team can see whether the whole journey improved.

Written by the Moga principals.

See the Search & AI Visibility service

Find out how the models see you.

A fixed-price audit, written findings, and a clear answer on whether GEO pays for you yet.

Book a call