Back to benchmark
Benchmark result

Vivino

vivino.com

Scanned September 7, 2026

Observable Frontend Consistency Score
17/100
— Several areas for review

This score measures Vivino's observable frontend consistency — patterns observable in publicly accessible frontend code and rendered pages, primarily vivino.com's shipped CSS. It is not a complete measure of Vivino'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
vivino.com homepage (0 of 3 linked stylesheets)
Observable data coverage
6,393 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/40

Color discipline

2.8/25

Typography discipline

14/20

Spacing discipline

0.7/15

What 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 67 pair(s) of near-identical colors (e.g. #F7F3F0 vs #F2EBE6) — 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.

Large public-facing color palette

120 unique color values were detected in the shipped CSS. This may indicate palette fragmentation, particularly where several appear to serve the same semantic role — though a large palette can also legitimately reflect semantic states, data-visualization colors, multiple themes, or brand/product variants.

Benchmark v1.1

Own or manage Vivino?

Being listed here isn't a submission, endorsement, or verified participation — Vivino has not necessarily reviewed or confirmed this result.