Peakon
peakon.com
Scanned September 7, 2026
This score measures Peakon's observable frontend consistency — patterns observable in publicly accessible frontend code and rendered pages, primarily peakon.com's shipped CSS. It is not a complete measure of Peakon's design-system maturity, internal tooling, design process, or team structure, which this benchmark has no visibility into. CSS-in-JS, Tailwind-style utility classes, hashed class names, JavaScript-rendered states, and authenticated product surfaces can all reduce how much is actually observable here. See the full methodology for what is and isn't measured.
Evidence & confidence
- Analysis date
- September 7, 2026
- Surface analyzed
- peakon.com homepage (1 of 4 linked stylesheets)
- Observable data coverage
- 41 CSS declarations analyzed
- Confidence level
- Low confidence in the observable CSS sample
This confidence level describes the completeness of the observable CSS sample, not the maturity of the organisation's full design system.
Only a small amount of CSS could be gathered, most linked stylesheets couldn't be fetched, or both. Treat this result as a rough, low-confidence signal rather than a firm conclusion.
Category scores
Token adoption
0/40Color discipline
22.4/25Typography discipline
20/20Spacing discipline
15/15What we found
The highest-leverage issues, ranked by impact.
Adopt CSS custom properties for color
Only 0% of color values reference a design token (var(--...)). Migrating hardcoded hex/RGB values to tokens is the single highest-leverage fix for long-term consistency and theming.
Review near-duplicate colors
We found 6 pair(s) of near-identical colors (e.g. #FFFFFF vs #F6F7F9) — close enough that they're likely candidates for consolidation into a single token, though a static scan can't confirm design intent. Worth a quick manual check before merging.
Benchmark v1.1
Own or manage Peakon?
Being listed here isn't a submission, endorsement, or verified participation — Peakon has not necessarily reviewed or confirmed this result.