Tech Bulletin: Page Unresponsive issue

Here are a few troubleshooting steps that might help pinpoint and resolve the cause:

• Be sure to whitelist: arktest.org, rollbar.com, pusher.com, googletagmanager.com, tagmanager.google.com

• For Chromebooks, activate Kiosk Mode for testing and simply add the ARK Student login URL to that kiosk (test.arktest.org/student_login): https://support.google.com/chrome/a/answer/3316168?hl=en  or https://support.google.com/chrome/a/answer/9781496?hl=en&ref_topic=6228580&sjid=7538436065119254089-NA

• Add websites or PWAs to kiosks

  1. Sign in with an administratoraccount to the Google Admin console.

     If you aren’t using an administrator account, you can’t access the Admin console.

  2. Go to Menu Devices > Chrome > Apps & extensions > Kiosks.
  3. (Optional) To apply the setting to a department or team, at the side, select an organizational unit. Show me how
  4. Point to Add and click Add by URL .
  5. Enter the URL (test.arktest.org/student_Login) and click Save.

• We've also developed a "light" testing page for the school that should allow you to test smoothly. The only difference is that this will disable some of the auto-update features - most certainly the audio player for students and the "Progress Meter" for the testing dashboard for the Teacher. The teacher can still update this page by simply refreshing the browser page manually. Please ping our Help Desk at help@arktest.org or through your Help button on ARK.

Alternatively:

1. 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.

2. 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.

3. 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.

4. 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.

5. 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.

6. 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.