Track Core Web Vitals and your site score

Performance in a website's sidebar shows how fast the website is for the people who visit it, and how its homepage scores in a daily audit: Google's lab test, the basics search engines and link previews read, and its security headers. Nothing to install: the tracking script you already have measures it.

The daily site audit

Once a day SuprAnalytics audits the website's homepage (https:// and its domain) and scores it out of 100 three ways. The top of the page shows the overall score (their average), when the homepage was last audited, and four figures: the three parts' scores and the domain's Domain Rating, whose info tip says when it was read. Domain Rating doesn't change the overall score. A new website's first audit runs when someone on its team first opens Performance. Owners and editors can Run audit at any time, at most every 10 minutes; it takes up to a couple of minutes, and the latest result stays on the page meanwhile.

Score history charts the audits on a fixed 90-day timeline ending today, one metric at a time on a 0 to 100 scale, with one reading per day (the day's latest), so a first reading is a single point on its date. It doesn't follow the date range, which applies to real visitors only. A day without a reading is a gap in the line: an audit from before Domain Rating, or a day no audit ran, is never drawn as a zero.

• PageSpeed: Google's PageSpeed Insights runs Lighthouse on the homepage as a phone and as a desktop: the Performance, Accessibility, Best practices and SEO scores, the lab metrics (FCP, LCP, Total Blocking Time, CLS and Speed Index) against their thresholds with the points each earned, Performance's opportunities, and every scored SEO, Best practices and Accessibility check, passed or failed, with its points. The PageSpeed score is the average of the two Performance scores. Lab results change a little from run to run; real visitors (below) are what Google uses for search.
• Website quality: the title and meta description, favicon, viewport, robots.txt, a sitemap, llms.txt, one main heading, structured data (JSON-LD), a canonical URL, the page's language and character encoding, and each Open Graph and Twitter card tag (Twitter's title, description and image count when Open Graph has them).
• Security: HTTPS, whether http:// redirects to it, and the HSTS, Content Security Policy, frame protection, MIME type protection and referrer policy headers, with who serves the website when its headers say, and the domain's registration from its registry's public record: its age, registrar, expiry and, when not withheld, the registrant's country (all shown, not scored).
• Domain Rating: how strong the domain's backlinks are, 0 to 100, from Ahrefs, read with each audit. Shown beside the scores, not part of them.

Latest audit lists the three parts, each with how many checks it ran and how many need attention (warnings and failures). Open one to see all its checks, passed ones included, in subsections; PageSpeed's are for the device you pick, Mobile or Desktop. Open a check to see what was found (the title and its length, the favicon, the start of robots.txt and llms.txt, the page's headings, an FAQ's questions, the share image, each header's value), its points and how to fix it. Security also shows Domain trust and Infrastructure when the audit found them; these aren't scored. Audits are kept for 180 days.

Real visitor performance

On every page load the script reads the timings the visitor's browser reports and sends them once, when the visitor leaves the page or switches away from it. Each figure on the page is the 75th percentile over the dashboard's date range: three in four page loads were at least that fast, which is how Google reads them.

LCP, INP and CLS are Google's Core Web Vitals: the assessment says passed when all three are good at the 75th percentile. Each metric shows the shares of page loads that were good, needed improvement and were poor, and its change from the previous period. The chart follows one metric over the period, with dashed lines at its good and poor thresholds, and the table breaks every metric down by page, device, browser and country; click a row to filter by it. Pick Mobile or Desktop above the figures to see one kind of device.

• Only page, device, browser, country and hostname filters apply to these figures; the page says which others it left out.
• A page load is measured at the address it loaded at. On a single-page website, the pages it moves to without loading again aren't measured on their own.
• Not every browser reports every metric: Safari and Firefox don't measure layout shifts, for example, so a metric's count of page loads can be lower than another's.
• Rows with fewer than 5 page loads are marked with an asterisk: too few to rely on.
• Vitals don't count as events on your plan, and they're kept as long as the rest of your analytics.

Who can see it

Everyone on the website's team can see Performance; it's never on a public dashboard or in the All websites view. Running an audit needs an owner or editor.