Summary
The frontend has no performance baseline. There has been no Lighthouse audit to measure performance, accessibility, SEO, and best practices scores. For a financial application targeting emerging markets with potentially slower connections, performance matters significantly.
Motivation
Google Lighthouse provides actionable, quantified performance metrics. Poor Lighthouse scores (especially performance and accessibility) directly correlate with higher bounce rates and lower user trust. Running a baseline audit reveals the biggest optimization opportunities.
Proposed Work
Step 1: Baseline Audit
Run Lighthouse against the following pages (on testnet with mock data):
/ (landing page)/dashboard (SME dashboard)/invest (investor page)/invoice/[id] (invoice detail)
Record scores for: Performance, Accessibility, Best Practices, SEO.
Step 2: Fix Critical Issues
Based on typical Next.js app issues, expected fixes:
Performance:
Accessibility:
SEO:
Best Practices:
Step 3: CI Integration
Add a Lighthouse CI step that fails if performance score drops below 70:
- uses: treosh/lighthouse-ci-action@v10
with:
urls: http://localhost:3000
budgetPath: ./lighthouse-budget.jsonAcceptance Criteria
References
frontend/next.config.js — performance configuration.github/workflows/ci.yml — add Lighthouse CI
Summary
The frontend has no performance baseline. There has been no Lighthouse audit to measure performance, accessibility, SEO, and best practices scores. For a financial application targeting emerging markets with potentially slower connections, performance matters significantly.
Motivation
Google Lighthouse provides actionable, quantified performance metrics. Poor Lighthouse scores (especially performance and accessibility) directly correlate with higher bounce rates and lower user trust. Running a baseline audit reveals the biggest optimization opportunities.
Proposed Work
Step 1: Baseline Audit
Run Lighthouse against the following pages (on testnet with mock data):
/(landing page)/dashboard(SME dashboard)/invest(investor page)/invoice/[id](invoice detail)Record scores for: Performance, Accessibility, Best Practices, SEO.
Step 2: Fix Critical Issues
Based on typical Next.js app issues, expected fixes:
Performance:
next/imagefor all images (automatic WebP conversion, lazy loading)Accessibility:
langattribute to<html>tagSEO:
<meta name="description">to all pagesrobots.txtis present and correctly configuredBest Practices:
rel="noopener noreferrer"console.logstatements in production buildStep 3: CI Integration
Add a Lighthouse CI step that fails if performance score drops below 70:
Acceptance Criteria
docs/performance-baseline.mdReferences
frontend/next.config.js— performance configuration.github/workflows/ci.yml— add Lighthouse CI