Web Vitals
Real-visitor loading, interaction and layout stability for your site, by device and by page type.
Web Vitals shows how fast your site is for real visitors, from the field data Google publishes about real Chrome users, alongside a lab test of the homepage. It needs no connection: it works from your website's address.
What it shows
Pick a device (all devices, phones or desktop) to see the 75th percentile of:
- LCP, Largest Contentful Paint: how long the main content takes to appear.
- INP, Interaction to Next Paint: how quickly the page responds to input.
- CLS, Cumulative Layout Shift: how much the layout jumps while loading.
- FCP, First Contentful Paint, and TTFB, Time to First Byte.
Each is rated against Google's published thresholds for good and poor:
| Metric | Good up to | Poor above |
|---|---|---|
| LCP | 2.5 s | 4 s |
| INP | 200 ms | 500 ms |
| CLS | 0.1 | 0.25 |
| FCP | 1.8 s | 3 s |
| TTFB | 800 ms | 1.8 s |
The field data covers a rolling 28-day window, and RankDebug keeps the history so you can see a metric change over time.
Homepage Lab Score is a mobile lab test of the homepage, run with each site check. A drop of 15 points or more between checks is reported as Performance Dropped.
By page type
By Page Type groups your busiest pages by their first path segment, so /cars/golf-7 belongs to /cars/*. The pages are chosen by Search Console clicks over the last 28 days. For each type it shows the median across its measured pages now and four windows earlier, so a template that got slower stands out.
Field data only exists for pages with enough Chrome visits. Pages with too few are skipped, and a site with too little traffic shows No real-visitor data yet.
Related documentation
- Guide
How the parts of RankDebug fit together, and where to find each one in the dashboard.
- Connections
How data sources connect to a workspace, how often they sync, and what happens when you disconnect one.
- Search Console
Connect Google Search Console with read-only access. What RankDebug pulls and what it is used for.
- Google Analytics
Connect Google Analytics with read-only access to see what search visitors did after they landed.
- Cloudflare
Connect Cloudflare with a read-only API token to see which crawlers reach your site and what the edge did to them.
- Bing Webmaster Tools
Connect Bing Webmaster Tools with an API key to add Bing search data and crawl statistics.
- GitHub
Connect a GitHub repository so production deploys are recorded on their own, with the SEO-relevant files each one changed.
- GitLab
Connect a GitLab project with a read-only token so production deploys are recorded on their own.