DealerDB · From Driverseat
How the performance score works
We measure loading, responsiveness, and visual stability using Google’s Chrome User Experience Report (CrUX). This is a website performance benchmark, not an assessment of a dealership’s service, sales, accessibility, security, or conversion rate.
Real visitors
CrUX aggregates eligible Chrome users’ experiences across a website’s origin and device types, over a rolling 28-day window. Sites need sufficient CrUX coverage to be scored. Absence from CrUX does not establish poor performance.
We use the 75th percentile (p75) of each metric. Lighthouse audits and screenshots can explain opportunities, but do not change the score.
Google’s CrUX methodologyScoring · crux-weighted-v1
All five finite, nonnegative metrics are required. Missing metrics are never treated as zero or estimated. Each contribution is clamped between zero and its full weight; the weighted sum is multiplied by 100.
| Metric | Best | Worst | Weight |
|---|---|---|---|
| First Contentful Paint (FCP) | 1000 ms | 6000 ms | 15% |
| Largest Contentful Paint (LCP) | 1000 ms | 8000 ms | 25% |
| Cumulative Layout Shift (CLS) | 0 | 0.8 | 30% |
| Time to First Byte (TTFB) | 250 ms | 3000 ms | 15% |
| Interaction to Next Paint (INP) | 100 ms | 1000 ms | 15% |
Contribution = clamp(1 − (value − best) / (worst − best), 0, 1) × weight
A reproducible example
- FCP: 2500 ms
- LCP: 3500 ms
- CLS: 0.1
- TTFB: 500 ms
- INP: 200 ms
These values produce 79.79 / 100, calculated with the same configuration used by ingestion.
Independence
Scores reflect measured performance and are independent of whether a dealership uses Driverseat or requests a review. DealerDB is published by Driverseat, a dealership website provider.
Questions or corrections: contact the team.