You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 12, 2023. It is now read-only.
A lighthouse user sent me a use case and I thought it may make sense on the lightcrawler side:
I have a clean WP site, I install a new theme, and we want to run a set of audits across the pages: crawl the pages, record LH reports for each page, take final screenshots of each page, and spit out a summary report with links to individual pages.
Is that UX something you'd consider in-scope for lightcrawler? It seems to have a little different approach as far as reporting (HTML vs stdout) so curious what you think.
The text was updated successfully, but these errors were encountered:
A lighthouse user sent me a use case and I thought it may make sense on the lightcrawler side:
Is that UX something you'd consider in-scope for lightcrawler? It seems to have a little different approach as far as reporting (HTML vs stdout) so curious what you think.
The text was updated successfully, but these errors were encountered: