Remove any software programs that may be affecting Chrome.
If you repaired an extension but it's still corrupted, a suspicious program might be changing this extension's files. Next to “Allow this extension to read and change all your data on websites you visit,” change the extension’s site access to On click, On specific sites, or On all sites. Allow site access: On the extension, click Details.Fix corruptions: Find a corrupted extension and click Repair.Allow incognito: On the extension, click Details.Turn on/off: Turn the extension on or off.
At the top right, click More More tools Extensions.If the extension is trusted by Enhanced Safe Browsing, click Add extension to complete the installation.To abort the installation, click Close.
However, I would check CRL configuration in Chrome. You obviously, as the best of us, did not mention your Chrome version, so it hard to say if it was an issue or is still an issue. Turns out the browser was delaying because of processing Certificate Revocation Lists because of the nature of our SSL certs.
We had used the infamous ipsCA authority because they were free for educational institutions, but eventually pissed off Firefox with their shadiness and OCSP checking of their certs was the culprit. With Firefox (I know, I know, I can read, point forthcoming), a bunch of people had issues while Internet Explorer users (if you can believe it) did not. For this to be an issue, you need to confirm the issue is only with https pages. We had a very similar issue at a facility I previously worked at, but with Firefox. Tl dr Check how Chrome handles certificate checking and revocation.