Norton Safe Web and websites not loading in Chrome. What should you check?

If some websites are slow or do not load in Google Chrome, but the same pages work in Microsoft Edge, the problem may not be the internet connection itself. This is especially true when internet speed tests look normal and other online services continue to work.

This guide is mainly written for people using Norton 360 or Norton Small Business where Norton Safe Web or browser protection may be part of the troubleshooting path. It is based on a real troubleshooting pattern where some websites were slow or did not load correctly in Chrome, while Edge loaded the same pages and speed tests showed that the connection itself was not the obvious problem.

The exact root cause was not confirmed. Norton technical support helped identify a temporary workaround involving Safe Web, and my own technical opinion is that the issue may have been linked to a recent conflict or update involving Norton, Google Chrome, Windows, or a combination of them. That is not the same as proving the root cause.

The guide also covers other possible contributors, including Chrome profiles, extensions, DNS filtering, NextDNS, Malwarebytes, McAfee, older Symantec branded tools and similar web protection products. These are included as comparison points, not as claims that they caused this specific issue.

Use the links below to jump to the section most relevant to your question.

• Quick checks before changing security settings
• Why Norton Safe Web is relevant to this problem
• Why Edge can work when Chrome does not
• Could a Chrome profile, extension or setting be involved?
• Could Chrome’s on device AI feature be the cause?
• Could DNS filtering or NextDNS be blocking part of the page?
• Could Malwarebytes, McAfee, Symantec or other tools cause similar symptoms?
• Why switching off Safe Web should only be temporary
• What to record before contacting support
• When this becomes an IT support issue
• Frequently asked questions
• Supporting references
• Need help with something covered in this guide?
• Further Guidance and Support

Before changing Norton, Chrome or any other security setting, it is worth checking whether the issue is limited to one browser, one website, one computer, or one network. This helps avoid unnecessary changes and reduces the risk of weakening protection while trying to fix a loading problem.

Start with these checks.

1. 1. Try the same website in Microsoft Edge or another trusted browser.
   2. Try more than one affected website.
   3. Restart Chrome and reopen the page.
   4. Restart the computer if this has not already been done.
   5. Check whether Norton 360 or Norton Small Business is showing any warning, blocked page message, or browser protection notification.
   6. Check whether the Norton browser extension is installed and enabled in Chrome.
   7. Check whether the affected website works on another computer or phone using the same internet connection.
   8. Run a speed test, but do not rely on the speed test alone.
   9. Avoid uninstalling security software as the first step unless there is a clear reason or support guidance.

If the internet speed test looks normal but specific pages still fail, that usually points away from a simple broadband speed problem. The issue may be closer to Chrome, Norton Safe Web, browser extensions, DNS filtering, browser protection, or a recent software update.

Norton Safe Web is designed to help protect users from unsafe websites, phishing pages, scam links and malicious content. Because it checks web activity before or during page loading, it can be relevant when a website is slow, blocked, or fails to open.

Norton’s own support material includes a troubleshooting path for website access problems that involves turning Safe Web off and on. That does not mean Safe Web is always the cause. It does mean Safe Web is a valid item to check when Norton is installed and website loading behaviour changes.

In the case behind this guide, some websites were slow or did not load correctly in Chrome. Microsoft Edge loaded the same pages correctly, and speed tests suggested that the internet connection itself was not the main problem. Norton technical support helped identify a temporary workaround involving Safe Web.

The important distinction is this: a workaround is not the same as a confirmed root cause. Turning off Safe Web may change the result, but the underlying problem could still involve Norton, Chrome, Windows, recent updates, browser extension behaviour, or an interaction between more than one component.

When one browser works and another does not, the website and internet connection are not automatically the main cause. Different browsers can use different profiles, extensions, cached data, site permissions, security integrations and browser protection add ons.

Chrome may have a damaged profile, a problematic extension, cached site data, or a security extension that is not active in Edge. A security product may also interact differently with different browsers, especially where browser extensions or web protection features are involved.

This does not prove Chrome is faulty. It narrows the investigation. The useful question becomes: what is different about Chrome on this computer compared with Edge?

A Chrome profile stores browser settings, extensions, cookies, history, saved site data and other local information. If the problem follows one Chrome profile but not another, the profile itself may be part of the issue.

Possible Chrome related causes include:

1. 1. A corrupted or overloaded Chrome profile.
   2. A browser extension interfering with pages.
   3. Cached site data causing repeated loading problems.
   4. A site permission or privacy setting.
   5. A browser protection extension checking or blocking page content.
   6. A recent Chrome update changing how a browser feature behaves.

