Quickstart: your first audit
Create an account, audit a website and read the first result. About five minutes.
Before you start
- A website address that is public on the internet, for example
www.example.com. Private, internal and local addresses are refused (which addresses can be audited). - An email address you can open: sign-up sends a confirmation link, and the app opens only after you confirm.
1. Create an account
- Go to Sign up.
- Enter your full name, your work email and a password of at least 8 characters, and accept the terms.
- Open the confirmation email and follow the link. You land on the sign-in page.
- Sign in. If you turned on two-step sign-in, enter the code from your authenticator app.
An account that is not confirmed gets a reminder each week and is deleted after 30 days.
2. Run the audit
- In the app, open Overview. It greets you by name.
- Type the website address into the field, for example
www.example.com. You can leave outhttps://. - Press Run audit.
Metricevo adds the site to your Sites list and puts an audit in the queue. You are taken to the Audit report page.
3. Wait for the result
The report says the audit is in the queue. Audits run in the background, usually within a minute. You do not need to keep the page open: every finished audit is listed under Audits.
Why a queue? An audit never runs while a request waits on it. This keeps the app fast and lets Metricevo pace its outgoing requests, so the sites it reads and the services it uses are never flooded. The asynchronous audits page explains the same model for the API.
4. Read the report
The report opens with one tile per area, then the checks. To fix is selected first: the checks that failed, with their severity. Switch to All checks to see what passed too.
| You see | It means | Do something? |
|---|---|---|
| To fix | The check failed. High, medium or low says how much it matters. | Yes, start with high. |
| Passed | The check passed. | No. |
| No data | There was nothing to check, for example no image on the page. | No. It is not a failure. |
| Not tested | This audit cannot see it from outside, for example the TLS certificate’s expiry. | No. It is not a failure. |
| Not measured | The measurement itself failed, for example the site did not answer in time. | Run the audit again later. |
The full explanation is in Read an audit report.
5. Next steps
- Repeat it. On Sites, set the site to repeat every week or every month: Run and schedule audits.
- Automate it. Create an API key and run the same audit from a script: API quickstart.
- Something looks wrong? Press Report a problem on the report: Report a problem.