Skip to content

Add OhMyPerf to Open source tools#7

Open
hoainho wants to merge 1 commit into
pajaydev:masterfrom
hoainho:add-ohmyperf
Open

Add OhMyPerf to Open source tools#7
hoainho wants to merge 1 commit into
pajaydev:masterfrom
hoainho:add-ohmyperf

Conversation

@hoainho

@hoainho hoainho commented May 21, 2026

Copy link
Copy Markdown

Adds OhMyPerf to the Open source tools section — a real-Chromium Core Web Vitals measurement tool with a closed agent fix loop and statistical regression detection.

Why this list fits

OhMyPerf is purpose-built for the budgeting use case this awesome list covers:

  • Per-metric Mann-Whitney U regression detection (α=0.05) — solves the flake problem that fixed-threshold Lighthouse-CI budget gates have. verify_fix runs the candidate URL N times against a baseline and returns a structured per-metric verdict (improvement | neutral | regression) with p-values.
  • Honest about variance — every report ships with a trustScore that decomposes into sampleConfidence (is n big enough?) + effectConfidence (is the signal noisy?), plus a recommendedAction per metric. No more pretending 3-run measurements are precise.
  • Real-Chromium, real-hardware — measures what the user sees, not a synthetic CPU in a datacenter.

Distinct from existing entries

Existing OhMyPerf
Perfume.js (RUM field beacons) Lab-style real-Chromium measurement for CI / pre-deploy gating
Falco (WordPress-focused) Framework-agnostic, runs against any HTTP(S) URL
Bundle Size / Size Limit (build-time bundle weight) Runtime CWV (LCP/INP/CLS) on a real browser
Lighthouse-CI (synthetic CPU + datacenter network) Real machine, real network, real Chromium

What you get

  • @ohmyperf/cliohmyperf run <url>, ohmyperf diff baseline.json candidate.json
  • @ohmyperf/mcp-server — 16 tools so AI agents can measure, propose fixes, and verify
  • @ohmyperf/eslint-plugin — 7 CWV-linked ESLint rules at editor-save time
  • Live drag-drop viewer: https://hoainho.github.io/ohmyperf/viewer/

Status

  • Apache-2.0
  • v0.1.0 on npm under @ohmyperf scope; v0.2.0 pending publish
  • 387 tests, all green
  • Real-world validated against 10 production sites
  • Public repo: https://github.com/hoainho/ohmyperf

Thanks for maintaining this list — performance budgets are still under-tooled in 2026 and a curated list like this is how teams find the right primitives.

OhMyPerf is a real-Chromium CWV measurement tool that fits the
Open source tools section alongside Perfume.js (field-data monitoring)
and Falco (analysis + optimization).

Differentiation vs the existing entries:

- Perfume.js: lab-style field RUM, JS library — OhMyPerf is a
  full standalone tool with its own browser runner, CLI, MCP server,
  and shareable static viewer. Both have a place: Perfume for prod
  RUM beacons, OhMyPerf for CI / pre-deploy budget gating + agent
  fix loops.

- Falco: WordPress-focused performance analyzer — OhMyPerf is
  framework-agnostic, runs against any HTTP(S) URL, and reports
  ROI-ranked patch candidates with first-party/third-party tagging
  via 'originClass'.

For the 'Tools to measure Performance Budget' lane, the closed agent
fix loop is the specifically novel piece: 'verify_fix' runs the
candidate URL N times, applies a Mann-Whitney U significance test at
alpha=0.05, and returns a structured per-metric verdict — solving the
flake problem that fixed-threshold Lighthouse-CI budget gates have.

Apache-2.0, public repo (https://github.com/hoainho/ohmyperf),
v0.1.0 on npm at @ohmyperf scope, v0.2.0 pending publish.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant