WebPerf Snippets
WebPerf Snippets packages reusable browser performance measurements as snippets, a CLI, MCP and agent skills. It is useful when a team wants explicit loading and interaction diagnostics plus CI budgets. We ran the published npm CLI 1.13.0 with Playwright 1.65.0 and Chromium 158.0.8127.18 on macOS 26.6.2, Node.js 26.3.0 ARM64. Selected package files matched release commit dc3a919ac50708d6d805b0b0f4fbd38cbd88a7f7. The page, delays and interactions were artificial and loopback-only.
The real browser measured three-run median TTFB of 3ms normally and 906ms with a 900ms response delay; recovery measured 7ms. The 500ms budget passed, failed and passed respectively, and baseline comparison marked the delayed run as a regression. A stable-page Core Web Vitals workflow measured LCP 20ms and passed its budgets. Inserting a late banner raised CLS from 0 to 0.2956; a handler busy for 260ms produced synthetic clicked INP of 304ms. Both exceeded their selected budgets. Without input, INP remained unmeasured and its budget failed rather than treating missing data as zero.
An incompatible CLS budget on a TTFB-only run returned exit 2 with an explanation. The real stdio MCP server listed nine tools and executed a TTFB measurement. These are selected local controls, not field-user metrics, ranking benefits or a cross-device performance benchmark. The three-run comparison explicitly lacked the five observations per side required for its statistical comparison. No model, CrUX, report upload, authenticated page, mobile hardware or other browser was tested. Installing the npm package also requires an independently installed Chromium browser.
Read the full review, verification scope and sources →Features
Why choose it
Trade-offs
Maintenance check
- Last commit
- 2026-11-07
- Commits, last 90 days
- 100+
- Releases, last 90 days
- 24
- Latest release
- v2.6.1 (2026-11-07)
- Open issues
- 4
- Recent issues with at least one comment
- 0/1
Oldest week on the left; the latest four weeks are orange. Source: GitHub commit activity.
Status rule: archived on GitHub = Archived; last commit within 90 days = Active; 91 to 365 days = Slowing; older = Stale. All figures come from the GitHub API on the date shown.
Most discussed open issues
- #75 Add expected output examples to all snippets4 comments · 2026-05-01
- #389 [Bug]: LCP Trail drops candidates whose element was removed from the DOM0 comments · 2026-11-04
- #43 [Markdown] An option to highlight a "Note" and "Warning" using blockquote0 comments · 2023-11-24
Issue titles are quoted from GitHub. Open the link to check whether a problem still applies to the version you use.
Who it fits
- You need specific browser metrics and CI budgets on representative pages.
- You can retain baselines and control browser, device and interaction conditions.
- You require field-user evidence from these local tests alone.
- You expect a performance tool to certify Google ranking improvements.
Compatibility
Quick start
Use cases
Alternatives
Comments
No comments yet. Be the first!