Audit Core Web Vitals: Complete Guide to Technical SEO Excellence

Google's Core Web Vitals are not just technical metrics. They directly influence your search rankings and user experience. They also affect your visibility in AI search results from platforms like ChatGPT and Perplexity. If you want to rank in Google and get cited by AI platforms, you need to audit core web vitals regularly. This guide walks you through the complete audit process step by step so you can identify problems and fix them before they damage your rankings.

A Quick Guide to Auditing Core Web Vitals

You're auditing core web vitals to measure three critical performance metrics: Largest Contentful Paint (LCP) measures loading speed, Interaction to Next Paint (INP) measures responsiveness, and Cumulative Layout Shift (CLS) measures visual stability. Google uses these metrics as ranking factors, and AI platforms are increasingly citing fast, stable pages. A proper audit reveals which pages need optimisation and how urgently.

What Are Core Web Vitals (and Why They Matter for SEO and AI Search)

Core Web Vitals are three user-centric performance metrics that Google introduced in 2020. They measure loading performance (LCP), interactivity (INP), and visual stability (CLS). Google confirmed these are ranking factors, and they apply to both desktop and mobile versions of your site.

More importantly for modern SEO, AI platforms are increasingly biased towards fast, well-structured pages when generating citations and recommendations. Pages with poor core web vitals are less likely to be featured in AI Overviews and AI-generated content. Your core web vitals audit is therefore an essential part of your AI SEO strategy.

Unlike vanity metrics, core web vitals directly correlate with user behaviour. Fast-loading pages have lower bounce rates, higher time-on-page, and better conversion rates. When you audit core web vitals, you're not just optimising for algorithms. You're improving the actual experience your visitors have when they arrive on your site.

Understanding the Three Core Web Vitals Metrics

Each core web vital measures a different dimension of user experience. LCP captures the first impression of loading speed. INP reveals how responsive your page is to user input. CLS measures whether the page layout shifts unexpectedly during interaction. Together, these three metrics create a complete picture of performance.

Largest Contentful Paint (LCP)

LCP measures how long it takes for the largest visible element on the page to render. This could be a hero image, a video thumbnail, a large heading, or a text block. Google's threshold is 2.5 seconds or less for a "good" LCP score. Anything above 4 seconds is considered "poor."

In practice, LCP tells you whether your page feels fast to users. It's the moment when visitors can actually see and interact with your main content. A poor LCP is one of the most common core web vitals issues, typically caused by unoptimised images, render-blocking JavaScript, or slow server response times.

Interaction to Next Paint (INP)

INP measures the latency between a user's input (click, tap, or keystroke) and the page's visual response. Google's good threshold is 200 milliseconds or less. INP replaced First Input Delay (FID) as Google's official interactivity metric in March 2024.

Think of INP as the responsiveness of your page. When you click a button, does it respond instantly, or does your browser pause for a moment before reacting? Poor INP usually indicates JavaScript processing bottlenecks, especially on pages with heavy interactive elements or lots of event listeners.

Cumulative Layout Shift (CLS)

CLS measures unexpected layout shifts that occur during the page's lifetime. A layout shift happens when visible elements move position without user input, such as when an image loads belatedly or an ad inserts itself into the layout. Google's good threshold is 0.1 or less.

CLS is invisible to raw loading speed metrics but deeply affects user experience. Imagine reading an article and suddenly a banner ad pushes all the text down. That's a layout shift. During your audit, you'll often find that CLS issues stem from ads, third-party widgets, or unspecified image dimensions.

What We Found When Auditing an eCommerce Client's Core Web Vitals

To show you what a real audit uncovers, here's what we found during a technical SEO overhaul for an Australian eCommerce meal delivery company. The audit revealed critical core web vitals issues hiding in plain sight:

These aren't unusual numbers. Most sites we audit have similar problems hiding beneath the surface. The difference is whether you find them before or after they cost you rankings.

After fixing these issues over a six-week sprint (compressing images to WebP, adding dimensions, restructuring headings, fixing broken URLs), the client's core web vitals improved and organic revenue grew 91% within eight months. You can read the full eCommerce AI SEO case study for the complete breakdown.

Tools You Need for a Core Web Vitals Audit

Before you start your audit, you need the right toolkit. Each tool serves a different purpose, from quick page-level checks to full site-wide crawls. Here are the essential tools:

For enterprise-scale audits, Lighthouse CI and SpeedCurve integrate performance testing into your development workflow, catching regressions before they reach production.

How to Audit Core Web Vitals: Step-by-Step Process

A proper core web vitals audit follows a structured methodology. Start with a high-level assessment, then dive into detailed investigation of problem pages, and finish with a prioritisation framework for fixes.

Step 1: Gather Data from Google Search Console

Log into Google Search Console and navigate to the Core Web Vitals report. You'll see pages grouped by performance status (good, needs improvement, poor) across mobile and desktop. This report shows you real-world experience data from your actual users.

Document three things:

This initial assessment tells you the scale of the problem and where to focus your effort.

Step 2: Run a Full Site Crawl with Screaming Frog

Set up Screaming Frog SEO Spider to crawl your entire site and export a list of all indexable pages with their URLs. Then use the PageSpeed Insights API or manually test a representative sample of 20-30 pages across different templates and sections.

Record the LCP, INP, and CLS score for each page, along with the specific issues identified by PageSpeed Insights. You'll start to see patterns: perhaps all product pages have poor LCP, or all blog posts have CLS issues due to a common widget.

Step 3: Analyse Results and Identify Root Causes

Group your results by page type or template. Look for patterns in what's causing poor metrics. Common culprits include:

Use Google Chrome's Lighthouse tool and DevTools Performance tab to investigate individual pages in detail. The flame chart shows you exactly which operations are taking the longest. The filmstrip shows you visually when elements render and when layout shifts occur.

