performance

Real numbers, on the pages your users actually see.

Most speed tools only measure your public homepage. CodeReviewer replays your signed-in flows under throttling, measures Core Web Vitals on the real pages, and alerts you the moment a change blows a budget.

Start free trial Talk to sales

performance · /dashboard

Budgets held on the real pages.

LCP1.2s
CLS0.02
INP180ms

Median of three throttled runs, signed in, with a budget alert the moment a change regresses it.

LCP · CLS · INPCore Web Vitals on signed-in pages

Budgetsper page, with regression alerts

the problem

Performance regressions ship silently.

Speed checks usually cover the marketing site, not the dashboard your customers live in.

Nobody notices a slow page until a customer complains. By then it's weeks after the change that caused it.

One-off audits give a score, not a trend, so there's no way to tell whether things are getting worse.

how it works

From trigger to result.

Reuse your test suites

Performance runs ride the signed-in flows you've already authored.

Measure under throttling

Each page is timed across multiple throttled runs, plus a Lighthouse audit.

Set budgets

Define per-page limits for LCP, CLS and INP.

Get alerted

Scheduled runs track the trend and flag a regression as soon as it lands.

capabilities

What you get.

Authenticated pages

Measure the dashboard, the checkout, the settings screens. The pages behind the login are the ones that matter most.

Core Web Vitals

LCP, CLS and INP, measured as the median of throttled runs so one noisy run doesn't mislead you.

Lighthouse audits

A full audit alongside the timings, with the specific opportunities to improve.

Per-page budgets

Set limits page by page and get alerted the moment a change breaks one.

Trends and schedules

Run on a schedule or on demand and watch each page's numbers over time.

Free to re-run

Performance runs replay your existing suites and don't use AI, so you can run them as often as you like.

Why medians and throttling

A single page-load measurement is noisy: network jitter, a cold cache or a background task can swing the number either way. CodeReviewer times each page across several runs under consistent throttling and reports the median, so the number you see reflects the page, not the moment. A Lighthouse audit alongside it tells you what to change.

Catch it at the change, not the complaint

Performance usually degrades one small change at a time. With budgets per page and runs on a schedule, CodeReviewer tells you which page slowed down and roughly when. The change that caused it is still fresh in someone’s mind.

faq

Questions, answered.

Does performance testing use our AI allowance?

No. Performance runs replay suites you've already authored, so they don't use AI and can run as often as you like.

Why measure behind the login?

That's where your customers spend their time. Public-page scores say little about how fast your product feels to the people paying for it.

How do budget alerts work?

Set a limit per page for each metric. When a run goes over, CodeReviewer notifies your team in the app.

Do you support load or stress testing?

Load and stress testing is on the roadmap. Today, performance testing focuses on real-user page speed.

Give every PR the review it deserves.

Start your 15-day free trial. We onboard a few teams every week.