Comments for The AMP Blog https://blog.amp.dev News and announcements from the AMP team Mon, 01 Jun 2020 22:17:28 +0000 hourly 1 https://wordpress.org/?v=6.8.3 Comment on Innovation in navigation on the web platform by Eduardo Gonçalves https://blog.amp.dev/2019/06/05/innovation-in-navigation-on-the-web-platform/#comment-4688 Mon, 24 Jun 2019 00:55:30 +0000 https://blog.amp.dev/?p=2615#comment-4688 Wow! Loved the idea of portals to seamless navigations on the Web!

]]> Comment on A year into contributing back lessons learned from AMP to the whole web by Malte Ubl https://blog.amp.dev/2019/05/21/contributing-back-lessons-learned-part-1/#comment-4484 Mon, 03 Jun 2019 15:12:52 +0000 https://blog.amp.dev/?p=2576#comment-4484 In reply to Joe.

Good question with respect to User Timing. These are for very different purposes.

User Timing is for telling you that the thing you care about is fast. Metrics like LCP can be used to compare sites to each other (since they don’t rely on manual instrumentation) and for easy to use tools to get a good first impression about a side. But as you mention, metrics like LCP just won’t always do what you need. And that is what User Timings are for.

So, we really need both to cover those 2 very different use cases.

]]> Comment on A year into contributing back lessons learned from AMP to the whole web by Joe https://blog.amp.dev/2019/05/21/contributing-back-lessons-learned-part-1/#comment-4483 Mon, 03 Jun 2019 13:01:24 +0000 https://blog.amp.dev/?p=2576#comment-4483 What is the advantage of this compared to measuring with User timing? At a glance it seems that you dont need to insert timing marks. But are there other advantages such as more accuracy?

Has this been measured in SPAs such as Angular? The challenge I see is that if I run a network test the test will end with onload event but content will appear after in Angular

]]>