Step 4: Prioritise Pages and Issues

Not all core web vitals problems have equal impact. Prioritise based on:

Create a prioritised list with quick wins at the top and longer-term optimisations below. This approach lets you show quick progress while planning more complex fixes.

How to Fix Common Core Web Vitals Issues

LCP, INP, and CLS issues require different solutions. Understanding which metric you're trying to improve guides your optimisation strategy.

Fixing Largest Contentful Paint (LCP)

To improve LCP below the 2.5-second threshold, focus on these three areas:

In our eCommerce client audit, we found 590 images over 100KB that were directly responsible for poor LCP scores. Compressing these to WebP format and adding proper dimensions was the single biggest improvement.

Fixing Interaction to Next Paint (INP)

INP problems stem from JavaScript processing. The key strategies are:

Sometimes the fastest JavaScript is JavaScript you never send to the browser.

Fixing Cumulative Layout Shift (CLS)

CLS fixes are often the quickest to implement:

When we audited our eCommerce client, 100% of their images lacked size attributes. This single issue was responsible for most of their CLS problems. Adding width and height attributes to all 982 images eliminated the layout shifts within the first two weeks of implementation.

How Core Web Vitals Impact Search Rankings and AI Search Visibility

Google explicitly stated that core web vitals are ranking factors. Pages with poor core web vitals may be outranked by faster alternatives, particularly in competitive niches where search engine optimisation is intense.

More significantly for your AI SEO strategy, pages with fast, stable rendering are more frequently cited by AI Overviews and AI search systems. AI platforms favour pages that load quickly because they can analyse the content faster and provide better responses to users. A page that takes 5 seconds to load is less useful to an AI system than a page that loads in 1 second.

We saw this firsthand with our eCommerce client. After fixing their core web vitals issues, the site earned 126 Google AI Overview citations and 12 ChatGPT citations within six months. Pages that previously had poor performance scores weren't being cited at all. The technical foundation unlocked AI visibility that content quality alone couldn't achieve.

Enterprise SEO services should integrate core web vitals optimisation into broader technical SEO programmes. Your content marketing strategy is only as effective as the technical foundation supporting it.

Enterprise-Scale Core Web Vitals Auditing

Large sites require a different approach to auditing and optimisation. What works for a 50-page website doesn't scale to thousands of pages across multiple properties.

Enterprise-scale auditing requires automation, continuous monitoring, and integration with your development workflow. The essential components are:

Building a performance-first culture is essential for maintaining good core web vitals as your site grows. Establish a topical authority strategy for your content so that core web vitals optimisation is built into your editorial workflow from the start.

Monitoring Core Web Vitals After Your Audit

Your audit is only the beginning. Ongoing monitoring ensures your improvements stick and new issues are caught early.

Set up these monitoring systems to stay on top of your performance:

Share before-and-after metrics with stakeholders to justify ongoing investment in performance optimisation. In our experience, the most successful clients are those who treat core web vitals as an ongoing programme rather than a one-time project.

Frequently Asked Questions

What's the difference between lab data and field data?

Lab data (from Lighthouse) simulates a specific device and connection speed in a controlled environment. Field data (from CrUX) comes from real browsers of real users visiting your pages. Both matter: lab data helps you debug specific issues, while field data reflects actual user experience. Google's ranking algorithm uses field data.

How often should I audit core web vitals?

You should monitor continuously using Google Search Console and your analytics platform. A formal full-site audit takes 4-6 weeks depending on site size and complexity. Plan quarterly audits to catch regressions and validate that fixes are working.

Does my entire site need to pass core web vitals?

Technically no, but you should aim to get as many pages as possible into the "good" category. Pages that fail core web vitals are less competitive in search results and less likely to be cited by AI search platforms. We recommend targeting at least 80% of pages in good status as a baseline standard.

Do core web vitals affect AI search visibility?

Yes. AI platforms like ChatGPT, Perplexity and Google AI Overviews prefer citing pages that load quickly and render cleanly. Poor performance creates a barrier to AI indexation. In our eCommerce case study, fixing core web vitals was a prerequisite for earning 169 AI citations across five platforms.

What's the most common core web vitals issue?

From our audits, missing image dimensions and unoptimised images are by far the most frequent culprits. They cause both CLS issues (layout shifts from missing width/height attributes) and LCP issues (slow loading from oversized files). Fixing images first typically delivers the biggest improvement.

Can I fix core web vitals without a developer?

Some fixes are straightforward, like compressing images or adding dimensions in your CMS. Others, like optimising JavaScript execution or implementing Lighthouse CI, require development resources. Prioritise the fixes you can handle yourself and bring in a developer for the technical changes.

How long does it take to see ranking improvements after fixing core web vitals?

Google typically processes core web vitals changes within 28 days through the CrUX dataset, which updates monthly. You may see ranking improvements within 1-3 months after fixes, but the impact depends on how competitive your keywords are and how significant the improvements were.

Should I prioritise mobile or desktop core web vitals?

Google uses mobile-first indexing, so mobile core web vitals are generally more important for rankings. However, your analytics data should guide the decision. If most of your traffic and revenue comes from desktop, optimise both but start where the business impact is greatest.

Your Next Steps in Technical SEO Excellence

Auditing core web vitals is one component of a comprehensive technical SEO programme, but it's often the component with the most immediate impact on rankings, user experience and AI search visibility. Start with your highest-traffic pages, test them in PageSpeed Insights, document the results, and work systematically through your improvement list.

If you're managing performance optimisation across hundreds or thousands of pages, or if you need a structured AI SEO strategy that integrates technical excellence with content strategy, talk to our technical SEO consultant team. We've generated over $20M in client revenue by connecting performance optimisation to measurable business outcomes.