72 checks · free · no signup

See exactly what Google and AI see on your site.

A full technical audit in about seven seconds — SEO, speed, security and mobile, measured in a real browser, plus a written analysis of how findable you are to AI answer engines.

The method

Four passes over your page, each answering what the last one could not.

01

Read the source

One streaming pass over the HTML — title, description, headings, alt text, canonical, structured data, render-blocking resources, DOM weight. Twenty-six checks in about a second.

02

Fetch every asset

Each script, stylesheet and image is requested and measured: transfer size, cache headers, minification, image format, and whether it is served larger than it displays.

03

Open it in Chrome

A real browser navigation returns the certificate chain, negotiated compression, wire byte counts, Core Web Vitals and console errors — including everything JavaScript injects after load.

04

Ask what AI sees

Whether answer engines can crawl and attribute the site, and whether a language model recognises the brand at all. Scored as findability, and labelled as such.

Questions

Is the AI Visibility score a real measurement?

It is a findability score, not a citation count, and the report says so. It combines whether a language model recognises the brand from training data with how reachable and attributable the site is to answer engines. It does not query ChatGPT, Gemini or Perplexity live — doing that meaningfully takes minutes and dozens of prompts, which belongs in ongoing tracking rather than a one-shot audit.

Why do results appear in stages?

Because the checks finish at different speeds. Reading the HTML takes about a second, fetching every subresource a few more, a real browser navigation around five. The written analysis is last. Showing each batch as it lands beats watching a spinner for the slowest one.

Where does the performance data come from?

A real Chrome navigation, reading Core Web Vitals from PerformanceObserver inside the page. It is a lab measurement from a datacentre, not field data from your visitors, so LCP and TTFB are delivery indicators rather than what any individual user experiences.

What do you keep?

The report, so it has a shareable link, and a mobile screenshot for seven days. Page content is not retained beyond what the report shows.