Not efficient at all and crammed with errors.

Are you interested in getting our help to get AMP working on your site, or are you just interested in providing destructive feedback to our work?

Moderator note:

1. Please use your public words.

2. This is a support topic, so I’m going to move it from reviews into support.

Hello @ap6y3jimm

Sorry to hear about your experience with the AMP plugin, I will try to resolve the issues you are facing, in order start can you please share your site URL and site health information using this form.

I will take advantage of your offer of constructive help and provide access. If you manage to tweak everything and the GooglePageSpeed ??metrics really grow, I will change my mind and my negative comment.
I understand that you take my comment not glad. But you also understand my reaction to unfulfilled expectations.
I could understand the situation if I had a complex site with rare plugins and a non-standard structure. But I have the simplest site with 11 pages. A minimum of plugins, and only those that are fully compatible and the most popular.
I was hoping that you have definitely tested this configuration and it should work tolerably well. In practice, it turned out that no. Therefore, my reaction is fair. Here is a screenshot of the speed estimate of how I was able to tweak it using the caching plugin. And everything works! Nothing broke including scripts or design. After enabling AMP, the score dropped dramatically and the work of all modules was disrupted6, and even the menu in the basement of the site fell off. You can see for yourself.

https://monosnap.com/file/QcMBDRxI2q5QgqqT8UbHTZWvvDt1dd

These are indicators without AMP

• This reply was modified 3 years, 10 months ago by ap6y3jimm.

Hello @ap6y3jimm

1. When you enable AMP, the Google PageSpeed score is reduced from the original one. Showing negative influences.

Can you please switch to the transitional mode for now and disable the minification and concatenation feature for JS and CSS in the lite speed cache plugin? so we can identify performance issues and also compare AMP and non-AMP pages.

Please note that minifying and contacting JS also made your AMP pages invalid ( you can check AMP page validation here ), which means it will not be indexed properly and will not show up in google search results, also it will not be stored in AMP cache unless it’s valid AMP page.

2. The PayPal payment form completely disappears from the page: /membership-join/

The plugin you are using may not be compatible with AMP, I think excluding this from AMP is a better way to handle it.

3. The contacts form disappears but leaves instead a link to make another transition to another page where it already appears in its original form. This creates additional unnecessary traffic and reduces the site’s conversion rate.

WPform lite plugin provides standard features is fully AMP compatible.

However, the pro (paid) plugin has some incompatibilities with fancy fields so they have handled it with the link which redirects to non-AMP page, I think asking this question to WPForms support will be the right approach as you paid for the plugin support.

4. In the Blog section, there are sharing buttons for each article, social networks, and a “like” button that are represented by the jetpack plugin. But after enabling AMP, they are modified as it is not necessary. And the “like” button disappears completely.
And this is paid functionality in Jetpack. It turns out that AMP turns off jetpack’s premium paid features.

This is a known issue and still being worked on you can follow the below GitHub issue on GitHub repo for jetpack for further updates.

https://github.com/Automattic/jetpack/issues/9555

As we didn’t receive a response I’ll mark this as resolved. Feel free to open a new support topic if you require any further assistance.