"Preconnect to required origins" should not come up

[cihati]

Provide the steps to reproduce

1. Run LH on https://fatllama.com

What is the current behavior?

It shows this suggestion.

What is the expected behavior?

It doesn't show this suggestion, as I already preconnect to 5 domains in the homepage:

    <!-- preconnect 5 most costly connections https://www.webpagetest.org/forums/showthread.php?tid=15317 -->
    <link rel='preconnect' href='//api.segment.io' />
    <link rel='preconnect' href='//stats.pusher.com' />
    <link rel='preconnect' href='//m.stripe.com' />
    <link rel='preconnect' href='//www.google-analytics.com' />
    <link rel='preconnect' href='//js.intercomcdn.com' />
    <!-- preconnect end -->

According to #3106 , no more than 5 preconnections should be done for best performance. LH asks me to do a lot more:

Environment Information

• Affected Channels: DevTools
• Lighthouse version: Chrome Version 70.0.3538.110 (Official Build) (64-bit)
• Node.js version:
• Operating System: MacOS High Sierra

Related issues
#3106

[patrickhulce]

Thanks for filing @cihati! Some good news/bad news

Looking at the webpagetest results for your page, it looks like not all of the preconnect directives are being respected by Chrome. 😢

In latest version of Lighthouse I just tested though, we're not telling you to preload the ones that are successfully being preloaded in the WPT results though 😃

I think we'll fix this by fetching the links in your HTML to double check 👍

[cihati]

Thanks for the quick reply, @patrickhulce

[wardpeet]

it's more or less a duplicate of #5932.

Thanks for filling a bug

[patrickhulce]

Thanks @wardpeet I thought I remembered something like this, but I couldn't find it in the moment :)

Closing in favor of #5932

[nicolaskopp]

made some more observations here: #5932