What is actually wrong with your site
The same audit I run on a site before a call. Speed, what crawlers and assistants can see, and the paths a visitor is meant to follow. It takes about a minute and it tells you which findings are yours to fix and which are the platform’s.
No sign-up, no email. Nothing is stored.
Working
Looking at the site.
Loading the page, reading what a crawler would read, then asking PageSpeed for the speed numbers. The last part is the slow one: it runs a real browser on Google’s hardware.
That did not work
Could not check that.
What it looks at
Four things, and everything under them.
Not a checklist of everything that could be true of a website. These are the checks that actually run, and each one produces findings in the report above or it is not listed here.
Speed, as Google measures it
A full PageSpeed run on mobile, plus what real Chrome users on your site actually experienced, when there are enough of them to report.
- Performance, accessibility, best practices and SEO scores
- LCP, CLS, TBT and first paint
- Every third-party script, with what each one costs in main-thread time
- Total page weight, and how much of it is your own hosted media
What AI crawlers can see
Most assistants read the HTML and do not run your JavaScript. Anything applied in the browser is invisible to them, which is the finding that surprises people most.
- SEO fixes applied by script rather than in the page
- Structured data, and whether it parses
- Organization and FAQPage schema where the content calls for it
- llms.txt
Technical SEO
The mechanical layer. None of it is interesting and all of it has to be right, on the homepage and on the pages that convert.
- noindex, titles, meta descriptions and canonicals
- robots.txt and whether it points at a sitemap
- A sitemap that exists, works, and carries lastmod dates
- Internal links that hit a redirect instead of the page
- Images with no alt attribute
The paths a visitor is meant to follow
The checks nobody runs, because they need somebody to actually follow the links. This is where the report most often finds something you did not know about.
- Buttons whose text names one thing and whose link goes to another
- CTAs with no destination at all
- Anchor links pointing at a section ID that is not in the page
- Overlapping tools doing the same job twice
What comes back
A list you can hand to a developer.
01
The numbers, with what they mean
Four scores and the core metrics, each labeled in plain words rather than in acronyms. Plus the third-party table, which on most sites is where the answer is.
02
Findings, ordered by what to do first
Every finding says what it is, why it matters, and what to actually do about it, with the evidence quoted, so nobody has to take it on trust or go hunting for the thing being described.
03
Who owns each one
Some of what a speed tool reports is the platform’s and not yours. A finding that is Webflow’s CDN doing its job is not the same as one you can fix, and the report does not rank them together.
What it will not do is tell you which of it matters. A slow page on a site nobody visits is not your problem, and a clean report on a page that does not say what you sell is not a win. The tool finds what is measurably wrong. Deciding which two things are worth your week is the part that needs a conversation.
Before you ask
Questions about the audit.
Is it really free, and do I have to give you an email?
Free, and no. There is no form beyond the address, nothing is stored, and I do not see the result. It is generated in your browser from a single request and it is gone when you close the tab. If you want me to look at it, that is a separate decision you make afterwards.
Does it work on sites that are not built in Webflow?
Yes. Everything it checks is true of any site, and it detects the platform on the way in: WordPress, Framer, Next.js, Shopify and the rest. The advice leans on Webflow where the finding is Webflow-specific, because that is what I know best.
How long does it take?
Usually under a minute. The slow part is PageSpeed: Google runs a real browser against your page on their own hardware, and that takes as long as it takes. Everything else is a handful of requests.
Is this the same audit you run before a call?
It is the same engine. What I run before a call also crawls the links, checks the pages behind the nav, and I read the result rather than a page printing it. This is the part that can run on its own without me in the loop.
What can it not tell me?
Whether any of it matters for your business. A slow page on a site nobody visits is not the problem, and a perfect score on a page that does not say what you sell is not a win. It finds what is measurably wrong; deciding which two things are worth your time is the conversation.
Will the score be different if I run it twice?
A little, yes. Lab scores move a few points between runs on the same URL, which is the nature of running a browser on shared hardware. The findings underneath are stable, which is why the report leads with those rather than with the number.
Reach out and see if we are a good fit.
Currently booking two to four weeks out.