Viewing 12 replies - 1 through 12 (of 12 total)
  • Hi @kuknus,

    Thanks for contacting us, my name is Fellyph and I will help today. I saw that we started another thread previously.

    About the page experience guide, it is a tool to provide ways to improve your application in general there are items related to the plugin, but also there are items outside of the AMP plugin scope. It passes 27 checks on your website and as we can see the web core vitals are good, but there are a few improvements that can be made.

    The list you can see at the bottom of the page, I will try to go one-by-one:

    – Font “eicons” needs to use optional for the font-display property, I have a look here and this font is called by elementor, this is outside the amp plugin scope to control it, but you can check on elementor settings if there is a option to change the font-display to optional
    – About the data-hero I would check if it is possible to include this property manually but is not critical your LCP is passing as Good.
    – Preload AMP runtime is not applicable, as the AMP plugin will automatically preload it if needed.
    – Initial server-response, this is the most critical Item, it is taking 3498ms to respond. It is related to the performance from your hosting, you could check if your hosting is using a recent version of PHP and enabling some caching on the server side. But I saw your website is using WP Rocket to mitigate this problem and cache this response, the report is still getting the response without caching.

    The wording “poor” needs a better description, I will report to the AMP framework team. It causes confusion. My website passes all web core vitals and also appears the same message.

    And please could you share some of the errors you are getting at search console and the pages that are related to them?

    Thread Starter Anonymous User 17915638

    (@anonymized-17915638)

    Apologies, for improper use of the word “poor”.

    Please see all the errors my website is facing related to Page Experience:

    https://imgur.com/a/YL1vCRe
    Note: All the pages are AMP.

    Hi @kuknus,

    I mean the better description from AMP Page Experience guide, It should use better description because it causes a negative impression about the report.

    About your screenshots at 2nd of November was the day that you install the AMP plugin? LCP is not only on the front-end side as I mentioned before your server response is high, I would suggest you check with your hosting.

    Plugin Author Weston Ruter

    (@westonruter)

    Sorry, where is the word “poor” being used?

    Something to keep in mind is that the AMP Page Experience tool is doing a lab analysis of your page. It tries to show Field data, but it doesn’t have enough available (although I’m not sure why this is since the same CrUX data should be used by Search Console; I suppose it’s because this URL specifically is not in CrUX). In the Lab data tab, it shows the three CWV metrics are all good:

    Nevertheless, as Fellyph notes, the screenshot in Search Console it shows that there was a big dip in PX around the beginning of November:

    Did you make any big changes to your site around that time?

    PageSpeed Insights is showing that CrUX for the origin (averaging all URLs) is failing:

    But this is over a month period and is not a live analysis of the provided URL.

    As Fellyph noted, the server response is high and this is likely the cause of the PX degradation:

    It is surprising that even though you have WP Rocket installed, that there is a 2+ second delay. Perhaps WP Rocket has page caching turned off?

    Thread Starter Anonymous User 17915638

    (@anonymized-17915638)

    1) In the beginning of November, my host had problems: https://twitter.com/SiteGround/status/1458812869735243780

    2) WP Rocket Caching is already ON for the entire site:

    View post on imgur.com

    I am NOT sure why Page Experience is low even when all my URLs pass three CWV metrics in AMP Page Experience Guide.

    Plugin Author Weston Ruter

    (@westonruter)

    Do you have SiteGround’s SuperCacher active? See https://www.siteground.com/tutorials/getting-started/the-supercacher/

    Thread Starter Anonymous User 17915638

    (@anonymized-17915638)

    Yes. NGINX is crucial for speed optimizations.

    View post on imgur.com

    Hi @kuknus,

    The ideal serve response is 300ms or lower, Actually is 10x Higher, I would check with your hosting which service is consuming more resources from your server.

    Other suggestion is checking the Database queries – Check slow-performing DB queries with Query Monitor or Newrelic and Optimize them.

    If you have any question about the plugin, please let me know.

    Thread Starter Anonymous User 17915638

    (@anonymized-17915638)

    Hello @fellyph,

    I will get in touch with Hosting Provider to see what is causing the high server response time.

    Meanwhile, I am still worried about my website’s Core Web Vitals: https://imgur.com/a/3UkMmi7

    Google is showing LCP issue for all the AMP Pages when in reality, all my AMP URLs pass three CWV metrics in AMP Page Experience Guide.

    Hi @kuknus,

    I understand that you are worried about Core Web Vitals, but this metric isn’t exclusively AMP related, it is an overall metric. AMP works on the front-end side of your application, if your server deliver the first byte in 2,3s (92% of total LCP time), it only let the window of 0,2s for the front-end to accomplish the LCP of 2,5s.

    We can spend time debugging AMP, but It won’t cover the impact of the higher server time response on this case.

    You can check your more stats at gtmetrix

    You can check more info about Optimeze the LCP here.

    Before anything else, improve how and where your server handles your content. Use Time to First Byte (TTFB) to measure your server response times. You can improve your TTFB in a number of different ways: Optimize your server, Route users to a nearby CDN, Cache assets, Serve HTML pages cache-first, Establish third-party connections early Use signed exchanges

    Hi @kuknus,

    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.

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘Poor AMP Page Experience Guide’ is closed to new replies.