
I built a CLI that catches Lighthouse regressions before they ship
Google Lighthouse is great for one-off audits. But if you fix your LCP on Tuesday and ship a bundle regression on Friday — nobody notices until Search Console emails you three weeks later. Lighthouse tells you how fast your site is today. kanmi tells you when it gets slower. npm install -g @knfrmd/kanmi kanmi audit https://your-site.com Kanmi Performance Audit https://your-site.com mobile · Slow 4G, 4x CPU · LH 12.0.0 · 14.2s ───────────────────────────────────────────── Performance 72 Accessibility 95 Best Practices 100 SEO 91 Lab Metrics ───────────────────────────────────────────── LCP 4,200ms NEEDS IMPROVEMENT TBT 380ms NEEDS IMPROVEMENT CLS 0.003 GOOD FCP 1,800ms GOOD Top Issues ───────────────────────────────────────────── * Reduce unused JavaScript (~1.2s savings) * Eliminate render-blocking resources (~800ms savings) One command. Scores, lab metrics, top issues. What it does kanmi audit <url> — run Lighthouse, print results kanmi monitor <url> — run 3 audits (median), save to l
Continue reading on Dev.to Webdev
Opens in a new tab


