Skip to content

Web services.
Simply looked after.

Core Web Vitals in plain English

Core Web Vitals describe three aspects of page experience: how quickly the main content appears, how promptly interactions respond and how stable the layout stays. They are called LCP, INP and CLS. Useful performance work begins with the actual problem a visitor experiences, not only a coloured score.

Useful context

  • Choose a public page and an important mobile customer journey.
  • Record whether a report uses real-user field data or a controlled lab test.

How it works

  1. Translate the measures into symptoms

    A late hero image relates to loading. A menu button that reacts slowly relates to interaction responsiveness. Text moving while someone tries to tap a link relates to layout stability. These are different problems and may need different changes even on the same page.

  2. Read the evidence source

    Field data reflects eligible real-user experiences over a reporting period; lab testing runs under controlled conditions. A small site may lack enough field data. That absence is not a performance pass or failure, and one fast test on your own laptop is not a universal result.

  3. Prioritise a visible, repeatable problem

    Record the affected page, device and action. For example, note that the mobile menu is difficult to open while several widgets load. Ask for investigation tied to that symptom instead of installing several optimisation tools that may compete or change unrelated behaviour.

  4. Compare after a controlled change

    Repeat a similar lab check and test the customer journey yourself. Field reports can take time to reflect new experiences. Keep before-and-after evidence and make sure an apparent score improvement has not removed useful content, broken a form or made the design less accessible.

What to check

  • The metric is connected to a real customer experience.
  • Lab and field results are not being presented as interchangeable.
  • Any improvement preserves the page's important content and functionality.

Sources and further reading

Platform features can change. Check the provider’s current guidance before changing a live service.

A little help, when you need it

What can we help with?

Leave a message for PresGro support. This is not live chat. Please don’t include passwords or payment details.

Daily, 08:00–18:00 UK time

We aim to give an initial reply within 3–4 support hours. This is a target, not a guaranteed response or resolution time. Help outside these hours may be available.

Your details are used to respond to this enquiry. Read our privacy notice. Never send passwords. Prefer email? help@presgro.com.

Visit the support centre →