Patrick Hulce

Good point @phaseOne! I'll consider this in a future update. The major blocker right now would be querying. Right now everything can be done in one go with a GROUP...

Specifically for Google Ads we can use some of google ads own classification mechanisms: https://github.com/googleads/publisher-ads-lighthouse-plugin/blob/6ece2c93a1b1de57a29ba2428279ca6f70db2fc3/lighthouse-plugin-publisher-ads/utils/resource-classification.js#L381-L389

Thanks for filing @KenjiBaheux :) Always happy to consider additional perf impact of 3Ps! While we're shifting from 1->n metrics, network bytes is another stat we've been wanting to surface...

Thanks for those additional data points! Apologies for the miscommunication @KenjiBaheux I'm already super clear on the perf impact, only the UI/UX/presentation of this data is a blocker from my...

Thanks for filing @gottfridsberg! This appears to be a bug as nothing is happening in the trace of this page. We'll look into it.  [tomasmoberg.zip](https://github.com/GoogleChrome/lighthouse/files/5276709/tomasmoberg.zip)

Two incredible things happening in this trace: 1. There's a random `RunTask` **`B`** event without a matching `E` 😱 (`RunTask` to my knowledge up until now was *always* an `X`...

Can you share your URL @shgysk8zer0 ?

No worries, glad you got it figured out @shgysk8zer0 :)

> it also doesn't seem to be great to give everyone an auto +10 boost just for including a meta viewport tag Agreed. > adding back mp-fid I like this...

Btw, I was auto-assigned this for issue triage. Is anyone else interested in picking this up or shall I implement the viewport piece for now?