-
Notifications
You must be signed in to change notification settings - Fork 3
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
New CruX metrics #10
Comments
Yes we're looking into adding First Input Delay , CLS and LCP in a (near term) release.
We're working with the Google team on the exact key metrics to bring in (and they'll be in the API first then into the UI shortly after).
Thanks for the question!
Sent via Superhuman ( https://sprh.mn/[email protected] )
…On Wed, May 27, 2020 at 10:28 AM, samunderwood < ***@***.*** > wrote:
Hey,
Are there plans to update this to support new metrics in CruX such as
cumulative layout shift and largest contentful paint?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub (
#10 ) , or unsubscribe (
https://github.com/notifications/unsubscribe-auth/AE6P44QIGS25SRMJWGX4K6TRTVEUXANCNFSM4NMLCPTA
).
|
Awesome! Another question, in the UI how are you categorising FCP as fast, average and slow? Strugglign to find any pre-defined metrics for this categorisation? It doesn’t look like you surface this in the API.
… On Wednesday, May 27, 2020 at 6:47 pm, Jacob Loveless ***@***.*** ***@***.***)> wrote:
Yes we're looking into adding First Input Delay , CLS and LCP in a (near term) release.
We're working with the Google team on the exact key metrics to bring in (and they'll be in the API first then into the UI shortly after).
Thanks for the question!
Sent via Superhuman ( ***@***.*** )
On Wed, May 27, 2020 at 10:28 AM, samunderwood < ***@***.*** > wrote:
>
>
>
> Hey,
>
>
>
> Are there plans to update this to support new metrics in CruX such as
> cumulative layout shift and largest contentful paint?
>
>
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub (
> #10 ) , or unsubscribe (
> https://github.com/notifications/unsubscribe-auth/AE6P44QIGS25SRMJWGX4K6TRTVEUXANCNFSM4NMLCPTA
> ).
>
>
>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub (#10 (comment)), or unsubscribe (https://github.com/notifications/unsubscribe-auth/ADVITCWF3N5WZMRF3EDSI6LRTVG3DANCNFSM4NMLCPTA).
|
You know … we sure don't!
So a:
fast first paint is <1000ms, and a slow is >2500ms
fast first contentful paint is <1000ms, and a slow is >2500ms
fast content load is <1500ms, and a slow is >3500ms
These are all modeled after PageSpeed insights. Will get that added as a route!
Sent via Superhuman ( https://sprh.mn/[email protected] )
…On Thu, May 28, 2020 at 2:29 AM, samunderwood < ***@***.*** > wrote:
Awesome! Another question, in the UI how are you categorising FCP as fast,
average and slow? Strugglign to find any pre-defined metrics for this
categorisation? It doesn’t look like you surface this in the API.
> On Wednesday, May 27, 2020 at 6:47 pm, Jacob Loveless < notifications@ github.
com ( ***@***.*** ) (mailto: notifications@ github. com (
***@***.*** ) )> wrote:
> Yes we're looking into adding First Input Delay , CLS and LCP in a (near
term) release.
>
> We're working with the Google team on the exact key metrics to bring in
(and they'll be in the API first then into the UI shortly after).
>
> Thanks for the question!
>
> Sent via Superhuman ( https:/ / sprh. mn/ ?vip=jacob. loveless@ edgemesh.
com ( ***@***.*** ) )
>
> On Wed, May 27, 2020 at 10:28 AM, samunderwood < notifications@ github. com
( ***@***.*** ) > wrote:
>
> >
> >
> >
> > Hey,
> >
> >
> >
> > Are there plans to update this to support new metrics in CruX such as
> > cumulative layout shift and largest contentful paint?
> >
> >
> >
> > —
> > You are receiving this because you are subscribed to this thread.
> > Reply to this email directly, view it on GitHub (
> > https:/ / github. com/ edgemesh/ crux. run/ issues/ 10 (
#10 ) ) , or unsubscribe (
> > https:/ / github. com/ notifications/ unsubscribe-auth/ AE6P44QIGS25SRMJWGX4K6TRTVEUXANCNFSM4NMLCPTA
(
https://github.com/notifications/unsubscribe-auth/AE6P44QIGS25SRMJWGX4K6TRTVEUXANCNFSM4NMLCPTA
)
> > ).
> >
> >
> >
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub ( https:/ / github. com/
edgemesh/ crux. run/ issues/ 10#issuecomment-634830768 (
#10 (comment) ) ),
or unsubscribe ( https:/ / github. com/ notifications/ unsubscribe-auth/ ADVITCWF3N5WZMRF3EDSI6LRTVG3DANCNFSM4NMLCPTA
(
https://github.com/notifications/unsubscribe-auth/ADVITCWF3N5WZMRF3EDSI6LRTVG3DANCNFSM4NMLCPTA
) ).
>
>
>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub (
#10 (comment) ) ,
or unsubscribe (
https://github.com/notifications/unsubscribe-auth/AE6P44SIJUD2QJWTDLCZZVTRTYVJFANCNFSM4NMLCPTA
).
|
Awesome, thanks!
… On Thursday, May 28, 2020 at 7:31 pm, Jacob Loveless ***@***.*** ***@***.***)> wrote:
You know … we sure don't!
So a:
fast first paint is <1000ms, and a slow is >2500ms
fast first contentful paint is <1000ms, and a slow is >2500ms
fast content load is <1500ms, and a slow is >3500ms
These are all modeled after PageSpeed insights. Will get that added as a route!
Sent via Superhuman ( ***@***.*** )
On Thu, May 28, 2020 at 2:29 AM, samunderwood < ***@***.*** > wrote:
>
> Awesome! Another question, in the UI how are you categorising FCP as fast,
> average and slow? Strugglign to find any pre-defined metrics for this
> categorisation? It doesn’t look like you surface this in the API.
>
> > On Wednesday, May 27, 2020 at 6:47 pm, Jacob Loveless < notifications@ github.
> com ( ***@***.*** ) (mailto: notifications@ github. com (
> ***@***.*** ) )> wrote:
> > Yes we're looking into adding First Input Delay , CLS and LCP in a (near
> term) release.
> >
> > We're working with the Google team on the exact key metrics to bring in
> (and they'll be in the API first then into the UI shortly after).
> >
> > Thanks for the question!
> >
> > Sent via Superhuman ( https:/ / sprh. mn/ ?vip=jacob. loveless@ edgemesh.
> com ( ***@***.*** ) )
> >
> > On Wed, May 27, 2020 at 10:28 AM, samunderwood < notifications@ github. com
> ( ***@***.*** ) > wrote:
> >
> > >
> > >
> > >
> > > Hey,
> > >
> > >
> > >
> > > Are there plans to update this to support new metrics in CruX such as
> > > cumulative layout shift and largest contentful paint?
> > >
> > >
> > >
> > > —
> > > You are receiving this because you are subscribed to this thread.
> > > Reply to this email directly, view it on GitHub (
> > > https:/ / github. com/ edgemesh/ crux. run/ issues/ 10 (
> #10 ) ) , or unsubscribe (
> > > https:/ / github. com/ notifications/ unsubscribe-auth/ AE6P44QIGS25SRMJWGX4K6TRTVEUXANCNFSM4NMLCPTA
> (
> https://github.com/notifications/unsubscribe-auth/AE6P44QIGS25SRMJWGX4K6TRTVEUXANCNFSM4NMLCPTA
> )
> > > ).
> > >
> > >
> > >
> >
> > —
> > You are receiving this because you authored the thread.
> > Reply to this email directly, view it on GitHub ( https:/ / github. com/
> edgemesh/ crux. run/ issues/ 10#issuecomment-634830768 (
> #10 (comment) ) ),
> or unsubscribe ( https:/ / github. com/ notifications/ unsubscribe-auth/ ADVITCWF3N5WZMRF3EDSI6LRTVG3DANCNFSM4NMLCPTA
> (
> https://github.com/notifications/unsubscribe-auth/ADVITCWF3N5WZMRF3EDSI6LRTVG3DANCNFSM4NMLCPTA
> ) ).
> >
> >
> >
>
>
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub (
> #10 (comment) ) ,
> or unsubscribe (
> https://github.com/notifications/unsubscribe-auth/AE6P44SIJUD2QJWTDLCZZVTRTYVJFANCNFSM4NMLCPTA
> ).
>
>
>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub (#10 (comment)), or unsubscribe (https://github.com/notifications/unsubscribe-auth/ADVITCVBCF5XSMVBIY5XMIDRT2UXPANCNFSM4NMLCPTA).
|
Is there any ETA for when you think you'll be able to add the new CrUX metrics to the API? 😊 |
Not the next release (May) but the one after (June).
Sent via Superhuman iOS ( https://sprh.mn/[email protected] )
…On Thu, Jun 4 2020 at 7:54 AM, samunderwood < ***@***.*** > wrote:
Is there any ETA for when you think you'll be able to add the new CrUX
metrics to the API? 😊
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub (
#10 (comment) ) ,
or unsubscribe (
https://github.com/notifications/unsubscribe-auth/AE6P44QSPQVX6ZA76JIG2TDRU6YTPANCNFSM4NMLCPTA
).
|
This still planned for release this month? 😊 |
working on the rewrite of the parser as we speak! |
Awesome, I have a blog post prepped for when this goes live to show how to use it with Google Sheets 😊 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey,
Are there plans to update this to support new metrics in CruX such as cumulative layout shift and largest contentful paint?
The text was updated successfully, but these errors were encountered: