Reading through wordpress/audits.json, I stumbled upon this item:
|
{ |
|
"id": "uses-text-compression", |
|
"title": "Enable text compression", |
|
"description": "Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. [Learn more](https://developers.google.com/web/tools/lighthouse/audits/text-compression).", |
|
"secondaryDescription": "You can enable this in your web server configuration." |
|
}, |
This is applicable not only for WordPress, but for any PHP framework being used (or server-side language for what it's worth).
Would it make sense to create some sort of hierarchy for audits messages, and output the merged advices? (i.e php/audits.json would contain that item, and wordpress/audits.json would include it)
That could also make Lighthouse give some accurate recommendations even when the framework is not detected, or only partially matched.
Reading through
wordpress/audits.json, I stumbled upon this item:lighthouse-stack-packs/wordpress/audits.json
Lines 68 to 73 in 7821d37
This is applicable not only for WordPress, but for any PHP framework being used (or server-side language for what it's worth).
Would it make sense to create some sort of hierarchy for audits messages, and output the merged advices? (i.e
php/audits.jsonwould contain that item, andwordpress/audits.jsonwould include it)That could also make Lighthouse give some accurate recommendations even when the framework is not detected, or only partially matched.