Skip to content
This repository has been archived by the owner on May 16, 2024. It is now read-only.

userTiming: Lack of User Timing API should not impact score #148

Open
jasonbarry opened this issue Jul 12, 2016 · 1 comment
Open

userTiming: Lack of User Timing API should not impact score #148

jasonbarry opened this issue Jul 12, 2016 · 1 comment
Labels

Comments

@jasonbarry
Copy link

screen shot 2016-07-12 at 11 32 07 am

I use webcoach to score my company's production site. We use React's performance tools for measuring metrics. Those performance measuring calls are dev only and don't get shipped to production. My webcoach score shouldn't be dinged because I'm not using a certain API, one which IMO shouldn't be used in production anyway.

I'm on the boat where the userTiming check should be removed entirely.

@soulgalore
Copy link
Member

yeah, thought about if it should be in the info part from the coach or an actual advice when I added it the first time, but I kind of like the idea of that it helps people opening the eyes for the User Timing API, since it cool (but of course can be better in the future) and gives you more opportunities to collect your own RUM data.

soulgalore added a commit that referenced this issue Jan 15, 2017
@soulgalore soulgalore added the 1.0 label Jan 16, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants