Page experience issue

Hi guys, i’m getting this message from AMP Page Experience Guide:

Your AMP page from origin has a good page experience, but the cached AMP page needs work. Don't fret, we have some recommendations to help you improve! However, it's rare that we see a cached AMP page fail page experience. Please file a GitHub issue so that we can take a look and see how AMP can help.

url: https://me.ahazou.com/startnetvpn

Anyone can help to understand?

[twifkak]

Looks like I may have overestimated the impact of the cert bytes, but I’m not sure by how much. Looking at the waterfalls again, I see a significant difference in TTFB after the TLS negotiation stage. I suspect that is a function of which cache tier hit.

As some anecdotal evidence of that, here’s 3 runs of the same comparison in sequence:

run 1 - origin TTFB = 721 ms; cache TTFB = 775 ms run 2 - origin TTFB = 743 ms; cache TTFB = 779 ms run 3 - origin TTFB = 720 ms; cache TTFB = 740 ms

It could be that the 3rd set of requests are after closer cache tiers are populated. That said, it’s possible that all that’s being observed is varying performance characteristics of some different replicas being chosen along the request path.

[thiagoenge]

Hi guys, i would like to share another stranger message on page experience tool, i think that is related to this discussion

Why the message said that a poor page experience if i have all metrics green?

Below there are some actions appointed, the first one, about meta viewport, the current tag is: <meta name="viewport" content="width=device-width,minimum-scale=1,initial-scale=1"> which is injected by framework that we use (NextJs), the question is, this issue is really a problem or once all metrics are green is more an warning than error?