AMP Stackpack: Incorrect advice to run AMP Optimizer on AMP pages which are already optimized

[westonruter]

When running Lighthouse on an AMP page being served from the Cache, which is already serving Optimized AMP, the AMP stackpack is nevertheless suggesting to use the AMP Optimizer:

So this is not good advice because running the AMP Optimizer will have no effect since it is already optimized.

This stackpack suggestion for AMP should not be offered when the html element has the transformed attribute present.

Provide the steps to reproduce

1. Run LH performance audit on https://elsoberano-org.cdn.ampproject.org/c/s/elsoberano.org/constitucion/denuncian-que-walmart-esta-pidiendo-mas-represion-para-proteger-sus-ganancias/

This is the optimized AMP Cache version of https://elsoberano.org/constitucion/denuncian-que-walmart-esta-pidiendo-mas-represion-para-proteger-sus-ganancias/

What is the current behavior?

On an optimized AMP page, Lighthouse is advising: “Use tools such as AMP Optimizer to server-side render AMP layouts.”

What is the expected behavior?

No such advice should be offered.

Environment Information

• Affected Channels: DevTools
• Lighthouse version: 5.7.0
• Chrome version: 80.0.3977.4 (Official Build) canary (64-bit)
• Operating System: MacOS

[connorjclark]

This is WAI unfortunately, I don't think we've discussed detecting the tools suggested in stack packs. At the moment stack-specific advice is always given when a specific stack is detected.

[patrickhulce]

This is the same root issue as #2832 and should be resolved when the proposed solution is implemented. De-duping into it.