Network.enable timed out. Increase the 'protocolTimeout' setting in launch/connect calls for a higher timeout if needed.

### FAQ

- [x] Yes, my issue is not about [variability](https://github.com/GoogleChrome/lighthouse/blob/main/docs/variability.md) or [throttling](https://github.com/GoogleChrome/lighthouse/blob/main/docs/throttling.md).
- [x] Yes, my issue is not about a specific accessibility audit (file with [axe-core](https://github.com/dequelabs/axe-core) instead).
- [x] Yes, my issue is not answered by [other FAQs](https://github.com/GoogleChrome/lighthouse#faq).

### URL

vivanomada.com

### What happened?

```
Channel: DevTools
Initial URL: https://vivanomada.com/
Chrome Version: 138.0.0.0
Stack Trace: kt
at (devtools://devtools/bundled/third_party/puppeteer/puppeteer.js:111:829)
at new Nr (devtools://devtools/bundled/third_party/puppeteer/puppeteer.js:111:871)
at Or.create (devtools://devtools/bundled/third_party/puppeteer/puppeteer.js:111:56)
at s._rawSend (devtools://devtools/bundled/third_party/puppeteer/puppeteer.js:121:773)
at jr.send (devtools://devtools/bundled/third_party/puppeteer/puppeteer.js:116:561)
at Hn.addClient (devtools://devtools/bundled/third_party/puppeteer/puppeteer.js:318:657)
at Kn.initialize (devtools://devtools/bundled/third_party/puppeteer/puppeteer.js:323:2161)
at #Kn (devtools://devtools/bundled/third_party/puppeteer/puppeteer.js:353:4778)
at ls._create (devtools://devtools/bundled/third_party/puppeteer/puppeteer.js:353:1450)
at devtools://devtools/bundled/third_party/puppeteer/puppeteer.js:363:2545
```D

### What did you expect?

lighthouse to run

### What have you tried?

try a few times

### How were you running Lighthouse?

PageSpeed Insights, Chrome DevTools

### Lighthouse Version

138.0.0.0

### Chrome Version

138.0.0.0

### Node Version

_No response_

### OS

_No response_

### Relevant log output

```sh

```

Start by reproducing the failure for vivanomada.com through PageSpeed Insights or Chrome DevTools with Lighthouse 138.0.0.0 and Chrome 138.0.0.0, then inspect the bundled Puppeteer stack around Network.enable and the launch/connect calls mentioned in the title. Done means the cause is identified and Lighthouse runs successfully or the missing reproduction details are documented.

Written by the indexing model from the issue text.