Complexity level on opportunities result

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

Thanks

Start from the opportunities results interface described in the issue and review how opportunity saving time is currently presented. Define how easy, medium, and hard complexity should be assigned and displayed, then verify that the results help users choose work within a short hackathon.

Written by the indexing model from the issue text.