search

GoogleChrome / lighthouse

Automated auditing, performance metrics, and best practices for the web.
https://developer.chrome.com/docs/lighthouse/overview/
Apache License 2.0
28.37k stars 9.37k forks source link

New budget.json API #10617

Open khempenius opened 4 years ago

khempenius commented 4 years ago

Feature wishlist (not comprehensive):

Discussed here: https://github.com/GoogleChrome/lighthouse/pull/10579

WebCloud commented 4 years ago

Hello @khempenius! One of the things that me and my team have been trying to get done is to closely monitor our custom metrics through lighthouse reports. One possible great addition to the budget.json would be to be able to set a budget for user-timings for that purpose. That way we can assure those metrics don't degrade without any warning 😄.

khempenius commented 4 years ago

Hi @WebCloud, Thanks for the suggestion - this is a great idea. I created a issue for this (though tbh I've been bad at tracking things in Github rather than my head).

More broadly speaking, I think this is a good example of a usage pattern that the new budget.json API needs to address: the syntax for specifying budgets of things like user timings or file size where both a name (performance mark name, file name) and a metric (user-timing, file-size) needs to be supplied.

thejimbirch commented 3 years ago

Hi,

Developer here looking into budgets for the first time today at the request of a consultant. What I found not available from their request was:

  1. The ability to set a requirement on a total score like Lighthouse Page Speed Score > 90. We can of course work around this by having the test totally fail if it doesn't reach that number.
  2. First Input Delay (FID)
  3. Time to Interactive (TTI)
  4. Number of DOM elements. (This may be "resourceType": "total")
  5. HTML Requests (iframes) (This may be "resourceType": "third-party")

Thanks for a great too and for continuing to improve it!