Something weird is going on whenever you visit a page with Google Trends:
https://www.coingecko.com/en/coins/bitcoin
https://coin.fyi/
Tried this out but wasn't able to reproduce any slowdowns. Maybe you could try again with our background logs open, maybe on the network tab, look for excessive activity?
https://github.com/MetaMask/faq/blob/master/LOGS.md#background-logs-chrome
@flyswatter
I can easily reproduce it by going to https://coin.fyi/ (open JS console, and see that Metamask tries to initialize many many times.
And google trends won't render at all.
The problem goes away by disabling metamask. I guess Metamask is preventing Google Trends API to render itself and it becomes endless loop because The COINFYI page won't respond, won't render Google Trends and Metamask is continuously trying to initialize.
MetaMask initialization complete.
background.js:65853 POST https://mainnet.infura.io/metamask 502 ()
RpcSource.handleRequest @ background.js:65853
next @ background.js:58483
HookedWalletSubprovider.handleRequest @ background.js:66600
next @ background.js:58483
handleRequest @ background.js:66887
next @ background.js:58483
FilterSubprovider.handleRequest @ background.js:65981
(anonymous) @ background.js:10502
...
background.js:2929 SyntaxError: Unexpected end of JSON input


The multiple initializations is because metamask is also injected into iframes (intentionally).
Though, we should not be interfering with google trends widget - that is indeed a bug.
Hey guys how is the progress?
Closing old issue. Seems that it is no longer an issue on https://coin.fyi/. Will reopen if the issue persists.
Most helpful comment
@flyswatter
I can easily reproduce it by going to https://coin.fyi/ (open JS console, and see that Metamask tries to initialize many many times.
And google trends won't render at all.
The problem goes away by disabling metamask. I guess Metamask is preventing Google Trends API to render itself and it becomes endless loop because The COINFYI page won't respond, won't render Google Trends and Metamask is continuously trying to initialize.