Most business owners assume their website is fine. It loads, it looks decent, the contact form works. Job done.

But Google does not care whether your site looks decent. It cares about how fast it loads, how stable it is while loading, how quickly it responds to user input, and whether it is structured in a way that search engines can actually parse. If any of those things are broken — and for most small business websites, at least two of them are — your site is not just failing to help your ranking. It is actively suppressing it.

This post walks you through a free, structured audit you can run today. No paid tools required. No agency retainer. Just a clear process that tells you whether your site is working for you or against you — and what to do about it.

Why Google Ranking Is Not Just About Keywords Anymore

There was a time when SEO was mostly about content and backlinks. Stuff the right words in the right places, get a few other sites to link to you, and you would climb the rankings. That still matters — but it is no longer sufficient on its own.

Since 2021, Google has incorporated Core Web Vitals into its ranking algorithm as part of the Page Experience update. These are measurable, technical signals about how a page actually performs for real users. They sit alongside mobile-friendliness, HTTPS status, and the absence of intrusive interstitials as explicit ranking factors.

What that means in practice: two websites with identical content and identical backlink profiles can rank very differently if one loads in 1.2 seconds and the other takes 4.8 seconds. The slower one loses — not just in user experience, but in the algorithm itself.

The Three Core Web Vitals You Need to Know

Largest Contentful Paint (LCP) measures loading performance — specifically, how long it takes for the largest visible element on the page (usually a hero image or headline) to render. Google wants this under 2.5 seconds. Above 4 seconds is classified as poor.

Interaction to Next Paint (INP) replaced First Input Delay in 2024. It measures responsiveness — how long the browser takes to respond after a user interacts with the page. Under 200 milliseconds is good. Above 500 milliseconds is poor.

Cumulative Layout Shift (CLS) measures visual stability — how much the page jumps around as it loads. Anyone who has ever tried to tap a button on a mobile site only for it to shift at the last second and they accidentally tap an ad instead knows exactly what this measures. Google wants a CLS score below 0.1.

These are not abstract metrics. They describe real experiences that real users have on your site every day. If you are failing them, you are frustrating users and being penalised by Google simultaneously.

The Free Audit: What to Run and Where

You do not need to pay for Screaming Frog, Ahrefs, or any other SEO platform to run a meaningful first-pass audit. The tools below are free, authoritative (most of them are made by Google), and will surface the issues that matter most.

Step 1 — Google PageSpeed Insights

Go to pagespeed.web.dev and enter your homepage URL. Run it for both mobile and desktop. This is the single most important free tool in this audit because it uses real-world data from the Chrome User Experience Report (CrUX) alongside lab data from Lighthouse.

Pay attention to the distinction between Field Data and Lab Data. Field data is what real users have actually experienced on your site over the past 28 days. Lab data is what a simulated test produces. If your field data is poor, that is a ranking signal Google is already using against you. If only your lab data is poor, you have a warning — not yet a penalty, but one is coming.

Write down your scores. Specifically: your LCP, INP, and CLS values, and whether each is green (good), amber (needs improvement), or red (poor).

Step 2 — Google Search Console

If you have not connected your site to Google Search Console, do that first. It takes about ten minutes and requires you to verify ownership of your domain. Once verified, navigate to Experience > Core Web Vitals.

This report groups your URLs into good, needs improvement, and poor categories based on real field data. It also tells you which specific pages are underperforming, which is far more useful than a homepage-only score. A services page that loads slowly costs you just as much ranking potential as a slow homepage — sometimes more, because it is often the page users land on from a specific search query.

Step 3 — Google Rich Results Test

Go to search.google.com/test/rich-results and run your homepage and a key landing page through it. This tells you whether your structured data (schema markup) is valid and whether you are eligible for rich results — those enhanced listings in search that show star ratings, FAQs, breadcrumbs, and more.

Rich results do not directly improve your base ranking, but they dramatically improve click-through rates from the same position. A result with stars and a price range gets more clicks than a plain blue link sitting above it. That increased click-through rate is itself a positive engagement signal.

Step 4 — Mobile-Friendliness Check

Use search.google.com/test/mobile-friendly. This is blunt: your site either passes or it does not. If it does not pass, you have a serious problem. Google uses mobile-first indexing, which means it primarily uses the mobile version of your site to determine ranking — for all users, including desktop ones.

If your site fails this test, everything else in this audit is secondary. Fix mobile-friendliness first.

Step 5 — HTTPS and Security Headers

Check that your site loads over HTTPS (the padlock icon in the browser). Then go to securityheaders.com and enter your domain. This is not a direct ranking factor in the way Core Web Vitals are, but a site served over HTTP is flagged as insecure by Chrome — and that warning actively damages user trust and conversion rates, both of which have downstream effects on ranking signals.

The Audit Scoring Framework

Once you have run all five steps, use this framework to assess your site. Score each category as 0 (poor / failing), 1 (needs improvement), or 2 (good / passing). Maximum score is 10.

