What we check
Every item below is decided from your live home page: the HTML your server sends, the headers it returns, and how long it took to answer. Nothing is estimated, and nothing is inferred from a database of what we think your site looks like.
Turning visitors into customers
Can someone who lands here actually contact you?
- Whether your phone number is a tap-to-call link, plain text, or missing entirely
- Whether there is a contact form or an email link on the home page
- Whether analytics are installed, so you can see where visitors come from
- Whether shared links show a proper preview card on Facebook, WhatsApp, and iMessage
- Whether you link out to Google Maps and your social profiles
Getting found on Google
What search engines can understand about this page.
- Page title — present, and the right length to display in full
- Meta description — present, and the right length
- Whether anything is telling Google not to index the page
- robots.txt — present, and not blocking the whole site
- Sitemap — present, either at the usual address or declared in robots.txt
- Exactly one main H1 heading
- LocalBusiness structured data, so Google can read your address, hours, and phone
- A declared canonical address
- Enough readable text on the page to rank for anything
- A declared page language
Speed
How long a visitor waits before they see anything.
- Server response time, measured on the request we just made
- Page HTML size before images, scripts, and fonts
- Whether the server compresses what it sends
- Scripts in the head that block the page from rendering
- How many separate files the page asks the browser to fetch
- Whether static files are cached for repeat visitors
- Whether images use modern formats
Phone experience
Most visitors are on a phone. This is what they get.
- A mobile viewport, without which phones show a shrunken desktop page
- Whether pinch-to-zoom is blocked
- Markup that predates smartphones — font tags, frames, Flash
- Whether images offer a phone-sized version
- Alt text on images
Trust & security
What a visitor — and their browser — sees before they believe you.
- HTTPS, and whether the insecure address redirects to it
- Insecure files loaded on a secure page
- Standard browser security headers
- A favicon for the browser tab
- Whether the copyright year suggests the site has been abandoned
What we do not claim to know
- Your rankings. This is a check of your page, not of what position you hold for any search term.
- What happens after the page loads. We read what your server sends. A tag that a tag manager injects later is invisible to us, which is why analytics is reported as a warning rather than a definite failure.
- Pages other than your home page. The report covers the one address you gave us.
- How it looks. Design is a judgement call and we do not pretend to score it.