Your Website Is Not on Your Balance Sheet. It Is Still Under-Measured.

Most companies measure paid acquisition to the dollar and measure their website by whether it looks current.

That gap is real and worth closing. What follows is our attempt to make the case for it without overstating it.

An honest correction first

An earlier version of this post argued that a well-built website belongs on the asset side of your ledger. We are walking that back, because it is not an accounting fact. Whether website spend is expensed or capitalized as an intangible depends on your jurisdiction, your accounting policy, and what the spend actually bought. Design and content work is typically expensed. Some development cost can be capitalized. A blog post is not the place to settle that, and we are not your accountants.

The defensible version of the claim is narrower and more useful: leadership under-measures this channel relative to how it measures other acquisition spend. A paid campaign gets a cost per click, a cost per lead, and a weekly readout. The website gets a redesign every few years and a subjective opinion about the hero image.

What we can actually show

We scanned 292 business websites drawn from a B2B prospect list. 191 of them returned a valid mobile result. 185 of those 191 failed at least one Lighthouse lab threshold, 165 had a lab Largest Contentful Paint over four seconds, and the median mobile Largest Contentful Paint across the cohort was 10.5 seconds.

Two things about those numbers. They are lab measurements, so they are not the same thing as Google's Core Web Vitals, which are collected from real users in the field. And the sample was purposive rather than random, so it describes that cohort of B2B prospects. It does not give you a probability about your own site. What it does establish is that slow mobile rendering is common enough in this population to be worth checking rather than assuming.

In a separate study we crawled 405 sites and analyzed 368. On 92 of those 368, an answer-critical element that was present in the rendered page was missing from the raw HTML: body text on 57 sites, links on 51, and business name, address, or phone on 54. Any system that reads the raw response instead of running the page sees a thinner version of those businesses than a visitor does.

What we did not measure

We did not measure revenue. We do not know what any of those conditions cost those companies, because we did not have their analytics, their Search Console data, or a before and after. Nobody who has only scanned a site from the outside can tell you what it is costing you. If a tool hands you a dollar figure from a scan alone, it is guessing.

The board-level question that survives

For the demand we want, are we being considered, and can we connect that visibility to qualified revenue?

That question is answerable, but not by one team. It needs impressions and queries from Search Console, field performance data from real users, analytics on what happens after the click, and a CRM that records whether those sessions turned into pipeline. Marketing is usually asked the question and controls almost none of the inputs. Engineering owns rendering and performance. Operations owns the accuracy of the business information. Subject-matter experts own whether the claims on the page are true. Sales and the CRM own whether attention becomes revenue.

If nobody in the room can assemble those four inputs, the problem is not which line of the budget the website sits on. The problem is that four teams each hold one quarter of the answer and no one has been asked to put it together.

Where we stand

We build sites, and we measure them with the same tool we give away. Our free audit loads the page in Chromium and inspects the rendered DOM rather than parsing the raw HTML response, and it runs 60 or more checks across nine categories. It reports conditions. It does not report dollars, because it cannot see them.

Run a free audit if you want a baseline. Then go get the field data, because that is the half an audit cannot see.