Category Tool Used Score (0-2)
Largest Contentful Paint (LCP) PageSpeed Insights
Interaction to Next Paint (INP) PageSpeed Insights
Cumulative Layout Shift (CLS) PageSpeed Insights
Core Web Vitals field data (Search Console) Search Console
Structured data / Rich Results Rich Results Test

Score 9–10: Your technical foundation is strong. Focus on content and backlinks.
Score 6–8: Meaningful issues exist. Fix them before investing more in content or paid search.
Score 4–5: Your site is likely suppressing your ranking. Prioritise technical fixes now.
Score 0–3: Your site is actively working against you. Stop spending on SEO content until the foundation is repaired.

What Actually Causes Poor Scores — and What Fixes Them

Running the audit is step one. Understanding why your scores are what they are is step two. Here is what typically causes each failure and what genuinely fixes it.

Slow LCP: Usually an Image Problem

The most common cause of a poor LCP score is an unoptimised hero image — a large JPEG or PNG that has not been compressed, resized for the viewport, or converted to a modern format like WebP or AVIF. A 3MB hero image that looks identical to a 180KB WebP version at the same visual quality will cost you several seconds of LCP time.

Fixes to implement in order of impact:

Slow server response time (Time to First Byte / TTFB) is the second most common cause of poor LCP. If your server takes more than 800ms to respond, you are starting from a deficit before a single byte of content has loaded. This is often a hosting problem — cheap shared hosting with overloaded servers is a very common culprit for UK small business websites.

Poor INP: Usually JavaScript

INP failures are almost always caused by JavaScript blocking the main thread. When a user clicks or taps something and the browser is busy executing a long JavaScript task, it cannot respond to the interaction. The user sees nothing happen. They tap again. Still nothing. Then three things happen at once.

Common causes include bloated third-party scripts (chat widgets, marketing pixels, analytics libraries loaded synchronously), poorly written custom JavaScript, and WordPress plugins that load scripts on every page regardless of whether they are needed there.

Fixes include deferring or async-loading third-party scripts, removing unused plugins, and auditing your JavaScript bundle size. The Lighthouse report in PageSpeed Insights will show you a breakdown of long tasks and which scripts are responsible.

High CLS: Usually Missing Dimensions or Late-Loading Elements

Layout shift happens when elements load or render after the initial paint and push other content around. The most common causes are images without explicit dimensions, web fonts that swap in after a system font has already rendered (font flash), and ad or cookie banner slots that inject into the layout without reserved space.

Fixes: Set explicit width and height on every image. Use font-display: optional or font-display: swap carefully and preload your web fonts. Reserve space for any dynamically injected elements using CSS.

The Contractor and Freelancer Website Problem

There is a specific pattern worth calling out because it is so prevalent in the UK: the contractor or independent professional website that was built in a hurry, hosted on cheap shared hosting, uses a generic WordPress theme with twenty plugins, and has never been audited since launch.

These sites disproportionately fail Core Web Vitals. They typically have LCP scores above 4 seconds because the theme loads full-resolution slider images. They have INP failures because three different contact form plugins are all loading JavaScript on every page. They have CLS failures because the theme injects a cookie banner without reserved space.

The owner of that site is often spending money on Google Ads or paying for SEO content — neither of which will perform as well as it should because the technical foundation is broken. A contractor website with a poor Google ranking is not just a visibility problem. It is a revenue problem. Every month that site underperforms is a month of work that went to a competitor with a faster, better-structured site.

We wrote about this dynamic in more detail in our post on websites as your cheapest salesperson — the argument there is simple: if your site is not converting visitors into enquiries, the problem is almost always structural, not superficial.

Beyond Core Web Vitals: The Technical SEO Checks Most People Skip

Core Web Vitals get most of the attention because Google has made them explicit ranking factors, but there is a layer of technical SEO beneath them that also matters. These checks take fifteen minutes and can surface problems that have been silently suppressing your ranking for months.

Crawlability and Indexation

In Google Search Console, go to Index > Pages. This report shows you how many of your pages are indexed versus excluded. Click into the excluded categories. Common problems include pages blocked by robots.txt accidentally, pages marked noindex that should be indexed, and duplicate content issues caused by URL parameters generating multiple versions of the same page.

If your site has fewer indexed pages than you expect, this is your first place to look.

Internal Linking Structure

Google uses internal links to understand which pages on your site are important. If your most valuable service pages are only linked from one place — say, a dropdown menu — they receive very little internal link authority. Adding contextual internal links from blog posts and other high-traffic pages to your key service pages is one of the highest-return, lowest-cost SEO improvements you can make.

Duplicate Title Tags and Missing Meta Descriptions

In Search Console, go to Search Appearance and look at your page titles and descriptions. Duplicate title tags tell Google that two pages have identical content — it will pick one to rank and may suppress the other. Missing meta descriptions are not a ranking factor directly, but they reduce click-through rates from search results, because Google often displays them verbatim in the snippet.

