Transcript — Episode 0002: The 40-Page PDF Nobody Reads

Full accessible transcript of the episode. Speaker labels match the audio. No stage directions, no IPA tags — this is the version for screen-reader and reader audiences.

---

Christopher: A WordPress audit done well takes about a day.

Done badly, it produces a forty-page PDF that nobody reads.

I've watched both.

The forty-page version comes in a binder. The client signs off on it because the binder feels like the money was well spent. It sits on a shelf for a month and then gets recycled. Nothing about the site changes. The one-day version produces three findings, maybe five. Each one names a thing the site is doing badly and what it would take to fix. The client reads it on a Friday afternoon and starts fixing on Monday.

One of those audits is a service. The other is a document.

Christopher: I want to talk about what a real WordPress audit is. What it actually is, not what it looks like. The standard goes: hire someone, they spend two weeks, you get a thorough deliverable. The thicker the binder, the more thorough the work, the better the value. I don't agree with any part of that.

Frances: Christopher, hold on. Before you talk yourself out of selling audits to anyone.

Christopher: Go ahead.

Frances: Clients pay agencies for PDFs because the PDF is the deliverable they show their boss. A binder justifies the spend. A one-page list, even if it's the right one-page list, doesn't justify itself to the procurement committee. You're telling them to accept something they can't defend internally.

Christopher: That's a real thing. I'm telling them to accept a service instead of a document.

Frances: Same money?

Christopher: Same money. Sometimes more.

Frances: Why more?

Christopher: Because the service is harder than the document. The document is, sit down, run the checks, write what you found, hand it over. The service is, sit down, run the checks, decide which three of them actually matter, and tell the client what they shouldn't do.

Frances: Tell them what they shouldn't do.

Christopher: Yeah. That's where most audits hide. They tell you everything. They don't tell you what to ignore.

Kenji: Can I push on something?

Christopher: Please.

Kenji: You're saying the value is in what you remove from the deliverable, not in what you add to it.

Christopher: Yeah.

Kenji: That's an uncomfortable thing to charge for.

Christopher: It is. But it's the part that makes the audit work.

Frances: How does this play out in the actual room? When you tell a client they're getting five findings, not forty.

Christopher: I tell them up front. Before they sign anything. I say, you're going to get three to five things, and they're going to be the things that move your business. The other thirty-five things you might see in a typical audit, those are real, but they're not where the leverage is. If you want the document version, I'll tell you who does that. I do this.

Frances: And they sign?

Christopher: Most of them. The ones who don't, they wanted the binder. Which is fine. They knew what they wanted.

Iris: Can I bring something to this?

Christopher: Of course.

Iris: I track audit deliverables across the WordPress ecosystem. I have for about a decade. There's a pattern that doesn't get talked about.

Christopher: Go on.

Iris: The long audits live on shelves. The short ones produce work. I can predict, with maybe eighty percent accuracy, whether an audit will result in actual changes to the site, by looking at the page count alone. Forty pages and up, almost never. Under five pages, usually.

Frances: Eighty percent on page count alone?

Iris: Page count alone. The deliverable shape predicts the outcome.

Christopher: I hadn't framed it that way.

Iris: The long audit is structured to feel complete. The short audit is structured to produce action. Those are different goals. The buyer often doesn't realise they're choosing between them when they pick the agency.

Frances: OK, so a long audit is a memorial. A short audit is a prescription.

Kenji: There's also something about what the audit is doing for the auditor. The long version performs thoroughness, protects the auditor from the accusation of having missed something. The short version requires the auditor to take a position.

Christopher: The long audit hedges. The short audit decides.

Frances: And that's why most agencies ship the long one. The hedge is cheaper than the decision.

Christopher: It is. Right up to the moment the client realises nothing changed about their site.

Kenji: Can I ask what one of yours actually looks like?

Christopher: Sure. I'll give you the most recent. Services site, eight thousand organic visitors a month, contact form completion stuck around one point two percent. The audit ran one day. Four findings. One. Mobile L-C-P at four point one seconds. The hero image was loading lazily. Fixed, removed the lazy attribute, added a preload. Dropped to one point eight seconds within a week. Two. Plugins running on every page that were only needed on the contact and booking routes. Scoped them. Page weight dropped a hundred and eighty kilobytes. Three. Service pages had no above-the-fold call to action. Six of the eight required a scroll before the first book-a-call button. Added the CTA into the hero block at the template level. Four. Object cache was connected but empty. Misconfigured. Twenty-minute fix. T-T-F-B dropped two hundred and eighty milliseconds.

Frances: What did that do to the business?

Christopher: Form completion went from one point two percent to two point six percent inside thirty days. On eight thousand visitors a month, that's a hundred and twelve additional inquiries a year. From four findings.

Frances: From four findings.

Christopher: From four findings.

Iris: And those four are the ones a long audit might have buried on page nineteen.

Christopher: Page nineteen. Or page thirty-one. Or never surfaced at all, because the auditor was busy listing forty things and didn't have time to sort them.

Iris: Christopher, can I name what I think is the real thing here?

Christopher: Please.

Iris: It's not about page count. The page count is a symptom. The real question is, what's the audit for? Most audits are sold as 'tell me what's wrong with my site.' But the buyer doesn't need a list of what's wrong. They need a list of what to fix this quarter.

Christopher: Yeah.

Iris: Those are different lists. The first one is comprehensive, and it's what makes the binder feel thorough. The second one is prioritised, and it's what makes the business change. Most audits answer the wrong question on purpose, because the wrong question is easier.

Frances: Huh.

Kenji: The audit's value isn't the findings. It's the prioritisation. And prioritisation is the part most audits skip.

Christopher: Skip on purpose. Because to prioritise you have to take a position on what matters more than what. And taking a position is what gets the auditor accused of missing something.

Frances: OK. I think you're right about this.

Christopher: There's a kind of audit that's a document. There's a kind that's a service. The document audit gets paid the same as the service one. It takes ten times the hours. And it changes nothing about the client's business. The service audit takes a day, produces a short list, and changes the business by the next quarter. I do the service one. I tell clients up front. Some of them go elsewhere for the document. That's fine. They got what they wanted.

Frances: What about the ones who want both?

Christopher: There's no both. The point of the service audit is that the prioritisation is the work. If I also produce the long deliverable, I've done the work and then done it again. The second pass adds pages, not value.

Kenji: And the client who insists on both?

Christopher: Is paying for the document, with the service on the side. That's a different engagement. I can do that. I price it accordingly. And I make sure the client knows what they're paying for.

Iris: It's the same shape as the contract one, actually. The deliverable shape isn't the work. The work is what changes the site.

Christopher: Yeah.

Christopher: Three findings.

The right ones.

Worth a day to find.

Thanks for spending the time with us.

If you're sitting across the table from a vendor who's quoted you a forty-page audit, the question worth asking is what they'd actually deliver — not what they'd put in the binder. The good vendors welcome that question.

This is Sites I've Never Seen. Next time, we get into hosting vocabulary — what enterprise WordPress actually means once you cut through the tier sheets.

Glad you were here.