"Uses inefficient cache policy on static assets" rule should group by path

[tomayac]

The current "Uses inefficient cache policy on static assets" list is not very actionable (excerpt of an actual audit):

Can Lighthouse try to group them by origin and path?

• Oftentimes per-origin grouping already allows users to see if they can't change things (true third-party like securepubads.g.doubleclick.net) or if they in fact can do something about it (sharded third-party like cdn.example.com).
• Based on that, per-path grouping then reveals common patterns (like cdn.example.com/assets has 30 days vs. cdn.example.com/static/icons has 24h).

[patrickhulce]

Thanks @tomayac! :)

We have discussed introducing a third party filter perhaps just a more generic origin filter could be helpful here.

[paulirish]

IMO 3P badging or favicons could make this easier to deal with. cc #4516

[connorjclark]

What if we put all the items of the same origin in a single item, and used subItems for the actual resources?

[tomayac]

I think this would work and is what I had in mind when I filed the Issue. Thanks!