Broken Links and Redirect Chains

A free tool like ahrefs.com/broken-link-checker (their limited free version) or the browser extension Check My Links will surface 404 errors on your site. Broken internal links waste crawl budget and create dead ends for users. Redirect chains — where page A redirects to page B which redirects to page C — dilute link authority and slow page load times.

If you have recently migrated your site or redesigned it, redirect chains are extremely common. Our post on what actually happens during a website migration covers why getting redirects right at the point of migration matters so much — fixing them retroactively is always more painful than doing it correctly the first time.

A Worked Example: Before and After Audit

To make this concrete, here is a representative example based on the pattern we see regularly with small business websites in the UK.

The site: A four-page WordPress website for a structural engineering consultancy. Built in 2019. Hosted on shared hosting. Uses a premium theme. Has eight active plugins including two page builders that are both loaded on every page.

Pre-audit scores (PageSpeed Insights, mobile):

Issues identified:

Changes made:

Post-fix scores (PageSpeed Insights, mobile):

None of the fixes above required a new website. They required a methodical audit, correct prioritisation, and competent execution. The site went from actively suppressing its own ranking to being technically competitive — in a single sprint of focused work.

This is exactly the kind of structured diagnosis that Daybrain Digital runs as a starting point before any build or migration engagement — because fixing the foundation is always the prerequisite for everything else.

When to Stop DIY-ing and Get Professional Help

The audit described in this post is something any technically literate person can run. Interpreting the results and fixing the underlying issues is where the skill gap starts to open up.

If your INP failures are caused by a third-party script you cannot remove because it powers a critical business function, you need to know how to load it without blocking the main thread. If your CLS is caused by a web font issue, you need to understand the CSS font loading API. If your TTFB is caused by a server-side rendering bottleneck, you need to understand your stack.

There is also the compounding issue of hosting. Many UK small businesses are on hosting plans that were chosen based on price, not performance. Moving to a properly configured VPS or a platform with edge caching built in — like a modern managed WordPress host or a custom-deployed application — can improve Core Web Vitals scores dramatically without changing a single line of application code.

If you have run this audit and your scores are red across the board, and if the technical fixes feel out of reach, the right move is not to keep spending on Google Ads hoping the algorithm will relent. The right move is to fix the site. The audit tells you what is broken. A good technical partner tells you how to fix it in the right order without breaking anything else.

It is also worth noting that if you are considering a redesign or migration because of these issues, the audit data you gather now is invaluable input for that process. Knowing which pages are indexed, which are driving traffic, and which have structural problems means any migration can be planned around preserving what works and repairing what does not — rather than starting blind. We covered why that baseline matters in our post on capturing your old site before migration.

The UK Context: Why This Matters More for Smaller Businesses

Large enterprises typically have dedicated technical SEO teams, performance budgets, and monitoring infrastructure. Their sites are not perfect, but the obvious failures get caught quickly.

Small and medium businesses in the UK — particularly professional services firms, tradespeople, consultancies, and specialist retailers — often have none of that. They have a website that was built once, may have been handed off by a freelancer who no longer works with them, and has not been meaningfully maintained since. These are the sites that consistently fail Core Web Vitals, not because the owners do not care, but because no one has told them it is costing them ranking.

Google does not send an email to say your site is now being penalised. The rankings just quietly slip. The enquiries slow down. The owner assumes the market has changed or that SEO just does not work. In many cases, it is the site itself that is the problem.

Running a free PageSpeed audit and a Search Console review takes less than an hour. If the results are bad, that hour just saved you from months of wasted ad spend and lost organic traffic.

Checklist: The Complete Free Audit in Order

Here is the full process consolidated into a single checklist you can work through sequentially.

Phase 1 — Performance (20 minutes)

Phase 2 — Search Console Review (15 minutes)

Phase 3 — Technical Checks (20 minutes)

Phase 4 — Score and Prioritise

The Straight Takeaway

Your website is either helping your Google ranking or hurting it. There is no neutral. And because Core Web Vitals are now a confirmed ranking factor, a site that fails those measurements is being actively suppressed in search results — regardless of how good your content is or how many backlinks you have built.

The audit described in this post costs nothing except time. It uses tools built and maintained by Google. It will tell you within an hour whether your technical foundation is solid or broken, and it will give you enough specificity to know where to focus your effort first.

If the results are good, you can invest in content and promotion with confidence. If the results are bad, you now know exactly why your ranking is where it is — and you have a prioritised list of what to fix.

That is a more useful starting point than any keyword research tool, content calendar, or link-building campaign. Fix the foundation. Then build on it.

If you want someone to run this audit for your site and translate the results into a concrete fix plan, Daybrain Digital does exactly that — without the agency jargon or the twelve-month retainer requirement.