What a Website Audit Can Tell You, and What It Cannot

An audit finds conditions. It does not find costs.

That distinction is the point of this post, and it is the one most audit tools blur. A scan can tell you that your mobile Largest Contentful Paint is nine seconds, that your services page carries no structured data, and that your phone number is absent from the raw HTML. It cannot tell you that any of that cost you a customer, because it never saw a customer.

What an audit actually inspects

Our free audit loads your page in Chromium and inspects the rendered DOM. It does not parse the raw HTML response, and it is not Googlebot. Google crawls, queues, renders, and indexes on its own schedule, and no third-party tool reproduces that pipeline. What we can honestly say is that we look at the page after JavaScript has run, which is closer to what a person sees than a raw fetch is.

It runs 60 or more checks across nine categories: technical, content, on-page, social, security, performance, accessibility, AI readiness, and locality. A deep scan crawls up to 50 pages. It waits for network activity to settle, with a 20-second ceiling. It does not scroll and it does not click, which is deliberate, because Google Search does not interact with your page either.

Why raw-HTML tools miss things

Most free scanners request your URL, take the HTML response, and parse it. On a server-rendered site that is fine. On a site built with React, Vue, Svelte, or a modern site builder, the response can be close to empty and the real content arrives only after JavaScript runs.

This is measurable. We crawled 405 sites and analyzed 368. On 92 of them, something answer-critical was present in the rendered page and absent from the raw HTML: body text on 57 sites, links on 51, and business name, address, or phone on 54. A tool reading only the raw response would have reported thin or missing content on those 92 sites.

That is one in four of the sites we analyzed. It is not a majority, and we are not going to describe it as one.

The conditions we see most often

We will only give you numbers we actually have.

In our 292-site study, 191 sites returned a valid mobile result. Of those, 185 failed at least one Lighthouse lab threshold, 165 had a lab Largest Contentful Paint over four seconds, and the median was 10.5 seconds. The Lighthouse link-name rule, which flags links a screen reader cannot announce, failed on all 191.

Those are lab measurements from a purposive sample of B2B prospects. They are not field data, they do not tell you your odds, and Core Web Vitals is a different measurement taken from real users. We publish the denominators so you can judge the claim for yourself.

Why we will not tell you what it is costing you

Most tools in this category want to hand you a dollar figure. We will not, because proving cost requires four things a scan does not have.

Search Console. Impressions, queries, and average position tell you whether you are being seen at all, and for which searches.

Field performance data. Real users, on real devices, over real networks, rather than one lab run from a data center.

Analytics. What visitors did after they arrived, where they left, and which pages preceded a conversion.

A before and after. Fix the condition, wait, and compare. Without that, a real improvement and a seasonal swing look identical.

An audit is the cheapest of those four and the only one you can run on a site you do not own. It tells you where to point the other three. It does not replace them.

What to do with the report

Read it as a list of conditions, ranked by how much work it would take to address each one, and not as a list of leaks. Some items are genuinely small: a missing title tag, a page with no description, images without alt text. Others look small in a report and are not. Changing how a site renders, restructuring templates, or replacing a page builder is real engineering work, and we are not going to call it an afternoon fix.

Then route the conditions to the people who own them. Rendering and performance belong to engineering. Business name, hours, and service accuracy belong to operations. Whether the claims on the page are true belongs to whoever does the work. Whether a visit becomes pipeline belongs to sales and the CRM.

Above all of them sits one question: for the demand we want, are we being considered, and can we connect that visibility to qualified revenue?

Run a free audit to get the baseline. Then go get the data the audit cannot see. If you want help reading the results, book a call and we will walk through them with you.