Add Google PageSpeed Insights as an objective internal audit signal. The system should run mobile and desktop checks when possible, store raw results internally, and expose only plain-language implications to the later LLM/text pipeline rather than customer-facing scores.
Acceptance Criteria
#1 PageSpeed API runs for mobile and desktop strategies for qualified website leads
#2 Raw PageSpeed/Lighthouse response data is stored internally in Convex
#3 Key metrics are normalized for downstream analysis without exposing scores on customer audit pages
#4 Failures, quota errors, and unavailable pages are recorded without failing the entire audit pipeline
#5 Generated audit inputs translate technical signals into customer-impact language for later text generation
Implementation Plan
Add PageSpeed API client using environment/Convex secrets.
Run mobile and desktop analysis for the lead domain or final URL.
Normalize key findings such as load speed, mobile/desktop gap, SEO, accessibility, and best-practice hints.
Store raw and normalized results in Convex.
Add error handling and dashboard-visible status for quota, timeout, and API failures.
