Skip to content
lube

Web performance

LighthouseCore metricsBudgets

Keep the performance check after the build ends.

Ingest Lighthouse runs from CI or local, grade them against per-metric budgets, and keep the score, the metrics, and the artifact beside the commit that produced them.

92

Perf

  • Budget90
  • Largest contentful paint1.8s
  • Cumulative layout shift0.02
  • Total blocking time120ms
Lighthouse against your budget

Its place in the loop

Performance evidence lives in the Reliability stage.

One connected loop, held on the stage this capability serves. The other stages stay as context so you can see what feeds in and what comes next.

BD
Discovery
Feedback
Product
Engineering
Release
Reliability
Evidence

Stage inventory

Reliability

Know whether it held.

Web performance

Review Lighthouse report evidence against configured targets.

Available now

Test intelligence

Investigate test outcomes and flakiness evidence across runs.

Available now

Coming later reflects product vision, not a delivery commitment.

Every vital, against its budget

Watch each metric fill toward its value, and the one that fails flag itself.

Each core web vital fills to how much of its budget it spends. A metric over budget flags red and pulses; the passing ones settle and stay still.

LCP

1.8s/ 2.5s

largest contentful paint

CLS

0.02/ 0.10

cumulative layout shift

INP

240ms/ 200ms

interaction to next paint

TBT

120ms/ 200ms

total blocking time

Core web vitals vs budget

A score is only the headline

Everything under the number.

Resource waterfall

See what loaded, and in what order.

Requests reveal staggered left to right in load order, the same way a network panel draws them, so a render-blocking script is easy to spot.

load orderrender-blockingby type

resource waterfall · load order

  • documenthtml
  • app.cssstylesheet
  • main.jsscript
  • hero.webpimage
  • inter.woff2font
0 msstart of load1.8 s
Resource load waterfall

Categories

Five categories, not just performance.

Every run records accessibility, best practices, SEO, and PWA alongside performance, each scored 0 to 100.

accessibilitybest practicesseopwa
  • Performance92
  • Accessibility98
  • Best practices96
  • SEO100
Category scores

Budgets

Grade the run, don't just read it.

Set a threshold per metric with a comparison operator and a severity. Each run rolls up to one pass, warn, or fail verdict.

lt / lte / gt / gtewarn / failrun verdict

88

Perf

  • Largest contentful paint2.1s
  • Cumulative layout shift0.04
  • Total blocking time180ms
  • Interaction to next paint160ms
Run graded against your budget

An honest limit

Web performance is Lighthouse-based. It ingests lab runs pushed from CI or local, not real-user monitoring, full APM, or distributed tracing, and it does not crawl your URLs on its own.

Connected context

See what performance sits beside.

Keep Lighthouse evidence beside the targets you set.

Start free

Ingest a report and start tracking.