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.4k stars 9.39k forks source link

Complexity level on opportunities result #10428

Open tyohan opened 4 years ago

tyohan commented 4 years ago

We just had a Lighthouse hackathon, which is about several teams compete to fix their performance metrics. The hackathon was very short, only around 3 hours.

One of main struggle from the team was about deciding which opportunities they should work on. We asked them to check the guidance how to fix it, and decide which one they can do within 3 hours, but some of developers can't decided especially if they never work on performance optimisation before.

So we check each of the result from the teams and suggest them the easiest opportunities based on our experiences. For example image related issue is one of the easiest to fix.

So an idea, if possible can we have some kind like complexity level on opportunities results? So instead just a saving time for each opportunity, we can add also how complex to fix it. Let say hard, medium, and easy to fix. I know this complexity level is a bit subjective, but at least something that can help them to decide which one to handle first.

May be the layout could be like this image

Thanks

patrickhulce commented 4 years ago

Great suggestion @tyohan! One tricky bit with complexity estimation is that it can vary wildly depending on how the site is built, who controls the keys to server configuration, etc. But I agree it'd be super useful information to surface!

Maybe we can get some design eyeballs on this to come up with a way to communicate a difficultly range here and be a little more descriptive in the docs about it?

patrickhulce commented 4 years ago

We would like to pursue this in our next iteration of opportunity design, but that refresh is likely a ways off.

tyohan commented 4 years ago

I'm happy to test the design with some partners that I work with. We can ask them which one they're prefer to help them choose which opportunities they should prfioritize. Let me know if anything I can help from developers/partners side.

connorjclark commented 3 years ago

We're considering adding this to the report in this manner: some iconography (3 squares, 1-3 of which are shaded in) in between the "1.2 s" and the "v" carrot).

I'll start a spreadsheet with all our opportunities and crowdsource amongst us a difficulty score :)