Defaulting to "Good 3G" is too strict and might be better to elevate to "Regular 4G"

[enriquegh]

Summary
Trying my site on speedo like:

speedo run https://enriquegh.com

vs trying it on Chrome I get drastic different performance score.
This seems to be because Google Chrome uses 4G instead of 3G to run the tests.

Action items
To make sure Lighthouse Reports from Sauce and Google Chrome get similar results we should probably change this to match what Chrome is doing.

[initharrington]

Lighthouse

https://github.com/GoogleChrome/lighthouse/blob/master/lighthouse-core/config/constants.js#L100
https://github.com/GoogleChrome/lighthouse/blob/master/lighthouse-core/config/constants.js#L22-L29

  mobileSlow4G: {
    rttMs: 150,
    throughputKbps: 1.6 * 1024,
    requestLatencyMs: 150 * DEVTOOLS_RTT_ADJUSTMENT_FACTOR,
    downloadThroughputKbps: 1.6 * 1024 * DEVTOOLS_THROUGHPUT_ADJUSTMENT_FACTOR,
    uploadThroughputKbps: 750 * DEVTOOLS_THROUGHPUT_ADJUSTMENT_FACTOR,
    cpuSlowdownMultiplier: 4,
  },

Slow 4G - 1.6 Mbps Down, 750 Kbps Up, ~ 150ms

SauceLabs

https://github.com/saucelabs/speedo/blob/main/src/constants.js#L115-L122

    throttleNetwork: {
        description: 'throttle network speed for your test (e.g. "Good 3G")',
        default: 'Good 3G'
    },
    throttleCpu: {
        description: 'throttle cpu speed for your test (e.g. "4" for 1/4 speed)',
        default: 4,
        type: 'number'
    },

https://docs.saucelabs.com/insights/debug/#throttle-conditions
https://docs.saucelabs.com/performance/one-page/#network-conditions-settings

Good 3G - 1 Mbps Down, 750 Kbps Up, 40ms

---

I think they are as close as they will be unless Sauce creates a Slow 4G.