What a scan is in turbometrics
A scan is a complete analysis run for one URL. It delivers not just a score, but a report with metrics, sub-scores, bottlenecks, problems and recommendations.
Manual scans are ideal for:
- first analyses
- spontaneous quality checks
- before/after comparisons
- checks after deployments, plugin or theme changes
Guest scans without an account
turbometrics can be used without an account. Guest scans let you scan a URL directly and view the report — without registering.
Guest scans are always public and have limited functionality (no history, no alerts, no baselines). For repeatable analyses and monitoring, an account is required.
What you see in the report
A single report typically consists of:
- the overall score
- sub-scores such as speed, images, caching, WordPress and technical
- metrics such as TTFB, FCP, LCP, TBT and CLS
- the biggest bottlenecks
- problems and recommendations
- baseline or comparison context, if available
The goal is not just to display a number, but to deliver a usable technical assessment.
Frame timeline (filmstrip)
Every scan contains a frame timeline — a visual representation of the loading progress as a sequence of screenshots, showing how the page built up while loading.
The timeline appears in the report directly above the history and shows:
- frames as thumbnails in chronological order — each with a timestamp
- colour markers for relevant loading events:
- FCP (First Contentful Paint) — first visible content
- LCP (Largest Contentful Paint) — largest visible element fully loaded
- Load — the page's
onloadevent - Finished — fully loaded page
The timeline is captured separately for desktop and mobile and can be switched via tabs when both variants are available.
With more than 5 frames, scroll arrows appear for navigation. Below each frame, the timestamp is shown in ms or seconds.
Scan history in the report
Every report shows a scan history block directly on the page. It summarises the most recent scans of the same URL and gives you context immediately, without having to leave the report.
The block contains:
- an interactive graph with the development of score, TTFB, LCP and TBT — switchable via a dropdown
- a score delta against the immediately preceding scan
- back/forward navigation for quickly paging between scans
- a short list of the most recent scans of this URL with direct links
- an Open comparison button that puts the current scan up against a neighbouring scan
The current scan is highlighted in colour in the graph. Clicking another point in the graph opens that scan directly. The display is only available for your own and for public scans — guest scans have no history.
Scan history on the report page
Every report page shows a history block with the previous scans of the same URL. The features in detail:
- a score-over-time chart with the last 30 or 90 scans
- a metric dropdown for switching between score, TTFB, LCP, TBT and CLS
- clickable data points — clicking a point navigates straight to that scan
- the score delta between the current and the previous scan is shown prominently
- a region badge on every data point, so you can place the measurement location quickly
Exporting a report
On the report page, individual scan results can be downloaded in various formats via the "Export" dropdown:
| Format | Description |
|---|---|
| The complete report as a PDF document | |
| JSON | Raw scan data in JSON format |
| CSV | Scan metrics as a CSV file |
| Excel | An .xlsx file with 3 sheets (metrics, problems, recommendations) |
All export options are reachable directly via the "Export" button in the report header.
Regions
Scans can turn out differently depending on the region. A page can look unremarkable in Germany but show clearly higher runtime or different routing effects in Finland.
That is why turbometrics supports location-based measurements. Depending on the plan, the number of usable regions is limited.
Especially for:
- international sites
- CDN configurations
- hosting migrations
- load balancing
the location is often decisive.
Public and private scans
For logged-in users, a scan can be public or private:
- public suits team or client sharing
- private makes sense for internal analyses or unfinished projects
In guest mode, scans are always public.
Sharing a report (share link)
Individual scan reports can be shared on purpose via a share link — without the recipient needing an account. The link is unique and leads directly to the report.
Share links can be deactivated at any time. Once deactivated, the link is invalid immediately.
Notes on scans
A personal note can be added to every scan — directly in the report header. Notes are private and only visible to you.
Typical uses:
- recording the context of why a scan was made
- documenting anomalies or the deployment state
- commenting on a result for later evaluation
The note can be edited or deleted at any time. It appears as a preview in the scan list and stays visible in later comparisons as well.
Domain notes and colour dot
On the My domains overview, you can give every domain a short note and a colour dot.
Colour dot: a small coloured dot (8 px) right in the domain row. Five colours are available — grey, green, yellow, orange, red. Clicking the dot opens a popover with the colour options; the choice is saved immediately. The dot also appears on the domain detail page and in the dashboard.
Domain note: a short free text (max. 50 characters) as a reminder — for example "relaunch pending" or "client is watching". Edit it via the pencil icon in the row; the editor unfolds directly below it. The note is private and only visible to you.
Typical uses:
- sorting domains by priority or state using colour
- leaving a short note for the next step
- seeing at a glance which domains need attention
Good practice for manual scans
A manual scan is most helpful when you read it in context:
- choose the right location
- read the score only as an entry point
- check the biggest bottlenecks and the recommendations
- for relevant pages, follow up with comparison or monitoring
Common misconceptions
One scan is always enough
No. A single report is useful, but not automatically solid enough for decisions about stability or trend.
Only the overall score counts
No. In many cases LCP, TTFB, TBT, requests or clear problems matter more than the overall mark.
Public reports are always a good idea
No. In client or project contexts, private can be the better choice.
Further reading
→ Share links → Public reports → Baselines & comparison → Scoring & methodology