Here are a few troubleshooting steps that might help pinpoint and resolve the cause:
Disable or Remove Extensions
Since Incognito mode typically prevents extensions from running (unless explicitly allowed), one or more installed extensions might be causing the unresponsive page. Try disabling all extensions on a test device and reload the page to see if it helps.
Check Chrome Policies / Admin Console Settings
If these are managed Chromebooks, there could be a policy in place that interferes with the site’s resources. In the Google Admin console, review any content filtering, JavaScript blocking, or security policies set on the organizational unit (OU) for those devices.
Clear Browsing Data (Cache & Cookies)
Accumulated browsing data sometimes leads to unusual behavior. Clearing cache and cookies often helps eliminate stale resources or partial updates that might be causing the site to hang.
Test on an Updated Chrome OS
Make sure the Chromebooks are running the latest version of Chrome OS. Occasionally, known browser or OS bugs are patched in newer versions.
Look at the Console Logs for Errors
If possible, open the DevTools (Ctrl + Shift + I) and look at the Console tab or the Network tab when the page starts becoming unresponsive. This can reveal which resource or script is failing or stuck.
Reset Chrome Settings (if viable)
If everything else fails, resetting Chrome settings on a test device can help. This reverts many browser configurations to their defaults, which might eliminate any unusual or hidden configuration issue.
Because incognito mode works, the issue is likely something local to each user profile (extension, cache, or policy). Walking through the above steps—especially temporarily turning off extensions and reviewing policies—tends to isolate the culprit pretty quickly. If you find that a specific Chrome extension or a particular policy is at fault, adjusting or removing it should fix the unresponsiveness in the normal browser session.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article