A Core Web Vitals audit checks whether your website is slow to load, slow to respond, or unstable while people are using it. It is used to identify the causes of poor LCP, INP and CLS results, then turn those findings into a practical set of actions for your marketing, development or management team.
Google describes Core Web Vitals as metrics that measure real-world user experience for loading performance, interactivity and visual stability. The current metrics are Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift. Google Core Web Vitals documentation
For most businesses, the problem is not simply “the site is slow”. The real issue is knowing where the slowdown starts, which pages are affected, and whether the work is worth doing before other SEO or development tasks.
SEO Strategist provides a consultant-led Core Web Vitals audit for businesses that need a senior SEO view on website performance, especially where speed, user experience, development constraints and organic visibility overlap.
Use this audit when you know the site is underperforming, but need to know what is worth fixing first.
What a Core Web Vitals audit covers
The audit focuses on the pages and templates that have a real role in the business. That may include the homepage, service pages, pricing pages, ecommerce category pages, product pages, landing pages or high-traffic organic pages.
It looks at how quickly the main content appears, how responsive the page feels after a user clicks or taps, and whether elements move unexpectedly while the page is loading.
A poor result may come from heavy images, weak hosting, page-builder bloat, tracking scripts, theme issues, unnecessary JavaScript, font loading problems, embedded tools, or a template that has become too heavy over time.
For a South African SME, this often means working inside real-world constraints: a WordPress or WooCommerce site with years of plugins, a Shopify store weighed down by apps, a page builder such as Elementor or Divi, a previous agency handover, or hosting that has not kept up with the site’s growth.
The purpose is to move from vague warnings to usable decisions.
Instead of saying:
The website is slow.
A useful finding should be closer to:
The main service page has poor mobile LCP because the hero image is too large and the above-the-fold layout is delayed by scripts.
That is the difference between a speed complaint and a brief someone can act on.
What gets checked
A Core Web Vitals audit may use Search Console data, PageSpeed Insights, Lighthouse, Chrome DevTools and manual template inspection. Google notes that the Core Web Vitals report can show site-wide performance, while PageSpeed Insights can test individual pages. Google SEO starter guide
The review typically checks:
- LCP problems caused by slow hero images, delayed main content, weak server response or render-blocking files
- INP problems caused by heavy JavaScript, slow menus, sluggish forms, filters or overloaded page interactions
- CLS problems caused by shifting images, banners, fonts, embeds, pop-ups or late-loading content blocks
- Mobile performance differences
- Repeated issues across service, category, product or blog templates
- Third-party scripts such as analytics, chat widgets, review tools, booking tools or advertising tags
- Whether the affected pages support enquiries, sales or organic landing-page journeys
Field data and lab data are handled differently. Field data reflects actual users and their devices, while lab tools are useful for controlled testing and debugging. Web.dev recommends using both real-world and lab environments for a well-rounded Web Vitals analysis. Web.dev Web Vitals measurement guide
Common findings
A useful audit does not hand over a generic list of speed tips. It shows what is wrong, where it happens and what the next move should be.
Common findings include oversized hero images on service pages, JavaScript-heavy ecommerce filters, layout shifts caused by late-loading banners, slow product templates caused by app bloat, or WordPress pages slowed down by unnecessary plugins.
On a WooCommerce site, the issue may be a category template that loads too many scripts before users can interact with filters. On Shopify, it may be several apps adding code to every page, even where those apps are not needed. On a local service site, it may be a page-builder template that looks acceptable on desktop but performs poorly on mobile.
These examples matter because “make the website faster” is not a useful instruction. A stronger recommendation names the page type, the metric affected, the likely cause and the person or team best placed to handle it.
Who this page is for
This page is for businesses that can see performance problems but do not yet have a sensible route through them.
It is a good fit for marketing managers who need to brief developers properly, business owners who want to know whether speed work is worth the spend, ecommerce teams dealing with slow category or product pages, and developers who need SEO input before changing templates or scripts.
It is also useful for South African SMEs that inherited a site from a previous agency, have added plugins or apps over time, or are preparing for a redesign, migration or wider technical SEO review.
The audit is especially valuable when different people are giving different advice. A developer may suggest rebuilding the theme. A plugin vendor may blame hosting. A marketing team may want faster landing pages. An SEO-led assessment helps separate symptoms from causes.
Signs you may need this
You may need a Core Web Vitals audit if your site feels slow on mobile, key pages load in stages, buttons or forms respond slowly, page elements move while users are reading, or PageSpeed Insights gives warnings that nobody has interpreted properly.
Other signs include slow ecommerce filters, heavy category pages, organic landing pages that feel weak despite receiving traffic, or a site that became slower after a redesign, plugin change, app install or tracking update.
The goal is not a perfect score. The goal is to understand which issues are affecting real users on real pages.
The problems it solves
Many speed reports create more confusion than clarity.
They list unused JavaScript, image warnings, render-blocking files, caching issues, font problems and server response times. The information may be technically correct, but the team is still left asking what to do next.
A Core Web Vitals audit answers four practical questions:
- Which pages or templates are affected?
- What is causing the poor experience?
- Who is best placed to handle it?
- What should happen now, and what can wait?
That distinction matters. A minor warning on an old blog post should not distract from a slow ecommerce category template used across hundreds of URLs. A layout shift on a pricing page may deserve attention before a small score drop on a low-value archive page.
How this differs from similar reviews
| Review type | What it focuses on | How it differs |
|---|---|---|
| Core Web Vitals audit | LCP, INP, CLS, page experience and SEO-relevant performance issues | Focuses on performance signals affecting real pages, templates and user journeys |
| Page speed audit | Load time, performance scores and speed recommendations | Often score-led; may not connect findings to SEO value or page type |
| Technical SEO audit | Crawlability, indexation, canonicals, redirects, architecture, structured data and technical health | Broader than Core Web Vitals; may not go deep enough into performance causes |
| UX audit | Navigation, layout, user friction, clarity and conversion journeys | Useful for experience issues, but may not diagnose technical performance causes |
| Developer performance review | Code, rendering, infrastructure, scripts and implementation detail | Technically deep, but may not rank changes by search or business relevance |
A Core Web Vitals audit sits between SEO, development and user experience. It gives enough technical detail to brief implementation, but it stays tied to the pages that matter for visibility, enquiries or sales.
Recommended approach
The work starts with page selection. Testing random URLs rarely gives the best insight.
For a service business, the sample may include the homepage, main service pages, pricing pages and lead-generation pages. For an online store, it may include category pages, product pages, filtered views and templates affected by apps or plugins.
The analysis then compares real-user data, lab tests and manual inspection. If several pages use the same template, the template is treated as the area to improve rather than each URL being handled separately.
The process usually covers:
- Selecting the right pages and templates
- Reviewing Core Web Vitals data and tool outputs
- Identifying whether LCP, INP or CLS is the main issue
- Connecting poor scores to likely causes
- Separating page-specific problems from template-wide patterns
- Weighing impact, effort and implementation risk
- Translating findings into instructions for the right team
The output should be short enough to use and specific enough to brief.
How recommendations are ranked
Not every warning deserves developer time.
The audit looks at impact, reach and effort. A high-impact item may affect a lead-generation page, a pricing page or an ecommerce template used by hundreds of products. A lower-impact item may affect an old article, a small visual warning or a page with little business value.
The current platform also matters. A WordPress site with a heavy theme may need a different approach from a custom build. A Shopify store may need app cleanup rather than server-level changes. A WooCommerce site may need plugin review, image handling and template work.
This is where the audit earns its value: it helps the business avoid spending limited development time on low-value warnings while more damaging issues remain untouched.
What you receive after the audit
You should come away with more than a tool score.
Typical outputs include a plain-English summary of the main issues, a list of tested URLs and templates, LCP, INP and CLS observations, an issue log, severity ratings, developer notes, quick wins, larger changes and monitoring guidance after implementation.
The practical value is the shift from “we think the site is slow” to “we know which page type is affected, what is causing it, and what needs to happen next.”
That makes the conversation easier with developers, agencies, platform vendors and internal decision-makers.
How this connects to enquiries or revenue
A slow or unstable page can interrupt a user at the exact point where they are trying to understand your offer, compare a service, complete a form or view a product.
For a service business, that may happen on a core service page or pricing page. For an ecommerce business, it may happen on a category page, product page or filtered listing. For a local business, it may happen on a location page where the user is ready to enquire.
That does not mean Core Web Vitals improvements guarantee rankings, leads or sales. Google says good results in Core Web Vitals reports or third-party tools do not guarantee top rankings, and that page experience involves more than Core Web Vitals scores alone. Google page experience documentation
The commercial value is more grounded: fewer guesses, better briefs, less wasted development time and a site that is easier for users to work with.
When this should become a broader technical SEO review
Sometimes Core Web Vitals are the visible symptom, not the full problem.
If the site also has crawlability, indexation, architecture, internal linking, duplicate content, redirect or template issues, performance work should sit inside a broader technical seo south africa review.
For online stores, Core Web Vitals should also be assessed alongside category targeting, product templates, faceted navigation, internal linking and crawl control. In that case, review ecommerce technical seo.
This keeps performance work connected to the wider SEO roadmap, rather than treating it as a disconnected development task.
Next step
Book an SEO diagnostic review if you have speed warnings, poor Core Web Vitals results, or a site that feels slow but no confident route forward.
This is especially useful when developers need better instructions, marketing needs to defend the work internally, or the business needs to decide whether speed improvements should happen before a redesign, migration or wider SEO campaign.
SEO Strategist will help you identify which pages are affected, what is likely causing the problem, and which actions deserve attention first.
You will leave with a sharper view of the issue and a practical route your team can use.
Book an SEO diagnostic review.
Common questions before booking
Does fixing Core Web Vitals guarantee better rankings?
No. Core Web Vitals improvements can support a better user experience, but they do not guarantee rankings, traffic, leads or revenue. Google states that good Core Web Vitals reports or third-party tool scores do not guarantee top rankings. Google page experience documentation
Is this the same as a page speed audit?
No. A page speed audit often focuses on loading speed and tool scores. A Core Web Vitals audit focuses on LCP, INP and CLS, then connects those issues to real pages, templates and user journeys.
Is this the same as a technical SEO audit?
No. A technical SEO audit is broader. It may cover crawlability, indexation, redirects, canonicals, structured data, internal linking and site architecture. A Core Web Vitals audit goes deeper into page experience and performance causes.
Should every page be checked?
Usually not at first. It is better to review the pages and templates that matter most. If one template is used across many URLs, fixing the template can be more useful than testing every page individually.
What tools are used?
The audit may use Search Console, PageSpeed Insights, Lighthouse, Chrome DevTools and manual template review. The tool output is only the starting point. The useful part is the interpretation and implementation route.
Is this useful for ecommerce websites?
Yes. Ecommerce sites often have repeated issues across category, product and filter templates. A Core Web Vitals audit can show whether apps, plugins, scripts, images or template decisions are slowing down shopping journeys.
Who should implement the changes?
Most changes are handled by developers or platform specialists. The audit defines the work before implementation, so the team does not waste time dealing with low-value warnings while more serious issues remain.