I am experiencing a serious and ongoing technical issue related to protection and security on my Snow Day Calculator website, and I am posting here to understand whether AVG or similar security solutions could be contributing to the problem. The website is designed to calculate the probability of school snow days based on user inputs such as location, snowfall estimates, temperature, and timing. While the site works correctly in development and on some user devices, a growing number of visitors report that the calculator either fails to load, does not produce results, or behaves unpredictably when accessed on systems protected by AVG.
The most common problem reported is that the calculator interface loads partially or not at all. In many cases, users see the page layout and input fields, but the calculation results never appear after submitting data. Some users report warning messages from their antivirus software, while others experience silent failures where nothing happens after clicking the calculate button. Refreshing the page or switching browsers sometimes resolves the issue, but not consistently, which suggests that certain scripts or network requests may be blocked or interrupted by security protection mechanisms.
Another major concern is that AVG appears to flag or restrict some of the JavaScript files or API calls used by the Snow Day Calculator. The site relies on client-side JavaScript and external APIs (such as weather data sources) to process calculations in real time. On systems with AVG enabled, these API calls may be delayed, blocked, or modified, leading to incomplete calculations or outdated results. From the user’s perspective, this undermines trust in the calculator’s accuracy and reliability, even though the backend logic itself is functioning correctly.
From a technical standpoint, the website uses HTTPS, standard JavaScript frameworks, and well-known APIs, and it does not collect sensitive personal data beyond basic location input. Despite this, some users report AVG pop-ups related to web shield protection, script scanning, or suspicious behavior detection. This raises concerns that certain heuristic or behavioral protections may be misinterpreting normal calculator functionality—such as rapid calculations, repeated API calls, or dynamic DOM updates—as potentially unsafe activity.
I am also worried about false positives and reputation-based blocking. Since the Snow Day Calculator website is relatively new, it may not yet have an established reputation in AVG’s threat intelligence systems. This could result in aggressive blocking or warnings, especially if users are accessing the site from school networks or shared devices. I want to ensure that my site is properly recognized as safe and that legitimate users are not discouraged or prevented from using it due to security warnings.
I would greatly appreciate guidance from the AVG community on how to diagnose and resolve this type of issue. Are there recommended steps for testing website compatibility with AVG protection, submitting a site for false-positive review, or adjusting site behavior to reduce the chance of being flagged? Any advice on best practices for building interactive calculator websites that work reliably alongside antivirus and web protection tools would be extremely helpful in ensuring that my Snow Day Calculator remains accessible, trusted, and fully functional for all users. Very sorry for long post!