Skip to content

Feature/lighthouse ci budgets 530#621

Open
mijinummi wants to merge 2 commits into
MettaChain:mainfrom
mijinummi:feature/lighthouse-ci-budgets-530
Open

Feature/lighthouse ci budgets 530#621
mijinummi wants to merge 2 commits into
MettaChain:mainfrom
mijinummi:feature/lighthouse-ci-budgets-530

Conversation

@mijinummi

Copy link
Copy Markdown

📝 Pull Request Summary [Wave 200pts]

Description

This PR addresses Issue #530, introducing automated Lighthouse CI quality controls to enforce maximum thresholds on Largest Contentful Paint (LCP) and Cumulative Layout Shift (CLS).

Key Modifications

  • Lighthouse Contract Constraints: Configured assertions inside lighthouserc.js to block builds failing the 90%+ performance or core vitals requirements.
  • Continuous Integration Integration: Created .github/workflows/performance.yml to automatically execute audits on headless production code artifacts for incoming PRs.
  • Governance Tracking: Logged runtime metrics requirements and failure behavior explicitly within the main system workspace README.md.

Target Branch: main
Closes #530

@drips-wave

drips-wave Bot commented Jun 29, 2026

Copy link
Copy Markdown

@mijinummi Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

devops: add Lighthouse CI for LCP/CLS budgets

1 participant