wg-performance Status Update 2021-06-07

[jridgewell]

cc @ampproject/wg-performance

What was accomplished

Lessons Learned

What's Next

[samouri]

What was accomplished

Spent 3 weeks in Hawaii.

• Explored Maui.
  • [x] Road to Hana.
  • [x] Surfing in Lahaina
• Explored Kauai.
  • [x] Kalalau trail
  • [x] Waimea Canyon
• Big Island
  • [x] Walk on volcano
  • [x] See the Milky Way

Lessons Learned

Taking a break is A+

What's Next

Server rendering amp components.

[jridgewell]

What was accomplished

• SSR fluid layout: cl/375756231
• Better optimize WebP image generation during ingestion: cl/375986686
• Ingestion only branch for image experiment: cl/377110349
• New experiment framework for faster SSR experiments: cl/376059362, cl/377108647
• Compress hot-patched amp-geo with brotli (finally!): cl/377307679

Lessons Learned

• Our CSI metrics are sometimes incorrect, because aggregating a percentile is incorrect.

What's Next

• Fix CSI metrics
• Prototype Jolt

[erwinmombay]

What was accomplished

• tested new chrome experimental flags and they're interaction with LCP, CLS, font loading
• results from AVIF/WebP experiments

Lessons Learned

What's Next

• prioritize render time over load time on LCP reporting
• add Timing-Allow-Origin

[rcebulko]

What was accomplished

• Aliased import paths https://github.com/ampproject/amphtml/pull/34562
• lots of core migration and type-checking
• path forward on compiler security sandboxing

What's Next

• compiler security sandboxing
• finish core extraction
• Type-check src/preact so Bento components can be type-checked

[trademinister]

Hello, Created AMP page for Shopify platform - https://trademinister.net/ Can You recommend how can I boost PageSpeed score above 90? Attached current web.dev/measure status

[rcebulko]

It's interesting that Lighthouse is seeing FCP at 3.5s (confirmed locally) even though the Performance tab of DevTools shows it at ~680ms:

As an aside, it looks like the page JS fetches amp-auto-lightbox via JS, rather than it being included in the page at load time. I don't think that should be the issue, though. This isn't the right thread for a deep discussion; could you either file a separate issue or post under the #using-amp channel on the AMP Slack?

[samouri]

@rcebulko: are you using the same throttling settings as lighthouse?

[trademinister]

Hello Ryan,

Can You tell me how to subscribe to AMP Slack channel?

пт, 11 июн. 2021 г., 18:17 Ryan Cebulko @.***>:

It's interesting that Lighthouse is seeing FCP at 3.5s (confirmed locally) even though the Performance tab of DevTools shows it at ~680ms:

[image: image] https://user-images.githubusercontent.com/6694512/121709246-5981e900-caa6-11eb-9243-bb6977c00396.png

As an aside, it looks like the page JS fetches amp-auto-lightbox via JS, rather than it being included in the page at load time. I don't think that should be the issue, though. This isn't the right thread for a deep discussion; could you either file a separate issue or post under the

using-amp channel on the AMP Slack?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ampproject/wg-performance/issues/84#issuecomment-859654232, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFPXTPOJOAULKLDD7HAQCE3TSISKHANCNFSM46ID5HDQ .

[rcebulko]

@trademinister see https://github.com/ampproject/amphtml/blob/main/docs/contributing.md#discussion-channels

[trademinister]

Hello Ryan,

Thanks for the help

пт, 11 июн. 2021 г., 23:10 Ryan Cebulko @.***>:

@trademinister https://github.com/trademinister see https://github.com/ampproject/amphtml/blob/main/docs/contributing.md#discussion-channels

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ampproject/wg-performance/issues/84#issuecomment-859853735, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFPXTPKXGQFC37BF7XDPSQ3TSJUTRANCNFSM46ID5HDQ .