Contact

Email

There is no contact form here, on purpose. A form would need a backend to receive it, and this service is built with no database and nothing stored on its users — adding a mailbox server to accept mail would contradict that. Email works and costs nothing.

hello@example.com

What to include

• The URL you audited. This is the important one. A finding is only verifiable against the page it came from.
• The issue ID. Every finding in the report has an ID you can copy, and it identifies exactly which check fired.
• What you expected instead. If the page looks correct to you and the tool disagreed, say what you saw.
• Your browser and operating system, if the problem is that the page renders or behaves wrongly rather than a wrong finding.

Do not send confidential or personal information. The tool keeps no logs of your requests, which means a support request is the only record that will exist of the audit — so include anything needed to reproduce the problem in the first message.

Reporting a false positive

These are the reports that improve the tool most, because a check that reports a problem where there is none is worse than no check at all: it costs you time and trains you to ignore the output. Contrast in particular is a heuristic, and the tool says so on the About page. If it flags something that is clearly fine, that is a defect worth knowing about.

What we cannot help with

• Ranking or traffic advice for a specific site. This tool reports on pages; it has no knowledge of your data, market or competitors.
• Auditing a site you do not own without permission.
• Requests for the PageSpeed Insights API key. It is a server-side secret and is never exposed to the browser, which is why you never see it.

Response time

This is a small, independent project run on free infrastructure, so replies can be slow and there is no support SLA. That is a fair trade for free audits, no tracking and no upsell.