A useful test is to open Chrome with extensions disabled, use a temporary test profile, or try an incognito window. Incognito mode is not a complete clean test because some extensions may still be allowed in incognito, but it can help separate normal profile behaviour from a broader browser issue.

If the same pattern appears on several computers, a single damaged Chrome profile becomes less likely as the only explanation. In that situation, it is sensible to consider shared software, browser protection, DNS filtering, or a recent update affecting several machines.

Chrome includes support for on device AI models that can be used by browser features such as writing help, scam warnings, page summaries and tab organisation. Because these features can involve background browser activity, it may be reasonable to consider them when diagnosing unusual Chrome behaviour.

In the troubleshooting case behind this guide, this was considered because the issue appeared in Chrome while Edge loaded the same pages correctly. Internet speed tests also showed that the connection itself was not the obvious problem.

However, switching off Chrome’s on device AI feature made no difference in that case. That made this particular Chrome feature less likely to be the cause, although it did not identify the exact root cause.

This is a useful part of the troubleshooting record. A possible cause was tested and did not change the result. That means the investigation should continue rather than forcing the original theory to fit the evidence.

DNS filtering services can block known advertising, tracking, malware, telemetry or suspicious domains before the browser can connect to them. In many cases this is expected behaviour, but it can sometimes affect how a page loads if the page depends on blocked third party resources.

If only part of a page fails, or if a page hangs while trying to load external scripts, analytics, consent tools, login widgets, payment tools or support chat services, DNS filtering may be worth checking. This does not mean DNS filtering is wrong. It means the logs should be reviewed carefully before assuming the website, browser or Norton is the only possible cause.

For NextDNS or similar filtering services, useful checks include:

1. 1. Review the logs at the time the page failed.
   2. Look for blocked domains that match the affected website or its required services.
   3. Check whether the same page works when using a different network.
   4. Avoid allowing a domain unless there is a clear reason to trust it.
   5. Remember that many blocked domains are advertising, analytics, tracking or telemetry services and may not be essential to the main website.

A normal speed test does not rule out DNS filtering. Speed tests usually measure connectivity to a specific test service. They do not prove that every third party domain needed by every website is reachable.

The observed workaround in this guide involved Norton Safe Web, so Norton users are the main audience for this page. However, the wider troubleshooting principle can apply to other security products or browser protection tools.

Products such as Malwarebytes Browser Guard, McAfee WebAdvisor, older Symantec branded security tools, browser extensions, DNS filtering services and other web protection systems can also sit in the path between the browser and the website. Depending on their configuration, they may block, warn, filter, or delay page content.

This does not mean those products caused the Norton case described here. It only means that similar symptoms can sometimes come from similar layers of protection.

The safer way to investigate is to ask:

1. 1. Which browser is affected?
   2. Which security product is installed?
   3. Which browser extensions are enabled?
   4. Are DNS filtering logs showing blocked domains?
   5. Does the same page load in another browser?
   6. Does the same page load on another computer?
   7. Did the issue appear after recent browser, Windows or security software updates?

This avoids blaming one product too early and helps identify the layer that changes the result.

If turning off Safe Web allows affected websites to load, that is useful evidence. It suggests the web protection layer is involved in the behaviour, or at least part of the path that changes the result.

However, Safe Web is a security feature. Turning it off permanently may reduce protection against malicious websites, phishing attempts, scam pages or other unsafe browsing situations. For that reason, it should normally be treated as a temporary diagnostic step or a short term workaround while the issue is investigated.

A safer approach is:

1. 1. Record what changed and when.
   2. Confirm whether the same pages load with Safe Web off.
   3. Re enable the feature if instructed or once testing is complete.
   4. Check whether Norton, Chrome or Windows updates are pending.
   5. Contact Norton support or your IT support provider if the issue returns.
   6. Avoid leaving protection disabled without understanding the risk.

Security tools sometimes need updates to correct compatibility or detection problems. Browser and operating system updates can also change behaviour. This is why a temporary workaround should not be treated as a final security configuration.

If the problem continues, a short record of what happened can make support much more effective. This is especially useful where the issue may involve more than one product or update.

Record the following details where possible:

