Why is kraken.com so
very slow nowadays? Every click that has something to do with security takes about 30 to 60 seconds. Examples:
- Entering 2FA
- Clicking Deposit
- Generate new address
- Copy address
- Withdraw
During this time, there's a process "Isolate Web Content" that takes 100% CPU. I don't know what it's doing with all this CPU time, but it makes the website almost impossible to use. A simple order that should take no more than a minute to complete now takes about 15 minutes.
I know my laptop isn't the latest model, but most sites work just fine.
I can only speak for myself but I use Kraken on a daily base since ~2016 and I see only improvements in speed and reliability (which in all honesty doesn't say too much given the timeouts and downs we were used to years ago and when you were lucky to submit an order actually within an hour or two).
For example the 2FA screen comes really instantly after submitting user/pw. Also the site loads within 1-2s after 2FA. I too use (very) outdated hardware (basically what other people kick into the trash) but I haven't experienced any notable slowdowns recently.
I generated a new DOGE address yesterday and that wasn't a problem too (3-4s IIRC).
I checked just now and everything seems to be working smoothly for me. Though deposit and withdraw (tried BTC and DOGE) take 3-4s to fully load but I understand you experience a completely different ballpark of waiting times.
BTW: I use Linux, Firefox ESR and have around 10ms network latency to kraken.com.
I have seen quite a few reports of Firefox's site isolation feature to go nuts:
https://connect.mozilla.org/t5/discussions/quot-firefoxcp-isolated-web-content-quot-is-slowly-consuming-all/td-p/1872Given this, it might be worth a try to disable site isolation to see if things improve then (though I am always more than hesitant to advice anyone to disable some security feature, so only try that if you are fully aware of the risks):
To enable Site Isolation on Firefox Beta or Release:
Navigate to about:config.
Set `fission.autostart` pref to `true`.
Restart Firefox.
^ Just checked and my FF ESR has
fission.autostart on false by default.
HTH and good luck debugging it.