Search Console Core Web Vitals Report for Marketers
Read the Search Console Core Web Vitals report: LCP, INP and CLS thresholds, URL groups, what marketing tags change and how to validate fixes.
The Core Web Vitals report groups your URLs as Good, Need improvement or Poor based on how real Chrome users experience loading, responsiveness and visual stability. Marketers often cause the problems, through tags, banners and widgets, so it's worth understanding.
- Three metrics: LCP (loading), INP (responsiveness) and CLS (visual stability).
- Good thresholds: LCP ≤ 2.5s, INP ≤ 200ms, CLS ≤ 0.1, measured at the 75th percentile.
- Data comes from real Chrome users over 28 days, grouped by similar URLs.
- A URL group's status is its worst metric.
- Marketing tags and widgets often drive INP and CLS problems.
Checked 4 November 2026 (CET) against Search Console Help and Google Search Central documentation. Search Console reports and rollouts change often, and some features only appear for eligible properties, so confirm in your own property. "Our view" marks MentionX opinion. Ledgerline is a fictional company used for illustration.
01How does the report work?
From Google's Core Web Vitals report help:
- Separate Mobile and Desktop reports.
- URLs are grouped by similar experience, and each group gets a status for each metric.
- The group's status is its worst metric: Poor LCP makes the group Poor even if INP and CLS are Good.
- Values are the 75th percentile of real-user experiences over the last 28 days.
02What are the thresholds?
From web.dev's Web Vitals guide:
| Metric | Measures | Good | Poor |
|---|---|---|---|
| LCP | Time to render the largest visible element | ≤ 2.5s | > 4s |
| INP | Delay responding to interactions | ≤ 200ms | > 500ms |
| CLS | Unexpected layout movement | ≤ 0.1 | > 0.25 |
03Why does speed matter for AI search?
Slow, script-heavy pages are harder for crawlers to fetch and render. See Page speed and AI retrieval.
Our view: treat Poor mobile groups on money pages as a conversion issue first and an SEO issue second.
04Who fixes what
| Metric | Common causes | Typical owner |
|---|---|---|
| LCP | Large hero images, slow server, render-blocking CSS or JS | Developer, with design for images |
| INP | Heavy JavaScript, third-party scripts, chat widgets, tag bloat | Developer, with marketing for tags |
| CLS | Images without dimensions, late-loading banners, ads, fonts | Developer, with content and marketing |
Marketing often owns the cause: tag managers, consent banners, chat widgets and A/B testing scripts all affect INP and CLS.
05Troubleshooting
| Problem | Cause | Fix |
|---|---|---|
| "Not enough data" | Too little Chrome real-user data | Use lab tools like PageSpeed Insights |
| Group fixed but still Poor | Data covers 28 days | Validate fix and wait |
| Desktop fine, mobile poor | Slower devices and networks | Prioritise mobile |
| Whole site poor after a change | New script or template | Annotate and check recent tag additions |
06From report to fix: a working method
- Start with Mobile, Poor. Click the issue with the most URLs, for example "LCP issue: longer than 4s (mobile)".
- Open an example URL group. Groups are URLs Google treats as similar, usually one template. One fix often clears the whole group.
- Run the example URL in PageSpeed Insights. The top section shows real-user data (the same source as the report); the lower section is a lab test with specific diagnostics.
- Name the element. For LCP, the diagnostics identify the largest element, often a hero image or heading. For CLS, they list the elements that shifted.
- Write a ticket with the metric, the template, example URLs, the element and a suggested fix.
- After deployment, click Validate fix. Validation monitors for 28 days because the data window is 28 days.
- Annotate the release in the Performance report.
07Fix ideas by metric
| Metric | Fix | Marketing involvement |
|---|---|---|
| LCP | Compress and correctly size hero images; serve modern formats; preload the hero image | Design hero sections with smaller images |
| LCP | Remove sliders and carousels at the top of the page | Agree to a single hero message |
| INP | Remove unused tags; delay non-essential scripts until after interaction | Audit tag manager quarterly |
| INP | Load chat widgets only on pages where they matter | Decide which pages need chat |
| CLS | Set width and height on images and embeds | Brief content editors |
| CLS | Reserve space for cookie banners, promos and ads | Don't inject promo bars above content |
| CLS | Use font-display settings that avoid large swaps | Choose fewer web fonts |
08Edge cases
- Validation "failed" after a fix. Some URLs in the group still have the problem, often a second template or a page with a different hero.
- Report shows nothing for a new site. Real-user data needs enough Chrome visits; use PageSpeed Insights lab data until then.
- Good in lab tests, Poor in the report. Lab tests use one device and network; real users include slower phones and networks. Trust the report for status, the lab for diagnosis.
- Seasonal campaigns. A heavy campaign banner can push a template into Poor for the campaign's duration. Check the report after major campaigns go live.
- A/B tests. Testing tools that hide content until variants load can hurt LCP and CLS. Ask for server-side tests on key templates.
09A quarterly tag audit template
| Tag or script | Owner | Pages it loads on | Still needed? | Can it load later? |
|---|---|---|---|---|
| Analytics | Marketing ops | All | Yes | No |
| Chat widget | Sales | All | Pricing, contact only | Yes |
| Heatmap tool | Product marketing | All | Only during research | Yes |
| Old A/B test script | Growth | All | No | Remove |
Fill it in with your developer and make removals part of the routine.
10Questions practitioners ask
Should we chase a perfect score? No. The report uses Good, Need improvement and Poor. Getting key templates to Good is the goal.
Do we need separate fixes for desktop? Usually mobile fixes help desktop too. Check both reports after fixes.
Why does a single page show a different status from its group? The report shows group-level status; individual pages may vary.
11Ledgerline walkthrough: fixing CLS on blog posts
- The Mobile report showed blog posts in Need improvement for CLS.
- PageSpeed Insights on an example post showed a newsletter banner injected above the content after load.
- Marketing agreed to move the banner below the first section and reserve its space.
- After the release, the SEO lead clicked Validate fix and annotated the date.
12Troubleshooting Core Web Vitals
| Symptom | Likely cause | Who to involve |
|---|---|---|
| LCP Poor on templates with hero images | Large images, slow server response, render-blocking resources | Developer, design |
| INP issues on interactive pages | Heavy JavaScript, long tasks, third-party scripts | Developer, tag manager owner |
| CLS on article pages | Ads, banners or embeds without reserved space, late-loading fonts | Developer, marketing |
| "Not enough data" | Too little real-user traffic | Use lab tests in PageSpeed Insights |
Third-party marketing tags are a common cause. Our view: review the tag manager quarterly and remove tags nobody uses.
13Where this fits in the monthly routine
Check the Core Web Vitals overview monthly for movement between Good, Need improvement and Poor. Escalate only new Poor groups that include key templates.
14Worked example: Ledgerline's tag audit
Ledgerline is a fictional accounts-payable software company. Details and numbers are illustrative.
Ledgerline's mobile product pages moved to "Need improvement" for INP. The marketing team's tag list showed two A/B testing scripts from finished experiments and a chat widget loading on every page. Removing the old scripts and loading chat only on pricing and contact pages brought INP back within the Good range in a later 28-day window, after validation.
Walkthrough
- Open Experience > Core Web Vitals.
- Click Open report for Mobile.
- Read the Why URLs aren't considered good table: metric, status and URL groups.
- Click an issue, then an example URL group.
- Open the example URL in PageSpeed Insights for lab detail.
- Share the issue with your developer with the metric and example URLs.
- After the fix, click Validate fix.
15Try it yourself
List every third-party script your marketing team has added (tag manager tags, chat, heatmaps, A/B tools). For each, note who owns it and whether it's still used. Bring the list to your developer alongside the Core Web Vitals report.
16Quick quiz
1. Which three metrics does the report use?
Answer: LCP, INP and CLS.
2. What are the good thresholds?
Answer: LCP 2.5 seconds or less, INP 200 milliseconds or less, CLS 0.1 or less.
3. What data does the report use?
Answer: Real-user data from Chrome, at the 75th percentile over 28 days.
4. How is a URL group's status set?
Answer: By its worst metric.
17What should you check before the next lesson?
- You know the mobile status of your key page groups.
- You listed marketing-owned scripts.
- Fixes are validated in the report.
- Read Page speed and AI retrieval.
Next: Links report. Or return to the Search Console for Marketers track.
18Common questions
Do Core Web Vitals affect rankings? Google says page experience is one of many signals; good content still matters most.
Why is my page missing from the report? It may not have enough real-user data, so it isn't reported.
What replaced FID? INP (Interaction to Next Paint) replaced First Input Delay as a Core Web Vital in 2024.
Questions people ask
3 answersDo Core Web Vitals affect rankings?
+
Google says page experience is one of many signals; good content still matters most.
Why is my page missing from the report?
+
It may not have enough real-user data, so it isn't reported.
What replaced FID?
+
INP (Interaction to Next Paint) replaced First Input Delay as a Core Web Vital in 2024.
Sources
- Search Console Help, Core Web Vitals reportsupport.google.com
- web.dev, Web Vitalsweb.dev
- All accessed 4 Nov 2026.