The website https://lootup.me is horribly slow when Web Shield is enabled. It’s not blocked, but each page takes like 5 minutes to load. It loads instantly as soon as I disable Web Shield.
Adding an exception is useless since the problem is not that Avast blocks the website.
I’ve tested Edge and Chrome on Windows 10 with everything up-to-date.
The Web Shield is an activity based scanner (so there must be a lot of background activity going on.
As an Avast User and not having a membership I can’t test by browsing.
In particular look at the external links 436 and also the 1 potentially suspicious item (though as you say Avast isn’t alerting).
I don’t know where you are setting the exception or what you have entered ?
See attached screenshot (click to expand) for an example of one I have set before and where (Avast UI > Menu > Settings > General > Exceptions. The exception is for the webshield not to scan it. That said because there are so many external sites I don’t know if the wildcard * (see image) at the end of the primary URL would also stop the 3rd party links from there.
However, in doing this you are excepting any risk in having Avast not scan that site.
VirusTotal isn’t, though the numbers have reduced to one considering it suspect still ‘Quttera’, note Avast doesn’t do the on-demand scan of a website in the VT checks it only checks live checks at user level.
So far you haven’t indicated what the format of the exception is, which is why I posted the image as a hint, it needs the /* at the end of the url
For example hXXps://lootup.me/* and hXXp://lootup.me/* (note the XX is only there to replace tt so the link isn’t active. the http one I put there as if there was mixed content http and https you need both exclusions.
Avast has no control over the sites content or the external links (436) of the site. If this meant effectively excluding the site from scanning it could be putting users at risk without them having knowledge of the exception or other method, means they could be at risk.
As an Avast user I’m not prepared to go down that path on a live system.
Problem solved! Turns out my ISP has an opt-in phishing/malicious URL protection feature that I had enabled and somehow it was interfering with Avast’s Web Shield.