1440×900 · 390×844
https://cal.com

Heading outline, share card & baseline checks

OUTLINE & PRIMARY CTAdense density
H1×1 · H2×12
H1
H2
H2
H2
H2
H3
H3
Primary CTAGet started
Next.jsshadcn/uiTailwindlang=en

Words

2456

Action candidates

28

Links

148/20

HTML

675 KB

SHARE CARD & METAog:image ✓

cal.com

Cal.com | Scheduling Software for Online Bookings

The highest-rated scheduling system that helps you grow your business and better find time.

Title chars49 ch · Ideal
Meta chars91 ch · Ideal
HEADERS & ASSETS4/6
HTTPS
HSTS
CSP
nosniff
Viewport
JSON-LD
Scripts55 ext · 78 inl
Image alt coverage48/145 (33%)
Third-party hosts8 hosts

What makes it work

Custom calSans and inline UI chips own the category

Pairing heavy calSans with an inline 'Intro call 30m' chip demonstrates scheduling mechanics right inside the H1.

Calendar-native OAuth reduces friction

Leading with Sign up with Google and Sign up with Microsoft matches how users actually connect their calendars.

Where to focus next

  1. 01

    Clean up accessible text inside the chip-decorated H1

    Inline UI chips inside the H1 concatenate decorative slot timestamps into the heading's accessible text.

    Mark decorative inline booking chips aria-hidden="true" so crawlers and assistive tech read 'Where people find the time to meet' cleanly.

Colors, type scale & CSS tokens

Light ground · MonochromeText contrast 15.5:1 AAA
Click any swatch to copy HEX
cal.com

calSans

ABCDEFGHIJKLMNOPQRSTUVWXYZ · 0123456789

Embedding miniature booking chips directly inside an 80px calSans headline turns scheduling into an immediate visual hook.

TYPE SCALE

80px / 16px

5.00× display ratio

RHYTHM

LH 24px

Wt 700 · Track -0.8px

CORNERS

8pxButton
/* Extracted design tokens from cal.com via VibeCheck */
:root {
  --color-bg: #ffffff;
  --color-surface: #f4f4f4;
  --color-ink: #242424;
  --color-muted: #b4b4b4;
  --color-line: #e4e4e7;
  --font-display: "calSans", system-ui, -apple-system, "PingFang SC", "Noto Sans SC", sans-serif;
  --font-body: "calSans", system-ui, -apple-system, "PingFang SC", "Noto Sans SC", sans-serif;
  --text-h1: 80px;
  --text-body: 16px;
  --leading-body: 24px;
  --tracking-display: -0.8px;
  --radius-button: 8px;
  --space-section: 0px;
  --shadow-surface: rgba(0, 0, 0, 0) 0px 0px 0px 0px, rgba(0, 0, 0, 0) 0px 0px 0px 0px, rgba(0, 0, 0, 0) 0px 0px 0px 0px, rgb(255, 255, 255) 0px 0px 0px 2px, rgba(0, 0, 0, 0) 0px 0px 0px 0px;

  /* Source custom properties sample */
  --bend: 0px;
  --card: #fff;
  --ring: #9ca3af;
  --muted: #f3f4f6;
  --accent: #f3f4f6;
  --border: #e5e7eb;
  --hp-bar: color-mix(in oklab, #fff 52%, transparent);
  --radius: .625rem;
}

Parameters are element samples. Empty values are unknown, and individual samples are not site-wide rules.

Audit findings

Clean up accessible text inside the chip-decorated H1

Taste

Inline UI chips inside the H1 concatenate decorative slot timestamps into the heading's accessible text.

→ Mark decorative inline booking chips aria-hidden="true" so crawlers and assistive tech read 'Where people find the time to meet' cleanly.

evidence.json: h1 reads 'Where people Intro call30m 15:00...'

No Content-Security-Policy

Launch

A CSP is the standard way to limit script sources. Vibe-coded pages often load anything, including injected scripts.

→ Start with a report-only CSP, then default-src 'self' and an explicit script-src.

content-security-policy missing

No X-Content-Type-Options

Launch

Without nosniff, browsers may interpret a file as a different type than you sent. It is a one-line header.

→ Set X-Content-Type-Options: nosniff.

x-content-type-options missing

No Referrer-Policy

Launch

The default referrer can leak internal paths and query strings to third parties.

→ Set Referrer-Policy: strict-origin-when-cross-origin.

referrer-policy missing

Copy prompts or rules to your AI Agent

Switch between page fixes, style recreation, DESIGN.md, or a reusable SKILL.md guardrail file.

Paste into Claude Code / Cursor / Codex chatFull Taste Skill guide →
Improve the current project using the 2026-11-11T06:47:33.361Z snapshot of https://cal.com. First identify changes since capture; do not revert newer behavior to the old snapshot.

Design baseline
Over a subtle grid on #ffffff, an 80px calSans headline with inline calendar chips leads straight into Google/Microsoft sign-up buttons and a live booking preview.
{
  "colors": [
    {
      "role": "bg",
      "hex": "#ffffff"
    },
    {
      "role": "surface",
      "hex": "#f4f4f4"
    },
    {
      "role": "ink",
      "hex": "#242424"
    },
    {
      "role": "muted",
      "hex": "#b4b4b4"
    },
    {
      "role": "line",
      "hex": "#e4e4e7"
    }
  ],
  "fonts": {
    "body": "calSans",
    "display": "calSans",
    "stack": [
      "calSans",
      "-apple-system"
    ]
  },
  "radius": {
    "button": "8px",
    "card": "",
    "field": ""
  },
  "space": {
    "section": "0px",
    "card": ""
  },
  "type": {
    "h1": "80px",
    "body": "16px",
    "weight": "700",
    "lineHeight": "24px",
    "letterSpacing": "-0.8px"
  }
}
Values come from one capture. Fonts, radii and spacing are element samples, not a universal site-wide specification. Empty values are unknown. HTML bytes are source size, not compressed transfer size; script counts are DOM tags, not network requests.

Actions
1. Clean up accessible text inside the chip-decorated H1
Mark decorative inline booking chips aria-hidden="true" so crawlers and assistive tech read 'Where people find the time to meet' cleanly.
Evidence: evidence.json: h1 reads 'Where people Intro call30m 15:00...'

2. No Content-Security-Policy
Start with a report-only CSP, then default-src 'self' and an explicit script-src.
Evidence: content-security-policy missing

3. No X-Content-Type-Options
Set X-Content-Type-Options: nosniff.
Evidence: x-content-type-options missing

4. No Referrer-Policy
Set Referrer-Policy: strict-origin-when-cross-origin.
Evidence: referrer-policy missing

Acceptance
- Check text, layout and the main action “Get started” at 1440×900 and 390×844.
- Preserve branding, authentication and business behavior. A screenshot does not prove broken interaction.
- Change only evidence-backed issues. Validate security headers against existing resources and authentication in report-only mode where supported.
- Compare before/after screenshots and run relevant functional tests. Do not claim untested behavior passed.
All token kits →