pulse_
home
// quick start

Get Pulse running in minutes

Pick how you want to capture data, follow the checklist, and your first session will appear in the dashboard. Progress is saved in this browser.

What you'll unlock

  • Replayable session timeline

    Scrub through APIs, WS frames, long tasks and vitals on one cursor.

  • Problem APIs & Channels

    Click an offender to jump the timeline and open a ±2.5s context window.

  • Hardware Impact panel

    Separate slow code from slow devices, with coverage diagnostics.

  • Root Cause & Compare

    Diff sessions or correlate regressions to deploys / device class / network.

Onboarding checklist

0/5 complete · saved locally

Connect your project

Paste your project's public key (from the dashboard URL or project settings). We'll verify ownership and send a test beacon to confirm ingest is reachable.

Sign in to verify and save progress across devices.

Share setup status

Generate a read-only link or PNG of your checklist + diagnostics — handy for support tickets.

SDK install guide

  1. 1. Copy your project ID

    From the dashboard, open your project — the ID is in the URL.

  2. 2. Add the snippet to your site
    <script
  src="https://site-speed-sprite.lovable.app/sdk.js"
  data-project-id="YOUR_PROJECT_ID"
  defer
></script>
  3. 3. Deploy & visit a page

    The SDK auto-captures Web Vitals after page load and posts them to /api/public/ingest.

Create your first session

Once the SDK is live, open the dashboard and watch the Sessions list. New sessions appear within a few seconds. Look for:

  • A row with your browser/OS in the Sessions table
  • Populated vitals (LCP, FCP, TTFB)
  • A non-empty device object on the session detail page

How a session maps to results

A single page-load produces a beacon that fans out into three views in your dashboard. Click a row below to see the mapping.

From the sample beacon below, Pulse extracts each Core Web Vital and grades it:

{ "lcp": 2100, "fcp": 900, "cls": 0.04, "inp": 180, "ttfb": 220 }

LCP 2.1s → good. INP 180ms → needs work. The dashboard colours each card accordingly.

Troubleshooting

Need definitions? See the Glossary · Learn the architecture in the Introduction.