Ship less.
Load faster.

Ulpfe finds the JavaScript your pages never use, then enforces a performance and energy budget in CI.

Start free See a sample audit
No runtime agent Framework agnostic CI native Runs on your build output
A dense field of pebbles at the water's edge

The weight you cannot see.

A page can look finished and still ship hundreds of kilobytes of code that never runs. Ulpfe traces each route back to the modules that actually execute, then shows you the gap.

  • Per-route, per-chunk attribution
  • Third-party cost separated from your own code
  • History for every branch, not just production

A budget that fails the build, not the user.

Set a ceiling per route. Ulpfe checks it on every pull request and blocks the ones that cross it. Exceptions are explicit, reviewed and time-boxed.

RouteBudgetHeadroom
/90 KB18 KB
/pricing110 KB24 KB
/dashboard140 KB4 KB over
# ulpfe.config.yml
budgets:
  default: 90kb
  routes:
    "/pricing": 110kb
    "/dashboard": 140kb
fail:
  on_regression: true
  allow_override: 7d

Performance is also an energy decision.

Every kilobyte is transferred, parsed and thrown away. Ulpfe translates route weight into an estimated energy cost so the trade-off is visible before it ships.

The model is documented and conservative. It is a planning signal, not a certification.

Try a route weight

weight220 KB
slow 4G1.4 s
vs budget100 KB over

Transfer estimated at 1.6 Mbps. Excludes latency and parse time.

Priced per project, not per pageview.

Open

Free

For solo projects and open source.

  • One project
  • Route budgets
  • Local reports
Start free

Team

Monthly

For product teams shipping weekly.

  • Unlimited projects
  • CI gates and history
  • Energy estimates
  • Slack reports
Start free

Enterprise

Custom

For regulated and self-hosted setups.

  • Self-hosted runner
  • Audit export
  • Policy review
Talk to us

Make the budget part of the pull request.

Connect a repository, set one route budget, and see the first report before lunch.

Start free