Caliper

Measures what your AI interface makes users wait for.

Lighthouse for AI features

See where your AI feature's wait goes — and where to look first.

Caliper times every step from click to first word, then points you to the step furthest over its limit. Every tip is backed by a number it measured.

Click → first word · Quill, warm run
926 ms OVER585 ms OVER
  • click → request sent3 ms within its 200 ms limit
  • browser: response headers received926 ms over its 600 ms limit
  • headers → first paint585 ms over its 100 ms limit
Real numbers from a Caliper report of Quill, Nov 14, 2026. See the report →

The problem

Users click, then stare at a blank box.

Is it the browser, your server, the model call, or the size of the prompt? From the outside, nobody can tell. Caliper times every step in the browser and, with its server half, inside your server.

What you get

One report. Four ways in.

How it works

Three steps, one command.

  1. 1

    Opens and clicks

    Opens your page in Chromium and clicks your AI button, or types into your chat box.

  2. 2

    Times the wait

    From the click to the first word on screen, on the page's own clock.

  3. 3

    Shows where

    Splits the wait into steps, flags any step over its limit, and writes one HTML report.

Use it on your own app

Start with the browser. Add the server when you want it.

no token

Browser half

Point the CLI at any page you can open. Pages behind a login: save a session first with caliper login.

your own token

Server half

Add caliper-timings to your app and set your own CALIPER_TOKEN. Adds the Request Map and your server's timings.

npm i -g caliper-ai && npx playwright@1.64.1 install chromium

Needs Node.js 20 or newer. Full setup in the README →

What it doesn't do

  • It sees timings, not your code. Hints are common causes, not a diagnosis.
  • It never records your prompt text, only sizes.
  • It doesn't detect prompt injection.
  • Chromium and HTTP only. Replies over a WebSocket aren't timed.

What's next · not built yet

Where Caliper goes next.

  • Not built yet

    3D replay

    Watch a request travel through your app.

  • Not built yet

    Firefox + Safari

    Today Caliper needs CDP, which only Chromium has.

  • Not built yet

    Hosted Caliper

    Run it without installing.

  • Not built yet

    History

    See if you're getting faster or slower over time.

  • Not built yet

    More backends

    Server timings for Go, PHP and Java.

  • Not built yet

    WebSocket apps

    Time replies that arrive over a WebSocket, not just HTTP.

Star on GitHub to follow along →

See where your AI feature's wait goes.