1. 1. The affected websites.
   2. Whether the websites work in Edge.
   3. Whether the websites fail in Chrome only.
   4. Whether the issue affects one computer or several computers.
   5. Whether Norton 360 or Norton Small Business is installed.
   6. Whether Norton Safe Web is enabled.
   7. Whether the Norton browser extension is installed in Chrome.
   8. Whether any Chrome extensions were recently added or updated.
   9. Whether NextDNS or another DNS filtering service is being used.
   10. Whether any Norton, Chrome or Windows updates were installed recently.
   11. Whether turning Chrome’s on device AI feature off made any difference.
   12. Whether temporarily turning Safe Web off changed the result.

This information helps separate a browser profile issue from a security software issue, DNS filtering issue, update related issue, or wider support problem.

A single website failing in one browser may be a small local problem. Several websites failing across several computers can become a wider support issue, especially in a small business or professional environment.

Further support may be needed when:

1. 1. Several users or computers are affected.
   2. Important work websites fail to load.
   3. The issue affects logins, file transfers, banking, supplier portals or cloud services.
   4. Security software needs to be changed to keep work going.
   5. DNS filtering logs are difficult to interpret.
   6. The problem keeps returning after updates or restarts.
   7. Users are tempted to disable protection permanently.

In those situations, the aim should be to identify the layer involved rather than repeatedly trying random fixes. The cause may sit with Norton Safe Web, the Norton browser extension, a Chrome profile, Chrome extensions, DNS filtering, Windows updates, Chrome updates, Norton updates, or an interaction between several of them.

Does a normal speed test prove the internet is fine?

A normal speed test shows that the computer can reach the speed test service at that moment. It does not prove that every website, DNS lookup, security check or third party page component is working correctly.

Why would Chrome fail when Edge works?

Chrome and Edge may use different profiles, extensions, cached data, site permissions and browser protection integrations. If Edge works and Chrome does not, the issue is more likely to be browser specific or related to something interacting with that browser.

Does turning off Norton Safe Web prove Norton caused the issue?

Not by itself. If turning off Safe Web changes the result, it suggests Safe Web or the browser protection path is involved. It does not automatically prove the original fault, especially where recent updates to Norton, Chrome, Windows or related components may also be involved.

Is it safe to leave Safe Web turned off?

Leaving a browser protection feature turned off permanently is not usually advisable. If it is turned off for testing or as a temporary workaround, the change should be reviewed and reversed when possible, or handled with support guidance.

Should I delete my Chrome profile?

Not as the first step. A damaged Chrome profile is possible, but deleting or resetting a profile can remove useful settings and data if it is not handled carefully. It is better to test with a temporary profile or controlled troubleshooting first.

Can DNS filtering cause only some websites to fail?

Yes. DNS filtering may block specific domains used by a website while leaving general internet access working. This can make some pages load slowly, partly load, or fail while other websites still work.

Does turning off Chrome’s on device AI feature fix this issue?

In the troubleshooting case behind this guide, turning off Chrome’s on device AI feature made no difference. That made the feature less likely to be the cause in that case, although it did not prove the exact root cause.

Can Malwarebytes, McAfee or another security tool cause similar symptoms?

They can be part of a similar troubleshooting path because many security products include browser protection, web filtering, malicious site blocking, privacy protection or allow list features. This guide does not claim those products caused the Norton case. It simply recognises that similar protection layers can sometimes create similar symptoms.

The following official references are useful when reviewing this issue:

Google Chrome Help: Manage on device Generative AI models in Chrome.

Norton Support: Unable to access websites after installing Norton 360 app.

Norton Support: Browse the Internet securely with Norton Safe Web.

Malwarebytes Browser Guard: Add websites to the Allow list in Browser Guard.

McAfee Support: Install and configure WebAdvisor.

NextDNS help and community information about logs, blocked queries and allow list behaviour.

These references support the general troubleshooting context. They do not confirm the exact cause of every case where websites are slow or not loading.

A guide can explain the issue and outline useful checks, but some situations need the actual device, account, service, website, network or supplier arrangement to be reviewed. Evening Computing can help review what is happening and advise on suitable next steps before changes are made.

This guide forms part of a broader layered security approach. For structured guidance on security and resilience planning, see our Security and Resilience page.

For information about practical implementation and ongoing support, you can review our IT services and local IT support coverage across London, Hertfordshire, and Essex.

Return to all guides

Author
Elías Sánchez
IT Support Consultant
Evening Computing
London, United Kingdom

This guide was prepared by Elías Sánchez with research and drafting assistance from AI tools. All technical content has been reviewed and adapted for clarity and accuracy.

Last reviewed
10 June 2026