The 15-Minute Website Audit I Run Before Every Sales Call. Steal It.

Somewhere in your inbox there is a 40-page audit PDF an agency sent you. Colour-coded charts, severity ratings, a glossary. You read 3 pages and closed it forever.

I audit every prospect's site before every discovery call at Webight, and the whole thing takes 15 minutes with free tools. Five checks, 3 minutes each, one line of notes per finding. Those 5 lines have done more for me on calls than any deck I ever built.

Quick context so you know this is tested. I have never sent a cold email for Webight. Every client came inbound. So when someone books a call, they already want to talk. The audit has a different job: it lets me describe their site back to them with exact numbers before they finish telling me what they think is wrong. Specifics are proof of presence. The moment a prospect hears "your hero headline takes 4.1 seconds to paint on a phone," they stop treating me like a vendor and start treating me like the person who already looked.

Set a timer. Here is the sequence.

Minutes 0 to 3: PageSpeed Insights

Go to pagespeed.web.dev, paste the domain, look at the mobile tab first. Ignore the big score for a second. Two things matter more.

First, the field data at the top. That comes from real Chrome users over the last 28 days. The lab score below it is a simulation. If field data says LCP is 5.8s, that is what actual visitors lived through, and no amount of "but it loads fast on my laptop" changes it.

Second, expand the LCP breakdown. It splits load time into TTFB, load delay, load time, and render delay. The split tells you where the problem lives. High TTFB points at hosting or server work. High render delay points at JavaScript holding the page hostage.

I learned to read that breakdown on my own site. In June 2026 I audited webight.com and found the hero headline had a 4,190ms element render delay. The culprit was a framer-motion opacity animation that waited for React hydration before showing anything. I replaced it with a pure CSS animation that only moves the element, no opacity tricks, no JavaScript, and the render delay dropped to 382ms. Same page, same content, same server. One animation choice was eating 4 seconds.

The note I write: "Mobile LCP 5.8s in field data, render delay dominates, JS animation suspect. One-afternoon fix."

One line. If I cannot compress a finding into one line, I do not understand it yet, and I keep digging until I do.

Minutes 3 to 6: site:domain.com on Google

Open Google and search site:theirdomain.com. Nothing fancier than that. Now read the results like a stranger would.

This check reveals what Google actually has, which is often very different from what the owner believes is live. You are scanning for four things: how many pages are indexed, whether dead pages still show, whether titles read like titles or like file names, and whether www and non-www versions are fighting each other.

My own site failed this check. That same June audit found 12 deleted case-study URLs still sitting in the sitemap, so Google kept getting pointed at pages that no longer existed. Worse, every canonical tag pointed to webight.com while the server 307-redirected everything to www.webight.com. The page told Google one address, the server insisted on another. Two contradicting instructions on every single URL, shipped by me, the person who does this for a living. After fixing that plus the LCP work, the mobile scores went from 90/96/96/100 to 96/100/100/100. Run this on your own stuff first. It is humbling.

The note I write: "site: shows 23 pages, 7 dead or duplicate, two titles read 'Untitled'. Sitemap rebuild needed."

Minutes 6 to 9: view source

Right-click, View Page Source, or press Ctrl+U. You are looking at what crawlers see before any JavaScript runs. Faster option: open DevTools, go to Console, paste this:

console.log("Title:", document.title, "(" + document.title.length + " chars)");
console.log("Description:", document.querySelector('meta[name="description"]')?.content || "MISSING");
console.log("Canonical:", document.querySelector('link[rel="canonical"]')?.href || "MISSING");
console.log("Schema blocks:", document.querySelectorAll('script[type="application/ld+json"]').length);
console.log("H1 count:", document.querySelectorAll("h1").length);

Copy, paste, Enter. Five answers in one second.

What each answer reveals. A title of "Home" means nobody ever thought about search. A missing description means Google writes its own, badly. A canonical pointing somewhere unexpected means the redirect conflict from check two probably exists here too. Zero schema blocks on a local business site means Google has to guess what the business even is. An H1 count of 0 or 4 tells you the page was assembled visually, headings picked for font size instead of meaning.

For a restaurant, a clinic, a hotel, anything local, the schema line is the one I care about most. LocalBusiness schema takes 20 minutes to add and most sites I check have none.

The note I write: "Title is 'Home', 4 chars. No description, no schema, three H1s. Foundations missing."

Minutes 9 to 12: the mobile walk-through

Put the laptop down. Pick up your actual phone, open the site on mobile data, and do the one thing the site exists for. Book the table. Fill the contact form. Add the product to cart.

DevTools mobile emulation lies to you. It fakes the screen size but not the thumb, not the keyboard, not the patchy 4G in a basement. The phone shows you things no tool reports: the cookie banner covering the WhatsApp button, the form where the keyboard hides the submit button, the menu that needs two precise taps to open, the font that forces a pinch-zoom on the pricing section.

I weight this check heavily because conversion lives here. The boutique hotel we built a WhatsApp booking bot for got 600+ direct bookings without a rupee spent on ads, and every one of those bookings was someone on a phone completing a flow that did not fight them. Speed gets people in the door. The walk-through decides if they reach the end.

Do the full action. Submit the form with real data and watch what happens after. No confirmation message is one of the most common findings I log, and it is invisible to every automated tool on earth.

The note I write: "Form submits into silence, no success state. Cookie banner blocks the call button on a small screen."

Minutes 12 to 15: Google Business Profile and reviews

Last check. Google the business by name and look at the panel on the right.

Is the profile claimed? Are the hours right? Do the photos look like the business today or the business in 2019? Are the categories correct, or did someone pick the first vague option years ago? Then read the reviews, and more importantly, the replies. A 4.2 rating with warm, specific owner replies beats a 4.6 with total silence, because the replies are the only place a customer hears the owner's voice before walking in.

For a local business this panel gets seen far more than the homepage. People decide here. The website only receives the visitors this panel sends.

The note I write: "GBP claimed but hours wrong, newest photo 14 months old, last 6 reviews unanswered including one complaint."

Why one line per finding

The constraint is the method. A 40-page PDF performs thoroughness. Five lines force understanding, and they fit on a call. When the prospect says "we feel the site is a bit slow," I read line one back to them with the exact millisecond figure, then go quiet. The psychology is plain concreteness bias: people trust the person holding specifics over the person holding adjectives. I took a client's PageSpeed from 39 to 77 once, did it free because the finding was that clear, and they stayed on retainer afterwards. The specifics did the selling. I just read my notes.

And see, none of this needs my stack, my pricing, or my opinion. PageSpeed Insights is free. Google is free. View source is free. Your phone is already in your pocket. The barrier was never access. The barrier was nobody sitting down for 15 minutes with a timer.

So here is the move. Today, before you answer one more email, run all five checks on your own site and write your 5 lines. If every line comes back clean, you have earned the right to ignore the next audit pitch that lands in your inbox. If three come back red, you now know exactly what that 40-page PDF was hiding, and you found it in 15 minutes for free.

If a line confuses you, send it to me. I read everything.