Features

Technical SEO Audit Keyword Rank Tracking Competitors & Backlinks AI Search Visibility AEO & Schema Content & Blog Ideas Local SEO & GBP Performance & CWV Indexing & Uptime Reports & AI Assistant

Company

How it works FAQ Blog Privacy Policy Terms of Service Book a demo
Home Features Performance & Core Web Vitals
Performance & Core Web Vitals

Every page. Every metric. Ranked worst first.

A single site-wide speed score is close to useless. This module scores each URL separately on mobile and desktop, records LCP, CLS and FCP, and puts the low scorers at the top where they belong.

0
URLs scored per run
0
Core Web Vitals tracked
0
Device profiles
0
Pages of results
Dashboard · Performance · mobile, desktop & Core Web Vitals
Performance module showing per-page mobile scores in coloured gauges with LCP, CLS and FCP values, low-scoring pages highlighted in red at the top

Low scores are highlighted and sorted first, with LCP, CLS and FCP shown inline for each URL.

Per page, not per site

Your homepage score is not your site's score

Most speed tools test one URL and let you assume the rest matches. In reality a homepage at 46 and a privacy policy at 85 are the same site — and it's the service pages in between that convert.

Every crawled page gets its own gauge, its own vitals, and a clear low-score warning where it fails. Filter by URL to jump straight to the page you're working on.

  • Mobile and Desktop tabs scored independently
  • LCP — largest contentful paint, colour-coded against thresholds
  • CLS — cumulative layout shift, the metric most sites quietly fail
  • FCP — first contentful paint for perceived speed
  • Low Score warnings on any page below threshold, sorted to the top
Dashboard · Performance · mobile tab, page 1 of 6
Performance cards showing scores of 42, 46, 52, 56, 60, 64, 67, 80 and 85 for individual pages with their LCP, CLS and FCP values
Delivery issues

The technical causes behind slow scores

Scores tell you which pages are slow; the technical sweep tells you why. Unminified JavaScript and CSS across 63 pages, cache headers not set, oversized HTML documents and mixed content all show up as counted, addressable problems.

These are the fixes that move Core Web Vitals across the whole site at once rather than page by page.

  • Unminified JS and CSS counts across the site
  • Cache-control status per URL — “Not Set” is the common quick win
  • HTML document weight in KB, with large documents flagged
  • Mixed content and non-secure resource detection
Dashboard · Technical SEO Issues · minification & cache
Technical issues counters showing 63 unminified JS, 63 unminified CSS, 44 Open Graph issues, 2 large HTML documents and 63 cache issues

The three vitals that count

Google's Core Web Vitals, measured per page and tracked across runs.

LCP — Largest Contentful Paint

How long until the main content is visible. Usually a hero image, a font load or a render-blocking script. The most common failure of the three.

CLS — Cumulative Layout Shift

How much the page jumps while loading. Ads, embeds and images without dimensions are the usual culprits, and it is very fixable.

FCP — First Contentful Paint

When the first pixel of real content appears. It drives perceived speed and bounce rate more directly than total load time does.

Performance in context

Speed problems rarely stay contained — they show up in indexing and engagement too.

Dashboard · Analytics
Analytics overview with sessions, engagement and page performance metrics

Engagement metrics alongside speed, so you can see what slow pages actually cost.

Dashboard · Indexing Status
Crawl and indexing audit showing response time per URL alongside indexing verdicts

Response time is recorded per URL in the crawl audit and correlates with indexing outcomes.

FAQ

Questions about performance & core web vitals

The per-page scores and vitals shown here are lab measurements taken under consistent conditions, which makes them comparable across pages and across runs. Consistency is what you want for prioritisation — field data varies with your visitor mix and is better read alongside, not instead.
Mobile testing simulates a slower connection and less capable device, which exposes render-blocking resources and heavy JavaScript that desktop hardware absorbs. Since most search traffic is mobile, the mobile score is the one that matters for ranking.
Sort by score, take the worst page, and look at which vital is red. LCP problems are usually images or render-blocking resources; CLS is almost always missing dimensions on images and embeds. Both are typically faster to fix than they look.
No — it identifies and prioritises them. The technical issues table gives your developer a precise list: which files are unminified, which URLs have no cache headers, which documents are oversized.

Score every page, not just the homepage

Get mobile and desktop scores with Core Web Vitals for every URL on your site.