Alberto Medina

@ejazz Please open a separate support ticket for your case.

P.S.: That is a warning message, not an error. It may have to do with the version of PHP you are using.

@classicus Please open a separate topic in the forum to address your issue.

If the plugin is configured to Transitional or Native mode, all templates in your theme are eligible for AMP. Since AMP compatibility for TwentyFourteen will be included in 1.2, you will be able to have all your site in AMP, provided that you are not using plugins that inject JS to the pages, and that your theme is the standard TwentyFourteen theme (e.g. not modifications such as adding scripts, or too much CSS).

You can learn about how to use the plugin here: https://amp-wp.org.

Notice that in the upcoming release (1.2), the term Native mode will change and the docs will be updated.

Let us know if you have further questions.

Most of the optimizations here are being done by the plugin already. The preloading of hero images is not done by the plugin automatically because it is dependent on the theme being used.

One optimization that will be done in the future is the elimination of the AMP boiler plate, which is a piece of markup that hides the page until it is fully rendered. This implementation of this issue will enable the elimination of the boilerplate, which will probably give you your .5 seconds back ??

Yep; that means the problem is on the theme side as the link tag is not present. Perhaps it is being removed by a plugin.

That page has a corresponding AMP page:

https://www.veecotech.com.my/top-5-mistakes-your-website-should-avoid-in-2019/?amp

The plugin is working as expected.

As indicated, questions related to specific themes/plugins need to be directed to the corresponding theme/plugin authors.

Looking at the page you linked, the validation error reported by the validator extension is related to an auto-ads component script being added to the page but not used. When communicating with support from themes/plugins it is useful to indicate specific validation errors being observed.

I wonder if the functionality comes from this plugin: https://www.ads-software.com/plugins/pegasaas-accelerator-wp/

Not sure what exactly each of those options does to the pages; the key would be to experiment with them and see the ones that introduce AMP incompatibilities.

AMP does not allow custom JS; any option that introduces scripts should be disabled.

AMP also imposes certain restrictions on CSS use and size; options related to CSS need to be evaluated to see if they cause problems.

Another reference: https://developers.google.com/amp/cache/update-cache

Please provide a URL to site/pages having the issues.

How are you adding the code for inserting ads?

Verified: linked page works with the ?amp query parameter.

Custom JS is not allowed in AMP currently. It was recently announced that some support for custom JS is coming to AMP (https://twitter.com/AMPhtml/status/1116378847937613824).

In the mean time, if deactivating the WP Bakery plugin removes the error, you can ask Google (via Search Console) to validate the fix.