Nice overview! I'd like to see a movement towards more user-centric paint metrics. FCP was a step in the right direction but I think we can do better. Largest Contentful Paint (LCP) looks promising: web.dev/largest-contentful-paint
However, I think it's missing the point by focusing on one element. Several adjacent elements painted almost simultaneously are not considered to be the same visual element, whereas for a user, they are (first Gestalt law, regarding proximity).
In addition, the metric is complex to implement as, for example, every image needs to have a Timing-Allow-Origin HTTP header. The server configuration required for that will only be achieved by people who are already involved in Web Performance.
The Start Render is much easier to evaluate and can be collected on any public page right now without any implementation costs. Much easier to compare your web performance to others.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Nice overview! I'd like to see a movement towards more user-centric paint metrics. FCP was a step in the right direction but I think we can do better. Largest Contentful Paint (LCP) looks promising: web.dev/largest-contentful-paint
LCP is promising for advanced needs.
However, I think it's missing the point by focusing on one element. Several adjacent elements painted almost simultaneously are not considered to be the same visual element, whereas for a user, they are (first Gestalt law, regarding proximity).
In addition, the metric is complex to implement as, for example, every image needs to have a
Timing-Allow-Origin
HTTP header. The server configuration required for that will only be achieved by people who are already involved in Web Performance.The Start Render is much easier to evaluate and can be collected on any public page right now without any implementation costs. Much easier to compare your web performance to others.