Filament Spatie Lighthouse Laravel Package

Product Decisions This Supports

• Website quality monitoring as an in-product capability: This package turns Google Lighthouse audits into a first-class Filament admin feature — dashboards, history, thresholds, and alerts. It supports decisions like "do we build an internal SEO/performance monitoring tool, or buy/assemble one from open-source building blocks?"
• Build vs. buy vs. assemble: The package wraps Spatie's Lighthouse wrapper in a Filament UI with storage, scheduling, notifications, and an opt-in REST API. It is a strong candidate to assemble rather than build from scratch, materially reducing time-to-value for internal QA/DevOps tooling.
• Roadmap fit for content/marketing/SEO ops: Per-URL audit history, scheduled audits, and email/Slack notifications directly support recurring workflows (e.g., pre-launch checks, post-deploy verification, ongoing SEO hygiene) that product and marketing stakeholders often request.
• Deployment architecture decisions: Pluggable ResultStore (database vs. cache vs. custom), opt-in filesystem storage for raw results, and queue-backed audits give the team real choices about persistence, scaling, and infrastructure footprint — relevant for both small stateless deployments and larger multi-tenant installs.
• Observability and alerting strategy: AuditStartingEvent/AuditEndedEvent/AuditFailedEvent plus notification channels let PMs define SLAs around site quality (e.g., "alert on failed audits or score regressions") without bespoke engineering.
• Governance and access control: Opt-in, token-protected REST endpoints plus bulk export (CSV/JSON) support reporting to stakeholders, audit trails, and integration with BI or external dashboards.
• Internationalization and UX polish: Full i18n and metric cards (FCP, LCP, TBT, TTI, SI, CLS) mean the tool can be shipped to non-English teams and used by non-engineers without translation work.

When to Consider This Package

Adopt when:

• You are on Laravel + Filament and want Lighthouse results surfaced inside an existing admin panel without custom UI work.
• You need scheduled, repeatable audits with history, thresholds, and notifications — not just one-off CLI runs.
• You want low operational overhead: choose CacheResultStore for stateless/small deployments, DatabaseResultStore for durable history with pruning, and filesystem storage for large raw JSON.
• You need multiple integration surfaces: Artisan commands, events, an opt-in REST API, and bulk exports.
• You value extensibility: ResultStore interface, configurable headers/user-agent, throttling, and form factor cover most real-world audit scenarios.
• You need stakeholder-friendly reporting (color-coded scores, HTML report download, CSV/JSON export) for marketing, SEO, or leadership.

Look elsewhere or proceed cautiously when:

• You are not using Filament — much of the value (the page, UI actions, notifications) is UI-bound; a plain Spatie Lighthouse wrapper may suffice.
• You need enterprise-grade SLA, vendor support, or compliance guarantees — this is a community package (v1.0.0), so you own the support burden.
• You require multi-site / multi-tenant isolation, RBAC granularity, or SSO beyond what Filament policies provide out of the box; plan for customization.
• You need competitor benchmarking or deep performance analytics (trend analysis, regression attribution) — this is a monitoring tool, not an APM.
• You cannot run headless Chrome / Node in your environment (Lighthouse dependency) or cannot tolerate the resource cost of audits.
• You want a fully managed SaaS with uptime guarantees rather than self-hosted tooling.

How to Pitch It (Stakeholders)

For executives: This package gives us an in-panel website quality dashboard — performance, accessibility, best practices, and SEO — with scheduled audits, history, and alerts to Slack/email. It replaces ad-hoc Lighthouse runs and spreadsheet tracking with a repeatable, auditable process, at effectively zero licensing cost and a small integration effort (a Composer install, migrations, and config). It reduces the risk of shipping slow or inaccessible pages and gives marketing and SEO a shared source of truth.

For engineering: It is a thin, well-scoped Filament layer over spatie/lighthouse, with sensible extension points: a ResultStore interface (database, cache, or custom), filesystem offload for raw results, queue-backed audits, configurable headers/throttling, and lifecycle events for custom listeners. It ships Artisan commands (lighthouse:audit, lighthouse:schedule, lighthouse:list), opt-in token-protected REST endpoints, and configurable thresholds — so it fits into existing CI/cron/alerting patterns without forcing architectural changes. It is v1.0.0 and community-maintained, so we should treat it as a dependency we own: pin the version, review upgrade notes, and budget a small amount of maintenance.

Recommendation: Adopt for internal quality monitoring where Laravel + Filament are already in use; pilot on one or two sites, validate storage and scheduling choices, and revisit for broader rollout after a quarter of real-world use.