You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 16, 2024. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: