Audit: false positive for preconnect/dns-prefetch suggestion

OMG. Finally moved off tumblr.com for my blog! I built a dope site but want to make The House the happiest it can be.

I’m using `link rel=preconnect" for a couple of domains, but LH re-suggests that to me as an improvement :\

Provide the steps to reproduce

1. Run LH 3.0.3 on https://ericbidelman.com

What is the current behavior?

Perf > Opportunities says that I should use dns-prefetch and/or connect to reduce RTTs to origins:

What is the expected behavior?

I’m already using preconnect for both these origins:

Not sure if the audit already does this, but we we could look at the DOM for link rel=preconnect|dns-prefetch and remove any origins users are already preconnecting to.

Environment Information

• Lighthouse version: 3.0.3

Related issues

Report: https://googlechrome.github.io/lighthouse/viewer/?gist=4bd3bf89ce0ac69319db6cf1e9b94a83

[stephen-last]

I think I’m seeing the same. The report has Lighthouse 4.0.0-alpha.1 at the top.

I’m using the Lighthouse Chrome ext:

I have some preconnect link’s in the HTML:

But Lighthouse is suggesting I add them:

[patrickhulce]

@dawsbot in this WebPageTest result (https://webpagetest.org/result/200207_1J_c1f01a929bb96dde1265c14cd44ffd56/1/details/#waterfall_view_step1) without Lighthouse involved, those origins were not preconnected, so it would appear that Lighthouse is correctly flagging this situation. It’s worth noting that Chrome started ignoring preconnect directives in slow network conditions when there too many, so we’ve changed our advice to only preconnect to the 2 most important origins in the upcoming release of Lighthouse. I’d guess this is the situation we find ourselves in now and why Brave might be still preconnecting if it’s a Chrome-specific trial.