Lighthouse + Core Web Vitals optimization (95+ all axes)

[truthixify]

Tier: M (2-4 days) Type: perf

Context

Site is small but Core Web Vitals never measured. Google Fonts CDN is blocking, no font subsetting, no critical CSS inlining. Set explicit budgets and hit them.

Scope

Baseline + optimize:

• Run Lighthouse + PageSpeed Insights, capture in docs/PERF.md
• Target: 95+ on all four axes (Perf / A11y / Best Practices / SEO), mobile + desktop
• Font subsetting (only used weights of Space Grotesk, Inter, JetBrains Mono)
• font-display: swap, self-host fonts, preload critical files
• Image optimization (logo, og-image)
• Inline critical CSS for above-the-fold
• Tree-shake Tailwind
• CI Lighthouse job posting score comments on PRs

Acceptance criteria

• docs/PERF.md baseline + post-fix
• All four axes 95+ on mobile
• CI Lighthouse job in place
• No regression in CLS/LCP/INP

Files to start with

• index.html, src/index.css
• vite.config.ts

[abbys-code-hub]

@abbys-code-hub has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I would like to work on this issue.
Performance is measurable and this has a clear target (95+ on all axes). The diagnostics are specific, the optimizations follow naturally, and setting up CI prevents future regressions. This is infrastructure work that directly improves user experience.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @abbys-code-hub to this issue.

[truthixify]

@abbys-code-hub Assigned. Welcome to wave 6 (or welcome back).

Quick expectations:

1. Branch from develop (default branch now, GitHub auto-picks).
2. Open a draft PR within ~3 days so we see direction.
3. Update at least every 5 days. Silence costs the assignment.
4. Acceptance criteria in the issue body are the merge bar.

Ask on the issue if anything is ambiguous before building.

[drips-wave]

Congratulations, @abbys-code-hub! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @abbys-code-hub: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[abbys-code-hub]

@abbys-code-hub Assigned. Welcome to wave 6 (or welcome back).

Quick expectations:

1. Branch from `develop` (default branch now, GitHub auto-picks).

2. Open a draft PR within ~3 days so we see direction.

3. Update at least every 5 days. Silence costs the assignment.

4. Acceptance criteria in the issue body are the merge bar.

Ask on the issue if anything is ambiguous before building.

Done. Kindly review. Thanks

[drips-wave]

This issue has been completed by @abbys-code-hub as part of the Stellar Wave Program's 6th Wave 🥳

😎 @abbys-code-hub: You earned 100 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.