Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

timeline poor page experience throught releases? #60

Closed
barruka opened this issue Nov 11, 2020 · 3 comments
Closed

timeline poor page experience throught releases? #60

barruka opened this issue Nov 11, 2020 · 3 comments
Assignees

Comments

@barruka
Copy link

barruka commented Nov 11, 2020

Timeline google search console core web vitals:

I think movements are amp releases related, because we hadn't changed any server side stuff (code, server, hosting, ...)
Hope this helps to performance team.

Components in use:

v0
amp-analytics
amp-sidebar
amp-form

Thank you all!

@kristoferbaxter
Copy link
Contributor

Can you share a few example URLs impacted?

Do these pages fulfill all the items listed by the AMP Page Experience tool?

@barruka
Copy link
Author

barruka commented Nov 12, 2020

This report affect to all category pages and product pages:

Category page:
https://www.irisalia.es/afrodisiacos/perfumes-feromonas

Product page:
https://www.irisalia.es/afrodisiacos/perfumes-feromonas/mai-air-freshener-vanilla

We didn't run the AMP Page Experience tool on each page, but we changed nothing so the only difference are the AMP releases throught the timeline.

@kristoferbaxter
Copy link
Contributor

For the category page there are 5 recommendations.
Screen Shot 2020-11-12 at 7 42 28 AM

On the product page there are also 5 recommendations.
Screen Shot 2020-11-12 at 7 44 16 AM

A few notes to explain these outcomes:

  1. CLS impacts are due to not using an AMP Optimizer. AMP Caches, like those at Google will automatically apply a specific optimization removing the AMP boilerplate... doing so on the canonical origin will reduce the CLS issue significantly.

  2. Product Page images are oversized and unoptimized. Again, AMP Caches will losslessly optimize the output from the canonical origin... but direct visits will be impacted. Highly recommend using modern formats and optimizing image compression.

Here's an example: https://www.irisalia.es/i/m/MAI-Attraction-Air-Freshener-Vanilla-30-ml-Aromatizador-con-Feromonas.jpg
Original: 213kB
JPG Optimized: 54kB (75% reduction)
WebP Optimized: 40.4kB (81% reduction)
Avif Optimized: 27.4kB (87% reduction)

Why does this matter?

Visits to AMP documents are a blend of AMP Cache visits and origin visits. To achieve good page performance overall, it's highly recommended to ensure origin pages are optimized to the same degree as cached pages.

There are several factors to CWV, including a changing/expanding audience group that can impact the overall real world performance. Ensuring your documents use all the best recommendations available will give these pages the best opportunities to pass.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants