How to Explain a Slow Website to a Non-Technical Client

The hardest part of a performance problem often isn't fixing it - it's explaining it. A client hears "your LCP is 4.2 seconds" and hears nothing useful. An account manager who can't translate a Lighthouse report into a business consequence loses the argument for budget, even when the technical case is airtight. Here's how to actually have that conversation.

Start with money, not milliseconds

Nobody outside of development cares about a PageSpeed score as a number. They care what it costs them. The translation that actually lands: "For every extra second your page takes to load, a meaningful share of your visitors leave before they see anything - including the ones you paid to bring there through ads." A slow page isn't a technical flaw, it's a leak in a budget the client already approved for marketing.

Use one before/after number, not a jargon list

Resist the urge to list LCP, CLS, INP, and TTFB in the same breath as the sales pitch - that's for the technical debrief afterward, not the moment you're trying to get buy-in. One concrete before/after example does more work than five metrics: "A similar site we fixed went from a PageSpeed score of 38 to 94, and leads tripled within weeks - same traffic, same ads, just a site that didn't lose people before they saw the offer."

Reframe "it's slow" as "it's not converting the traffic you're already paying for"

This single reframe changes the entire budget conversation. Clients rarely fight for "better performance" as a line item - it sounds like polish, not necessity. They do fight for "stop wasting ad spend," because that's a number already on their P&L. The technical fix is identical either way; only the framing determines whether it gets approved this quarter or gets pushed indefinitely.

Show, don't just tell - live tools help

Running Google PageSpeed Insights live on the client's own site, in front of them, is more persuasive than any slide. Seeing their own site score a 41 in real time, with a red bar under "Diagnose performance issues," creates urgency that a written report doesn't. If you don't want to run this manually every time, our own free audit tool is built for exactly this - no email required, results in seconds, easy to screen-share on a client call.

Anticipate the pushback: "But the site looks fine to me"

This is the most common objection, and it's usually true - from the agency's own office, on fast wifi, with a warm browser cache. The fix: ask the client to test on their phone, on cellular data, somewhere with average signal. The gap between "looks fine on my desk" and "how it loads for an actual visitor on the go" is often the whole argument.

A script that works for the budget conversation

"Your site currently scores in the 30s-40s on Google's own speed test. Sites in that range typically lose a meaningful share of visitors before the page even finishes loading - meaning some portion of what you're spending on traffic right now never gets a real chance to convert. Fixing the core issues is usually a fixed, scoped project, not an open-ended one - and it's the kind of fix that keeps paying off every month afterward, unlike a one-time campaign."

Where I fit into this conversation as your white-label partner

If you're an agency account manager who needs the technical backup for this conversation - an actual audit, a fixed quote, and someone who can join the call to answer the harder technical questions without you having to bluff - that's exactly the kind of white-label support I provide behind the scenes.

Related reading

• The real cost of a slow WordPress site: a lead-loss breakdown
• Case study: 8s to under 2s, and a 40% increase in leads

Need the technical backup for an upcoming client conversation? Get in touch or run a free audit on the site in question.