Lighthouse Stack Packs

Lighthouse provides developers with guidance to improve their site by auditing for performance, accessibility and other best practices.

Many developers today use different technologies (backend/CMS/JavaScript frameworks) to build their web pages. Instead of only surfacing general recommendations, what if Lighthouse could also provide more relevant and actionable advice depending on the tools used?

You can see a prototype of this feature with Lighthouse Viewer.

Contributing

This is still under early development, but we would like to hear any suggestions from community members in the meantime. WordPress is the first ecosystem we would like to include before rolling this out for other stacks.

• If you are an active member of the WordPress community, feel free to provide suggestions for different audit messages to this spreadsheet.
• Alternatively, feel free to open PRs and provide suggestions for different audit messages in wordpress/audits.json.
  • For each audit, the secondaryDescription attribute can be used to include (or modify) the WordPress specific messages.
• If you have any feedback on the design or anything else, please open an issue!

Before contributing in any way, make sure to also read CONTRIBUTING.md.

Testing changes locally

If you would like to test your changes with Lighthouse Viewer using this prototype, you can do the following:

• In Lighthouse, create a branch off of the one used to set up this rough prototype.
• For any audit that you would like to update, open its respective file (the file name always matches the audit id)
• Add a secondaryDescription to the meta static method
• Run yarn update:sample-json to update the i18n strings
• Build and run Lighthouse CLI to view the report