- Oct 21, 2026
- 3 min read
Cold Email Personalised With a Website Audit, Not an AI Opener
The standard cold-email recipe in 2026: scrape a list, have an LLM read each company’s website, generate a “personalised” opening line. Recipients have learned to spot it: “I loved your recent post about…”.
I had something better to hand: a website audit tool. Instead of a clever line, each email states one problem I measured on their own website, something they can check in a minute.
One finding per site, chosen by impact
The audit returns dozens of numbers. The email needs exactly one, the most concrete and costly one, in plain words. The order:
- A security problem visitors can see (expired certificate, no HTTPS)
- Slow on a phone: main content takes more than 4 seconds
- Broken links: the kind that make a business look closed
- A heavy homepage: several megabytes on mobile
- No way to get in touch from the homepage
- Missing Google basics: no title or description
- No share preview: the link looks broken on WhatsApp or Facebook
if (m.lcp_ms > 4000) return {
short: `${Math.floor(m.lcp_ms / 1000)}s+ load time`,
text: `your homepage takes over ${Math.floor(m.lcp_ms / 1000)} seconds to show its main content on a phone (Google's target is under 2.5); you can check it yourself at pagespeed.web.dev`,
};
The short version becomes the subject line, the text version the
sentence. Both are rounded down, and the speed number is measured twice
(why, in a later post).
No finding, no email
If a site is fast, secure and has its basics in place, the batch skips it. A pitch with no real problem behind it is exactly the kind of email that gets marked as spam. In my first run every audited site happened to have a real problem, mostly 11–17 second load times on mobile, but the rule matters more than the result.
The template
Plain text, short, one question:
Subject: {{company}}: {{finding_short}}
Hi {{first_name | default: "there"}},
I ran a quick check of {{company}}'s website and noticed that {{finding}}.
I put the details in a one-page report (speed, search basics, security).
Want me to send it over? No charge.
{{sender_name}}
{{brand}}
If you'd rather not hear from me, reply "no" and I won't write again.
Choices behind it:
- No links and no attachments in the first email. Plain text lands in the inbox; the report (a PDF from the same audit) goes out only after a reply.
- No open or click tracking. It helps deliverability, and it’s how I’d want to be treated.
- The trading name (“Example Vets”), not the registered one in capitals (why).
- An easy way out in every email, honoured globally and permanently.
- One follow-up at most, four or five days later, two lines. Then stop.
The report behind the reply
When someone says yes, they get a one-page PDF from the audit engine, branded for the sender: score, the numbers that matter, why they matter, three priorities, and a fixed-price offer to fix them. It’s the same renderer as my public audit tool, with the brand passed in as a small JSON file.
Takeaways
- Personalise with something they can verify, not something a model wrote.
- One finding, rounded down, from a source they can check.
- Skip sites that are fine.
- Plain text, no tracking, the report after the reply.