Patrick Hulce

Oh I remember my third now :) I want something even stronger than that. I want an audit that fails too many preloads at once on mobile.

Thanks for the extra case @dvelasquez! I'm pretty sure Lighthouse would never suggest the developer to preload that case today because it's already discoverable from the main document. A separate...

I'm not sure that advice can be so broad as to always apply, which is exactly what we're trying to back away from here, even if it's absolutely true the...

More discussion offline, the current plan here is: - Move all preload audits to not applicable until the [preload bug fix](https://bugs.chromium.org/p/chromium/issues/detail?id=788757) is validated. Once validated... - Introduce an audit that...

Update here after syncing up with @pmeenan 1. Preload is safe to use after Chrome 95 (will not skip queue), other browsers are already good here 2. Order still matters...

> Do we auto connect to iframes but need to add SWs as well? We autoconnect to any target that gets sent our way through autoattach but we only listen...

Thanks for filing @paales! This is a great idea! It's important to note what Lighthouse is actually flagging here though. The breakpoint for this image that gets selected is the...

> Lighthouse is flagging my 'upgraded' images because i can not detect a slow connection The size explanation was attempting to clarify that this is not lighthouse's intention. A site...

> this would be a breaking change right I would consider it a breaking change, yeah. > if we didn't match what moto g4 is...what's the point of labelling our...

@iDVB we don't think this is a Lighthouse problem but rather a Chrome issue in particular environments (PSI being the environment discussed in this issue). Are you saying in a...