Weave Code
Laravel Google Lighthouse Laravel Package
logiek/laravel-google-lighthouse
Run Google Lighthouse audits directly from your Laravel app. Generate performance, accessibility, SEO, and best-practices reports programmatically, with a clean API for automating audits and storing results.
logiek/laravel-google-lighthouse brings Google Lighthouse auditing into Laravel. It provides a simple integration for running performance, accessibility, best-practices, and SEO audits against your application’s URLs, making it easy to validate page quality from your Laravel workflow.
- Run Lighthouse audits programmatically or via Artisan.
- Configure target URLs and audit categories.
- Access structured audit results and scores.
- Publishable configuration for project-specific setup.
- Lightweight Laravel service provider integration.
Frequently asked questions about Laravel Google Lighthouse
- How do I install logiek/laravel-google-lighthouse in a Laravel app?
- Install it with Composer using the package name logiek/laravel-google-lighthouse. Laravel package discovery should register the service provider if the package follows standard conventions, but confirm any publish or configuration steps in the repository README. After installation, run your application tests and verify the Composer constraints for your Laravel and PHP versions.
- What Laravel versions does logiek/laravel-google-lighthouse support?
- The 1.2.0 release adds support for Laravel 9 and Laravel 10. The available release information does not claim support for Laravel 11 or 12, so verify Composer constraints before adopting it on newer versions. Applications on Laravel 8 or earlier should remain on a previously compatible release or upgrade the host application first.
- How do I run a Google Lighthouse audit from Laravel with this package?
- The package wraps Google Lighthouse so you can trigger audits from Laravel and read the resulting scores programmatically. Exact method names and options should be taken from the repository README because the provided release notes do not document the API. Start with a single URL in staging, then expand to scheduled or dashboard-driven audits.
- What scores can I retrieve from a Lighthouse audit with this package?
- It exposes Google Lighthouse audit results for performance, accessibility, SEO, and best practices so you can compare page quality or track changes over time. The package is intended for programmatic use, such as dashboards, deployment comparisons, and CI checks. Confirm the exact response structure in the package documentation before building reporting around it.
- Can I use this package to monitor page quality after deployments?
- Yes, it is suited to monitoring page quality and comparing deployments because it returns Lighthouse scores programmatically. A common pattern is to run audits after a deployment and store or compare the scores against a baseline. Keep audits isolated from production traffic where possible and account for Lighthouse runtime and browser dependencies.
- Does laravel-google-lighthouse work in CI pipelines?
- It can support CI checks because Lighthouse audits can be run and their scores consumed programmatically. You will need a CI environment capable of running Google Lighthouse, which typically means a headless browser setup. Also verify the package Composer constraints and test coverage for your Laravel version before blocking merges on audit thresholds.
- How do I configure logiek/laravel-google-lighthouse after installation?
- Configuration details are not included in the provided release notes, so check the repository README for publishing config, service-provider registration, and any package-specific options. Follow standard Laravel package steps: install via Composer, publish any config if documented, and clear cached config after changes. Run a smoke-test audit in staging before relying on the configuration in production.
- Is logiek/laravel-google-lighthouse compatible with Laravel 11?
- The 1.2.0 release explicitly adds Laravel 9 and 10 support and does not claim Laravel 11 compatibility. Treat Laravel 11 support as unconfirmed until the package Composer constraints and CI matrix show it. If you are on Laravel 11, test in a branch or look for a newer release before adopting.
- What are alternatives to using this Laravel Google Lighthouse wrapper?
- Alternatives include calling the Google Lighthouse CLI or Node API directly, using a hosted Lighthouse or page-speed auditing service, or choosing another Laravel wrapper that matches your support matrix. This package is a reasonable fit when you want Laravel-native programmatic access to Lighthouse scores. Compare maintenance cadence, Laravel version support, and CI coverage before switching.
- How is logiek/laravel-google-lighthouse maintained and tested for Laravel 9 and 10?
- The available release information shows a 1.2.0 compatibility expansion for Laravel 9 and 10, but it does not document the CI matrix, PHP versions, or support SLA. Review the repository release history, issue triage, and test configuration before treating it as a safe default. For production use, pin the package version and run your application test suite during upgrades.
Weaver
How can I help you explore Laravel packages today?