Documentation

Getting started

Guest scans, first reports and the quickest route to reliable results.

Guest scans without an account

You can try turbometrics out directly without an account. Guest mode is deliberately kept simple:

  • one guest scan per 24 hours
  • this scan is always public
  • the result can be shared via the report URL

That is fine for a first impression, but it is no substitute for a proper workspace.

What a free account adds

With an account, the open test turns into a personal product area:

  • private scans
  • your own history
  • history and comparison in your own context
  • scheduled scans within the limits of your plan
  • alerts and notifications

If you monitor websites regularly or work on client sites, an account is almost always the sensible next step.

How to get started properly

1. Choose a URL and a location

Enter the full URL and pick a location if needed. This matters, because results can differ noticeably from region to region.

2. Do not judge a report by the score alone

The report shows you:

  • the overall score
  • sub-scores
  • the biggest bottlenecks
  • problems
  • recommendations
  • browser runtime and metrics

The score is only the entry point. For real work, the underlying signals are usually more important.

3. Think in comparisons and history

A single scan is only a snapshot. For conclusions you can rely on, you should start early on to:

  • use comparison values
  • set a baseline
  • or set up scheduled scans

Public and private scans

For logged-in users, visibility depends on the chosen scan type and the setting:

  • public scans are easier to share
  • private scans stay in the account context
  • guest scans are always public

This distinction matters when you analyse client sites, internal projects or URLs that have not been released yet.

Frequently asked questions

Why is my guest scan public?

Because guest mode is meant as a fair, open way to test the product. For private results, a normal account is the intended route.

Why do two measurements differ?

Region, load, cache state, third-party scripts, dynamic content or mobile/desktop runtime can all change results. That is normal.

What is the best next step after the first scan?

Usually one of three routes:

  • measure an important page again
  • use baseline and comparison
  • create a scheduled scan with alerts

Dashboard

After your first scan, the dashboard gives you a compact overview of all monitored domains with their current score, live data (RUM), open alerts and the scan statistics of the week. It is the central entry point for the daily overview.

Further reading