Modern QA2026Common Pitfalls — tiles
Log inJoin
44 / 95 · 05 Performance & Chaos Engineering · Lighthouse CI: Enforcing Frontend Performance Budgets← prev⊞ allnext →☰ Read as one page

7.8Common Pitfalls

  1. Flaky results from CI environments. CI runners have variable performance. Use numberOfRuns: 3 (or 5) and assert on the median, not a single run.

  2. Budgets too tight. Start with achievable budgets and tighten them over time. A budget that fails on every PR gets disabled, defeating the purpose.

  3. Ignoring mobile. Default Lighthouse settings simulate mobile. Do not change throttling to fast desktop to make numbers look good. Mobile is where most users are.

  4. Not testing authenticated pages. Lighthouse CI supports puppeteerScript for login flows. Do not skip your most important pages just because they require authentication.

  5. Budget drift. Review and update budgets quarterly. What was acceptable last year may not meet current user expectations or competitive standards.