A real report, on this website
What gets checked Download this report as a PDF
No email, no signup. It is this page, printed.
Most audit companies show you a designed mock-up of a report. This is the actual output of the engine this site sells, pointed at this site. Nothing below was written by hand — the scores, the findings and the recommendations are read straight out of the run.
A real run, on 22 August 2026, against the site as it stood that day. It was the live domain at the time, not a staging build: the same HTTPS, DNS and host a visitor reached. The site has since been rebuilt — new pages, a new stylesheet and a different Content-Security-Policy — so the numbers below describe the site of that date and not the one you are reading. They are left standing rather than quietly refreshed, because a report you can date is worth more than one that always claims to be current.
Two of the scores below are low on purpose, and both are explained where they sit. A check that could not run is never reported as a defect — those are listed at the end as conditions of the run, with the reason for each.
Every category, scored
A dash means the check could not run, not that it passed.
What it found: 2 findings that stand
0 critical, 0 warning, 2 informational. Everything else the engine raised is below, either overruled with a reason or listed as unmeasurable — a sample report that only shows a site passing is an advertisement, not a sample.
- infoInfrastructure
DNSSEC not enabled
Sign the zone at the DNS provider, then publish the DS record it returns at the registrar. Until then a poisoned resolver can send visitors to another server and the padlock still shows, because the certificate belongs to whatever answered.
- infoAnalytics
No Google Search Console verification found
Add the verification meta tag or the DNS TXT record, so indexing problems are visible. It is a static tag, not a tracker — it costs nothing this site is unwilling to spend.
One-page developer action list
The 2 findings that stand, in priority order, with what to change. This is the page to forward — it repeats nothing from the rest of the report and needs no context to act on.
-
Info · Infrastructure
DNSSEC not enabled
Do: Sign the zone at the DNS provider, then publish the DS record it returns at the registrar. Until then a poisoned resolver can send visitors to another server and the padlock still shows, because the certificate belongs to whatever answered.
-
Info · Analytics
No Google Search Console verification found
Do: Add the verification meta tag or the DNS TXT record, so indexing problems are visible. It is a static tag, not a tracker — it costs nothing this site is unwilling to spend.
A further 9 findings were raised by the engine and overruled by hand, each with the reason recorded against it. They are below under “What a person overruled” and are not developer work.
What a person overruled: 9 findings
This is the part a scanner cannot do. Every one is a real rule, correctly triggered, that this site is not going to act on — and the reason is written down. It is what “every finding checked by hand” actually means.
- criticalTrust signals
No customer reviews or testimonials found on the page
Correct, and it stays. Writing a testimonial would be the same category of lie this product exists to find on other people’s sites, so the critical stays on the board.
- warningAnalytics
No web-analytics platform detected
This site runs no analytics at all — no GA4, no tag manager, no pixel, no session recorder. That is the promise on the homepage, and it is worth more than the points.
- warningAnalytics
No JS error monitoring detected (Sentry/Bugsnag/Rollbar)
Would mean shipping a third-party script to every visitor. This site runs no analytics at all — no GA4, no tag manager, no pixel, no session recorder. That is the promise on the homepage, and it is worth more than the points.
- infoAnalytics
No conversion tracking detected
Same reason: nothing measures visitors here, on purpose.
- infoAnalytics
No custom event tracking detected
Same reason. Interactions worth counting are counted server-side, where an external audit cannot see them — and where they cost the visitor nothing.
- infoAnalytics
No Real User Monitoring (RUM) detected
Same reason. RUM means a script on every page timing every visitor, which is the thing being declined.
- infoSocial
No review/rating structured data
Review schema describes reviews. There are none to describe, and marking up reviews that do not exist earns a manual action from Google as well as being a lie.
- infoSpeed
No ETag or Last-Modified headers
A deliberate trade. The host rewrites the HTML to add navigation prefetching, and rewriting it drops the validator. The prefetch is worth more to a visitor than a conditional request on a page that already revalidates on every view, so the setting stays and the finding stands.
- infoLocal SEO
No embedded Google Map
An embedded map loads Google’s resources and sets its cookies on the visitor — the same objection as the analytics above. The address is in the footer and in the structured data instead.
What could not be measured: 3 checks
Conditions of this run, not defects. Each says why.
- infoSpeed
Real-visitor speed data (Core Web Vitals field data)
Google holds no real-user data for this domain: it does not yet get enough Chrome traffic to be measured. Nothing to report either way.
- infoAnalytics
Whether uptime monitoring is running
Monitoring is configured off-site. None of it is visible from outside the page, so its absence is not asserted.
- infoLocal SEO
The Local SEO category as a whole
Not applicable — this is not a business with a premises a customer walks into. Recorded as not applicable rather than scored as zero, which is why the tile shows a dash.