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
The AMP plugin is removing the <link rel="preload" as="script" href="https://cdn.ampproject.org/v0.js"> line from AMP output. This is happening since the 2.1 version of the plugin.
This is affecting LCP loading speed, and it's a recommendation according to the AMP Page Experience Guide tool.
Expected Behaviour
<link rel="preload" as="script" href="https://cdn.ampproject.org/v0.js"> should be always present inside <head> </head>.
Screenshots
No response
PHP Version
No response
Plugin Version
2.2.0
AMP plugin template mode
Standard
WordPress Version
5.8.2
Site Health
No response
Gutenberg Version
No response
OS(s) Affected
No response
Browser(s) Affected
No response
Device(s) Affected
No response
Acceptance Criteria
No response
Implementation Brief
No response
QA Testing Instructions
No response
Demo
No response
Changelog Entry
No response
The text was updated successfully, but these errors were encountered:
Bug Description
The AMP plugin is removing the
<link rel="preload" as="script" href="https://cdn.ampproject.org/v0.js">line from AMP output. This is happening since the 2.1 version of the plugin.This is affecting LCP loading speed, and it's a recommendation according to the AMP Page Experience Guide tool.
Expected Behaviour
<link rel="preload" as="script" href="https://cdn.ampproject.org/v0.js">should be always present inside<head> </head>.Screenshots
No response
PHP Version
No response
Plugin Version
2.2.0
AMP plugin template mode
Standard
WordPress Version
5.8.2
Site Health
No response
Gutenberg Version
No response
OS(s) Affected
No response
Browser(s) Affected
No response
Device(s) Affected
No response
Acceptance Criteria
No response
Implementation Brief
No response
QA Testing Instructions
No response
Demo
No response
Changelog Entry
No response
The text was updated successfully, but these errors were encountered: