Track compressed Webpack asset sizes over time.
-
Updated
Jun 15, 2026 - JavaScript
Track compressed Webpack asset sizes over time.
Audit URLs using Lighthouse and test performance with Lighthouse CI.
⚡️Articles, Websites, Tools and Case Studies to implement performance budget to a website. (PR 's welcomed)
Run Lighthouse tests in Pull Requests for multiple URLs with custom budgets
A Github bot for size-plugin
performance-budgets gives you a simple way to check and stay on top of performance
Webpack plugin to set budget on individual file
Prevent bundle bloat before it ships. Track PR size diffs with instant feedback and enforce budgets-no external services
Example performance budget for Next.js applications
Assert a Lighthouse / PageSpeed Insights report against a performance budget. Zero-dep TS library + CLI for CI.
Capped GitHub Actions template for hosted Lighthouse release regression checks
CLI and library that scripts a real scroll in headless Chrome and reports dropped frames, long tasks, forced reflows and non-compositor animations against a performance budget.
Monitor the total size of your production JavaScript files to maintain fast performance.
Drop-in Lighthouse CI performance budget and GitHub Actions workflow for fast Astro marketing sites. Real lighthouserc.json with Core Web Vitals and resource-size budgets, desktop and mobile configs, and a ready-to-use lighthouse.yml. Fail the PR before a regression reaches a visitor.
GitHub Action + zero-dependency Node CLI that measures your static-site build on every pull request and posts a sticky PR comment diffing build time and output size (total, gzipped, per-type, largest assets) against the base branch — with rollback-friendly build artifacts and an optional preview URL.
A compact isometric Three.js action slice: defend the moonshard across three escalating waves, read telegraphs, chain mooncuts, dash through committed strikes. Its real weight is the accessibility and performance discipline - reduced-motion paths, gamepad remapping, screen-reader status, and a build that fails above a 12 KiB initial-JS budget.
Budget-driven Lighthouse audits with Markdown and JSON reporting.
See which Lighthouse metric is actually costing you the points. Exact log-normal scoring curve, weighted contributions, and points-to-gain per metric.
CI gate that checks Core Web Vitals against a performance budget and fails the build on regressions, diffing against a saved baseline. Findings link to explainers on frontend-performance.com.
The main shelby and brad site
Add a description, image, and links to the performance-budget topic page so that developers can more easily learn about it.
To associate your repository with the performance-budget topic, visit your repo's landing page and select "manage topics."