This is not an issue with the AMP plugin. There’s nothing that can be done on our side. It’s not apparently even an issue with AMP, but rather with how Lighthouse is reporting.
Thread Starter
wn nj
(@waseemnaikgmailcom)
pagespeed is reporting this on amp
and if lighthouse is an issue, that too is google’s own implementation;
both are google teams;
can they talk with each other and figure out the problem(s)?
TIA
They are talking on the AMP issue you linked to. Also opening a support topic here for the plugin won’t have any benefit.
-
This reply was modified 5 years, 11 months ago by
Weston Ruter.
Thread Starter
wn nj
(@waseemnaikgmailcom)
@choumx choumx mentioned this issue 18 hours ago
Load or Use only required portion of AMP Library Framework #27741
how does this work ?
and have you updated the amp plugin along these lines ?
kindly advise
The AMP plugin removes scripts that are not used in the page, yes. It will automatically add scripts for components as required, and if you manually added AMP component scripts that aren’t used, they will be removed.
Thread Starter
wn nj
(@waseemnaikgmailcom)
that is good to know;
however, I ran the test again, and the results remain the same:
URL
Transfer Size
Potential Savings
/v0.js(cdn.ampproject.org)
72.3 KB
35 KB
/v0/amp-analytics-0.1.js(cdn.ampproject.org)
30.9 KB
13.3 KB
/v0/amp-bind-0.1.js(cdn.ampproject.org)
17.5 KB
12.4 KB
/v0/amp-form-0.1.js(cdn.ampproject.org)
16.1 KB
10.2 KB
/v0/amp-lightbox-0.1.js(cdn.ampproject.org)
8.7 KB
5.5 KB
…v0/amp-auto-lightbox-0.1.js(cdn.ampproject.org)
4.1 KB
2.7 KB
/v0/amp-install-serviceworker-0.1.js(cdn.ampproject.org)
5.5 KB
2 KB
pagespeed continues to have problems with amp scripts for size;
how can I help you improve the amp plugin ?
All those scripts are being used by AMP components on the page, right?
There is nothing more the AMP plugin can do here. This is an AMP core issue.
Thread Starter
wn nj
(@waseemnaikgmailcom)
I am not sure what that means, but perhaps you are suggesting that the AMP plugin is not part of AMP core?
if that is the case, then are you resolving it with AMP core ?
and when do you expect light a resolution that does not penalize the website by pagespeed using your plugin ?
The AMP plugin is not part of AMP core, no.
For the resolution, follow the issue you originally referenced: https://github.com/ampproject/amphtml/issues/28638
Thread Starter
wn nj
(@waseemnaikgmailcom)
so, are you getting any help from them to solve this ?
our pages are in penalty box because of this…
There’s nothing we can do from the plugin side. You have to follow the AMP core issue.
Note that the Lighthouse warning does not necessarily indicate a score penalty. The performance of the page is what the score is derived from. Apparently Lighthouse may be misidentifying those scripts as being problematic and so you can see from the AMP core issue a linked Lighthouse issue that may address that on the next Lighthouse release.
Thread Starter
wn nj
(@waseemnaikgmailcom)
sounds like if you cannot follow and fix; then I am one additional step removed;
I cannot help you and cannot help them;
>>Note that the Lighthouse warning does not necessarily indicate a score penalty.<<
it does not say that; is this your personal option or fact?
>>Apparently Lighthouse may be misidentifying those scripts as being problematic and so you can see from the AMP core issue a linked Lighthouse issue that may address that on the next Lighthouse release. <<
do you know when the next lighthouse release is due?
Thread Starter
wn nj
(@waseemnaikgmailcom)
it has no date for release
do you know the release date?
