Website calculator behaves differently when AVG Secure Browser shields are enabled

Hello everyone,

I’m trying to diagnose a browser-specific issue that appears to occur only when testing through AVG Secure Browser.

The website being tested is:

(URL removed by Admin)

One section of the site contains an interactive project estimation tool that updates costs dynamically based on user selections. During testing, I noticed inconsistent behavior that doesn’t appear in Chrome, Edge, or Firefox.

Observed behavior:

  • The page loads normally.

  • Dynamic calculation fields occasionally stop updating after several input changes.

  • Some values refresh only after a full page reload.

  • Browser refresh can produce different results than the previous session.

  • Developer console does not show obvious JavaScript errors.

  • The issue appears intermittent rather than permanent.

Troubleshooting already completed:

  • Browser cache cleared.

  • Cookies removed.

  • Testing in private mode.

  • JavaScript validation completed.

  • CDN cache verified.

  • Different network connections tested.

  • Browser extensions disabled.

  • Multiple devices tested.

What makes troubleshooting difficult is that the behavior seems to occur more frequently when browser privacy and protection features are active.

My questions:

  1. Has anyone seen dynamic web forms behave differently in AVG Secure Browser compared to standard Chromium browsers?

  2. Can privacy shields, anti-tracking features, or script protection affect real-time calculation updates?

  3. Is there a recommended method for identifying which browser protection component may be blocking part of a page’s functionality?

  4. Are there diagnostic tools inside AVG Secure Browser that help identify blocked scripts or delayed page execution?

  5. Has anyone encountered inconsistent form calculations caused by browser security settings rather than application code?

Because the website relies heavily on user-generated project estimates and real-time updates, ensuring consistent browser behavior is important before further development work.

Any suggestions would be greatly appreciated.

Thank you.

This sounds like it could be related to AVG Secure Browser’s privacy protections rather than the calculator logic itself. Since the behavior changes when the shields are enabled and doesn’t produce obvious console errors, I’d compare the page with the protection features disabled one at a time rather than disabling everything at once.

It may also help to monitor the browser’s Network and Console tabs while reproducing the issue and check whether any JavaScript, XHR/fetch request, or third-party resource is being blocked or delayed. Comparing the same interaction with Shields enabled versus disabled could help identify the specific component responsible.

If AVG provides a blocked-content or pr