71–77 of 77 posts
Meanwhile "Engineering Leader" at Chrome argues that 2.4s to First Contentful Paint is fast: https://twitter.com/addyosmani/status/1678117107597471745?s=... Google's one (of many) heads has no idea what another (of many) heads says or does.
Meanwhile "Engineering Leader" at Chrome argues that 2.4s to First Contentful Paint is fast: https://twitter.com/addyosmani/status/1678117107597471745?s=... Google's one (of many) heads has no idea what another (of many) heads says or does.
Whether 2.5s to LCP is fast or not depends on what your normal day to day experience is
Of course, when everything takes 8 seconds to load, 2.4 seconds is "fast" :)
Meanwhile "Engineering Leader" at Chrome argues that 2.4s to First Contentful Paint is fast: https://twitter.com/addyosmani/status/1678117107597471745?s=... Google's one (of many) heads has no idea what another (of many) heads says or does.
Isn’t that tweet talking about 2.4s for Largest Contentful Paint? It mentions 0.9 for FCP being fast, which I agree is pretty reasonable.
Earlier quoted context omitted.
Isn’t that tweet talking about 2.4s for Largest Contentful Paint? It mentions 0.9 for FCP being fast, which I agree is pretty reasonable.
Funnily enough I clearly remember typing Largest Contentful Paint. But it turns out I typed First :) My point still stands. "The First Contentful Paint (FCP) metric measures the time from when the page starts loading to when any part of the page's content is rendered on the screen." [1] Unless your server is overwhelmed, and can't send back data fast enough, there's literally no way to call "1 second before anything…
[1] https://infrequently.org/2022/12/performance-baseline-2023/
Earlier quoted context omitted.
Funnily enough I clearly remember typing Largest Contentful Paint. But it turns out I typed First :) My point still stands. "The First Contentful Paint (FCP) metric measures the time from when the page starts loading to when any part of the page's content is rendered on the screen." [1] Unless your server is overwhelmed, and can't send back data fast enough, there's literally no way to call "1 second before anything…
He’s referring to the P75 from Chrome’s field data. Now, Reddit definitely could do more here and get that LCP at the same time as the FCP (eliminate load and render delay). But a big purpose for these metrics is to make the web more accessible/usable, and the reality is most of the world doesn’t have iPhones or fast networks[1]. [1] https://infrequently.org/2022/12/performance-baseline-2023/
And yet these metrics literally optimize for Reddit's 109 Javascript files to render a page of text with images in 2.4 seconds. And they call it fast.
However you slice, dice, or interpret these metrcis, none of these shenanigans make it fast.
What these metrics and "75p" show is that modern web sucks for everyone, and they have to pretend that 2.4s to render a page is fast because everyone is even slower.
Or, to put in context: Reddit's servers serve that page in under 200 milliseconds. There's literally no justification in the world that make it ok to say "2.4 seconds to render that on screen is fast". None.
We started seeing reports about it in GSC early July, when over a single day all our scores turned to crap with no explanation. We are in the yellow, but the biggest culprits for blocking time are...Google Tag Manager, GAds (and Ganalytics where we still have it). So yeah, thanks Google, can't wait to lose on SEO due to your own products. And also, thanks for releasing this without the proper analysis tooling. ( http…
I for one commend Google's efforts to improve the web's chances of long-term survival by eliminating themselves and hopefully tracking in general.
My company is scrambling to account for the changes here, and ultimately it will be users who suffer until we have the proper data available.
This should’ve been a standard that all major browsers have implemented and agreed to, before being rolled out generally.
Earlier quoted context omitted.
I for one commend Google's efforts to improve the web's chances of long-term survival by eliminating themselves and hopefully tracking in general.
Meh, with Googles resources they could do so much good. This is a drop in the bucket, compared to what they could be doing. My company is scrambling to account for the changes here, and ultimately it will be users who suffer until we have the proper data available. This should’ve been a standard that all major browsers have implemented and agreed to, before being rolled out generally.
They don't care if their web tendrils are a net positive or not