Amp Error on amp.dev

Hi @immmukeshpatel,

Thanks for contacting us again; it looks like the issue is at the amp.dev page-experience tool. I tested my personal blog that is using AMP, and I got the same error, but if you check the AMP validator, it is passing:

https://search.google.com/test/amp/result?id=cZEuh3m-4Qz9lP-aQNu-_g

AMP framework(.dev) and AMP WordPress plugin are different teams, but I will notify the amp.dev team about this issue.

Hi @immmukeshpatel,

For example, the pageSpeed Insights has two reports. The first one is how real users are seen your website based on the last 28 days, and the second report is the lab test collected from a simulated environment. This video has some good info about it:

Going back to your website, the Core web vitals from real users are failing, which means if your website had something slow in the past few days, it could affect this report. The lab data all the core web vitals are ok at the moment. I would suggest watching if the user’s data will reflect in the next few days.

You should consider checking:
1. the location from your server and your audience
2. Check the type of devices from your audience because the number of ads can slow down users’ low-end devices and affect some metrics.

The AMP plugin will provide the tools to improve your front-end, but once the ads call an external script to render ads, it goes outside the AMP plugin umbrella; the number of ads included on the page will affect the performance.

But the revenue is important for everyone, but the best way is to balance performance and revenue. For example, on your homepage, 2/3 of the screen are ads for me. In this type of scenario, the lab test won’t get it because this type of ads won’t be loaded on the lab test.

Hi @immmukeshpatel,

Yes, I know that it wasn’t served by AMP but is just an example to balance it. If you have any questions feel free to contact us again.

Hi @immmukeshpatel,

Thanks for getting back to us, this is a good question. Always should think about your users, in other words, you should look at the field data.

1. The lab data is a simulated environment and it can give different results. Only one test on a particular page can’t be a decision-maker. For example for me the page speed was:

AMP:

non-AMP

2. AMP is not a ranking factor, you don’t need to use AMP only to use AMP. The key point is performance and user experience. If you have better infrastructure and front-end better than AMP, great!

But you should look at all the layout variations and possible scenarios: sharing buttons, youtube videos, images, slideshow, tracking tools, ads, and other functionalities when is used.

For example, sometimes for me, your website loads 8MB of content when the biggest percentage is ads. You can load your website and have a different experience. That is another reason to check the field data to compare the AMP and non-AMP versions before taking any decision.

3. The AMP job is to enhance the front-end and improve the rendering on the front-end side. There are other best practices to improve the performance of a WordPress website. And sometimes applying all the best practices can guarantee the best results, may you end in an over-doing situation. You should test and check each configuration is better for your users.

Also, be aware if you apply best practices for your AMP and non-AMP version, also you should look at the site health reports to check if AMP has the infrastructure that is needed to work properly.

Those are my considerations, I hope that would help you.