Hello @zeplanilha
Thank you for contacting and sharing your UUID with us, As we checked your site on the Page speed, it seems there is an opportunity of 2.5 seconds with server-side rendering.(screenshot)
The server-side rendering can be optimized using caching, As we checked your site you are using FlyingPress plugin for caching, but the response header for flyingPress always reports a MISS for AMP pages.(screenshot)
When It says “MISS” it means it was not able to find a cached version of pages so it’s retrieving a fresh copy which includes a whole lot of processing delaying the page response (Server-side rendering)
We will recommend contacting FlyingPress support and checking with them about why AMP pages are MISS.
We will also recommend checking the following documentation on How your AMP pages perform better with persistent caching and Page caching
Hope this is helpful!
In an early contact with them about bad LCP in amp pages, they said:
“We don’t optimize/cache AMP pages since it’s handled by Google”
Hello @zeplanilha
I guess they confused the WordPress page cache with the AMP cache.
The AMP cache is created once Google bots crawl your site, the AMP cache is used when someone searches a term on Mobile and if your site has a relevant term it will present a link to the AMP cache on Google Search Result.
You can learn more about How AMP pages are cached on this article
The AMP cache has nothing to do with the WordPress page cache.
I think the FlyingPress plugin is not caching pages with query parameters
eg: https://zeplanilha.com/?abc=1 is not cached.(screenshot)
You can check by adding any random parameters such as ?xyz=abc ?opq=24 etc.
You can check the response header using this tool
Hey @zeplanilha
Another suggestion you can try changing Paired URL Structure to path suffix /amp/ and check if the endpoint is cached.
Goto Dashboard->AMP->Paired URL Structure and choose path suffix /amp/
This will change all AMP pages from ?amp to /amp/ and hopefully, the /amp/ endpoint is cached by the FlyingPress plugin.
Olá @zeplanilha,
O LCP, involve diversos elementos e eles seguem uma sequência: localização do servidor > capacidade de processamento do servidor > renderização da página.
AMP trabalha na última camada, se você tiver algum atraso nas etapas anteriores o AMP vai processar a página depois do tempo limite do LCP.
Por isso que o Milind comentou sobre um plugin de cache para você resolver o problema de processamento do seu servidor que tem um TTFB de 3s ou 3000ms quando o ideal é de 300ms.
Olá @zeplanilha,
Vou fechar esse tópico, conforme conversamos no linkedIn o flypress é a fonte do delay referente ao LCP:
Versão não-AMP:
Versão AMP:
O mesmo problema está ocorrendo no demo do flypress. Nesse caso você tem a opção de utilizar um tema compatível com AMP ou utilizar em tema alternativo no modo leitor.
Só uma correção o nome tema é Reco
