I'm having the same issues since upgrading from Big Sur to Monterey on my MacBook Air 2020 (Intel).
A typical Chrome browser user.
Normally a complete reboot resolves the slow / loss of connectivity WiFi issue. I particularly experience this when attempting to play / streams videos on several websites, one being such as YouTube for example.
Also, i never had the "Share Mac Analytics" / "Improve Siri & Dictation", nor "Share with App Developers" options checked, under System Preferences > Security & Privacy > Analytics & Improvements, as others have suggested. So i can clearly rule these particular configurations out as being the root cause of the WiFi issues since the upgrade to MacOS Monterey.
I also tried other options, such as PRAM / SMC reset, Renew DHCP lease, clear network configuration files and let the OS regenerate fresh files in case there's some incompatibilities with previous Big Sur configurations. But, nada.
Just did an internet speed test on the upgraded MacBook Air, and it looks normally, maxed out, which is good. And for now it seems that things look normal on Safari, and Firefox where sites like YouTube is streaming videos without any buffering this morning, for now.
And so this suggests to me that the system is somehow severely interfering with the packet data from the connection down to the Chrome browser(?).
However, i have another device; MacBook Pro 2019 (Intel), which is still on Big Sur, and the Google Chrome browser is on the same perfect home network connection and browser version too (Chrome version 96), where Chrome runs sites (eg, YouTube streams) seamlessly without connectivity issues over on Big Sur.
Is Apple now throttling the connection to the Google Chrome browsers now on MacOS Monterey? Coercing us to use non-Chrome browsers perhaps, such as Safari / Firefox? Then that would be a bigger issue if that's the case.
Has anyone come across similar specific issues, specifically with Google Chrome on MacOS Monterey? If so, have you found a long lasting solution? Please share!
Nevertheless, this is clearly an underlying software issue somewhere, and should surely be fixed.