No browser console errorsWhat it checks and how to fix it

What it checks

Loads the page in headless Chrome and collects everything written to the browser console. Any uncaught JavaScript exception, or more than 3 console errors, is a failure; 1 to 3 errors, or any warnings, is a warning; a clean console passes.

Why it matters

Console errors are usually symptoms of something visibly broken: a script that crashed halfway, a 404 on a bundle or font, a blocked API call, a third-party tag that no longer loads. An uncaught exception stops the rest of that script, so menus, forms or checkout can silently stop working for every visitor. They also signal to search engines rendering the page that it may not render as intended.

How to fix it

Open DevTools (F12), reload the page with the Console tab open, and fix each message starting with uncaught exceptions.

Typical causes and fixes:

• Failed to load resource (404): a missing script, stylesheet, font or source map. Fix the path or remove the reference.
• Blocked by CORS policy: the API or font host must send Access-Control-Allow-Origin for your origin.
• Refused to load ... Content Security Policy: add the source to the right CSP directive, or stop loading it.
• Uncaught TypeError: guard code that runs before the DOM element exists.

document.addEventListener("DOMContentLoaded", () => {
  const button = document.querySelector("#signup");
  if (button) button.addEventListener("click", openSignup);
});

Report production errors to an error tracker (Sentry, Honeybadger, Bugsnag) so new ones are caught before visitors notice.