Detects web performance regressions by comparing page metrics against captured baselines.
npx skills add https://github.com/no-session/pstack --skill benchmark-no-session
Please help me install this Agent Skill. Skill: benchmark Source: https://github.com/no-session/pstack/tree/main/benchmark Command: npx skills add https://github.com/no-session/pstack --skill benchmark-no-session
High-intent search queries and answers about installing and using this skill.
Capture a baseline with /benchmark <url> --baseline on the main branch, then run /benchmark <url> on your feature branch. The skill compares TTFB, FCP, LCP, bundle sizes, and request counts, flagging regressions over 50% or 500ms.
The skill uses a headless browse daemon to load pages and reads performance.getEntriesByType data via JavaScript evaluation. It extracts FCP, LCP, TTFB, DOM Interactive, and full load times directly from the browser's Performance API.
Yes, use /benchmark --diff to benchmark only pages affected by the current branch. It runs git diff against the base branch to determine which files changed and scopes the audit accordingly.
Timing increases over 50% or 500ms absolute count as regressions, while over 20% is a warning. Bundle size growth over 25% is a regression, and request count growth over 30% triggers a warning.
Without a baseline, the skill can only report absolute numbers, which are meaningless across different page types. A 2000ms load is fine for a dashboard but terrible for a landing page, so comparison against your own baseline is essential.
ollieb89Run Lighthouse audits and collect runtime metrics via Python script.
JeremyDev87Profile CPU, memory, and I/O to prioritize and prevent performance regressions.
InverterNetworkNavigate web pages and interact with DOM elements for exploratory QA testing.
legioncodeincConfigures Lighthouse CI and PageSpeed Insights audits with performance budgets and lab-versus-field reconciliation.
