Confirm JavaScript is running
Open the Full Browser Test. If the cards stay empty, buttons do nothing, or the results never populate, JavaScript is blocked. For a second signal, run the JavaScript Speed Test. You should see a benchmark progress indicator and a score at the end.
Common symptoms when JavaScript is blocked:
- A site says "enable JavaScript to continue"
- Buttons do nothing when you click
- Infinite spinners after login
- Checkout pages that never advance to the next step
- CAPTCHA loops even after solving
Keep the test tab open and re-check it after each fix.
Fix 1: Allow JavaScript for the site (fastest fix)
Start with site-level permission. This avoids changing global settings.
-
Chrome / Edge:
- Open the site that is failing.
- Click the lock icon in the address bar.
- Open Site settings and set JavaScript to Allow.
- Reload the page, then rerun the Full Browser Test.
-
Safari (macOS):
- Safari does not expose per-site JavaScript in the same way. Use the global toggle in the next fix.
-
Firefox:
- Firefox does not have a normal per-site JavaScript toggle. Use the
about:configfix below.
- Firefox does not have a normal per-site JavaScript toggle. Use the
If JavaScript was blocked for that domain, this is usually enough.
Fix 2: Turn JavaScript back on globally
If JavaScript is disabled at the browser level, every site breaks.
Chrome:
- Open
chrome://settings/content/javascript - Set Sites can use JavaScript to On
- Reload the problem site and rerun the Full Browser Test
Edge:
- Open
edge://settings/content/javascript - Set Allowed (recommended) to On
- Reload and retest
Safari (macOS):
- Open Safari > Settings > Security
- Check Enable JavaScript
- Quit Safari and reopen it
Safari (iPhone/iPad):
- Open the Settings app
- Go to Safari > Advanced
- Turn JavaScript On
Fix 3: Undo script blocking from extensions
Script blockers can make a site look "broken" even though JavaScript is enabled.
- Disable extensions like NoScript, strict filter modes in uBlock Origin, or privacy tools that block scripts by default.
- Test in Incognito/InPrivate where extensions are off. If the site works there, re-enable extensions one by one to find the blocker.
- If you need the extension for other sites, add an allowlist rule for the domain instead of leaving it disabled.
After changes, reload the page and rerun the Full Browser Test.
Fix 4: Check tracking protection and content blockers
Some privacy modes block scripts or critical third-party domains used for sign-in and payments.
- Firefox: Settings > Privacy & Security and set Enhanced Tracking Protection to Standard for testing. Reload the site and try again.
- Safari: turn off Content Blockers for the site (address bar aA menu), then reload.
- Brave: lower Shields for the site or temporarily allow scripts for testing.
If you are troubleshooting a bank or enterprise login, keep changes site-scoped. Avoid changing global privacy settings unless you need to.
Fix 5: Test for network or DNS-based blocking
If JavaScript files are blocked at the network level, the browser cannot run the app.
- Try the site on a different network (mobile hotspot is a fast check).
- If it works on the hotspot, your home router, DNS filter, or office proxy is likely blocking a required script domain.
- On managed networks, ask IT to allow the site’s static asset domains (CDNs) rather than bypassing security controls.
Fix 6: Check for managed device policies
Work and school devices can enforce settings that block scripts.
- Chrome: open
chrome://policy - Edge: open
edge://policy
If you see policies that mention JavaScript or content settings, only the administrator can change them. Copy the failing behavior from the Full Browser Test so IT can reproduce it.
Verify the fix
Return to the Full Browser Test and confirm results populate normally. Then retry the action that failed on the original site (log in, submit a form, complete checkout). If the site still breaks in one browser only, test in another browser profile to rule out a corrupted profile or extension set.
