Run your first audit

Start a scan

Paste your URL on the home page and start the audit. The URL is normalised and its protocol validated before anything runs, then field and lab checks go out together — field data usually answers in seconds, the lab run takes longer because it is a real Chrome browser loading your page.

Choose the device context

Switch between desktop and mobile to see how each audience actually experiences the page. Mobile field data routinely exposes problems desktop hides, and it is the profile Google weights most heavily for the majority of sites. Each device profile counts as its own scan.

Read the executive brief

The brief carries the field verdict, the lab score and the single biggest risk or opportunity. It is the part to paste into a stand-up: it says whether real visitors are having a bad time, and what is causing it, without requiring anyone to read an audit list.

Act on the prioritized fixes

Move to “What to fix first”. Each finding names the element or request responsible, quotes what it measured on your page, and estimates what fixing it recovers. Work down the list — it is ordered by measured cost to your visitors, not by audit ID.

Save the site, or lose the history

A one-off scan gives you the report and nothing else. Saving the site into a project is what starts the trend line, and it is the prerequisite for everything that makes this more than a speed test:

• History — every scan is kept, so you can prove a fix worked.
• Performance Pulse — scheduled re-checks and regression alerts.
• Competitor Eye — rivals are pinned against a saved site.

Each saved site counts against your plan’s site limit; a URL you scan once and never save does not.

What a scan costs

One URL on one device profile is one scan. Running the same page on mobile and desktop is two. A scheduled Pulse re-check costs the same as one you ran yourself.

Limits reset on the first of the month. Reaching one does not delete anything — new scans wait for the next cycle and scheduled sites pause. See pricing for the current ceilings.

Settle into a cadence

• Take a baseline scan of every key landing page.
• Re-scan after a release, or after any change to a shared template.
• Turn on Performance Pulse so the re-checks happen without you.