Getting started

Six steps. The only one that needs your site is the second, and it is one line of HTML.

1. Create an account and add a website

Sign up with an email address or Google, and give your account a name — your company or agency. Then open Projects → Add project and enter the domain, for example example.com. The domain is the whole scope: every page on it, and on its subdomains, is tracked. There is no list of pages to maintain.

2. Paste the script

Each website has its own script tag, shown on its project page with your site key filled in. It looks like this:

<script src="https://vitalsdesk.com/beacon.js" data-site="YOUR_SITE_KEY" async></script>

Put it in the <head> of every page — usually that means your site template, theme header or tag manager, once. It is small, loads asynchronously, sets no cookies and never delays your page.

3. Check it is working

Open your site in a browser, then go to Real-user data. Your visit appears in the live feed within a few seconds. Core Web Vitals fill in as people browse; a page needs a handful of visits before its figures settle.

Every plan counts pageviews against a monthly allowance — 3,000 on Free. See Plans and limits for what happens if you go over.

4. Choose the pages to lab-test

Real-user data covers every page automatically. Lab tests are different: a full Lighthouse run of one page, on mobile and desktop, and they are what reports are built from. Your homepage is added for you; add the pages that matter most, or import them from your sitemap, on the project page.

Collect now tests up to three pages straight away. On paid plans, pick a Lab schedule and they are tested for you. Free includes 100 lab tests a month, run by hand.

5. Send a report

Open Reports → New report, pick a website and a month, and you get a branded, plain-English report with the top fixes — a link you can forward and a PDF you can attach. On paid plans, monthly reports are generated and emailed for you.

6. Bring in your team

Invite colleagues from Settings → Team. They see every website on the account. If you deploy often, set up release tracking next, so a slowdown comes with the deploy that caused it.