> ## Documentation Index
> Fetch the complete documentation index at: https://patterns.heurilens.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Quickstart

> Start measuring UX on real products in minutes — no setup required.

## Get started with Heurilens in minutes

Heurilens is not a design tool or a checklist.
It analyzes **real interfaces** and surfaces **measurable UX patterns** based on user behavior signals.

This quickstart shows how to go from **zero → first UX insight** in minutes.

## Step 1 — Create your Heurilens account

<Card title="Create a free account" icon="user-plus" href="https://heurilens.com/auth/signup">
  Sign up to start analyzing real interfaces and UX patterns.
</Card>

<Note>
  No installation, no plugins, no setup required.
</Note>

## Step 2 — Start your first analysis

<AccordionGroup>
  <Accordion title="Enter a URL" icon="link">
    Paste the URL of any live website or product page you want to analyze.

    This can be:

    * a landing page
    * a marketing site
    * a SaaS dashboard
    * a checkout or form flow
  </Accordion>

  <Accordion title="Run Quick Scan" icon="bolt">
    Heurilens runs an instant scan to detect:

    * core UX signals
    * early friction points
    * visibility and hierarchy issues

    This gives you a fast, high-level signal before deeper analysis.
  </Accordion>

  <Accordion title="Review detected patterns" icon="eye">
    Instead of generic feedback, results are grouped into **UX patterns** such as:

    * Visual Hierarchy Failure
    * Consistency Breakdown
    * Cognitive Load Spikes

    Each pattern is tied to observable product signals.
  </Accordion>
</AccordionGroup>

## Step 3 — Inspect signals, not opinions

<AccordionGroup>
  <Accordion title="User behavior signals" icon="users">
    Heurilens highlights behavior-level indicators like:

    * hesitation
    * misaligned clicks
    * delayed actions
    * unclear intent
  </Accordion>

  <Accordion title="Product-level signals" icon="chart-line">
    You’ll see signals such as:

    * time to first meaningful interaction
    * CTA dominance issues
    * content density imbalance
    * structural inconsistencies
  </Accordion>

  <Accordion title="Actionable outputs" icon="code">
    Each detected pattern includes:

    * a clear explanation
    * impact level
    * example fixes
    * optional code snippets (CSS / structure)
  </Accordion>
</AccordionGroup>