Fix guides · UX & conversion

How to fix “Browser errors were logged to the console”

JavaScript errors and failed requests that the browser reports while your page loads. How to find what's broken and who can fix it.

Time to fix
15–60 minutes
Skill needed
Developer
Who notices
Any visitor who uses the broken feature

Why it matters

The browser console is where the page reports problems: a script that crashed, a file that returned 404, a request blocked for security reasons.

Some errors are harmless, but many mean something visibly broken: a menu that doesn't open, a form that doesn't submit, a tracking pixel that never fires.

“An Error message means there's a problem on your page that you need to resolve.”

Chrome: Browser errors were logged to the console

Before you start

  • Your report lists each error with the file it came from. Group them by source: your theme or code, an app or plugin, or a third-party service.
  • 404 errors for missing files (an old script, a deleted image) are usually the quickest fix: remove the reference or restore the file.
  • Errors from browser extensions don't count against your site; Lighthouse runs without them.

Fix it on your platform

Shopify

  1. Errors from an app's script: update the app, check its settings, or contact its developer. Leftover code from uninstalled apps is a common source of 404s.
  2. Errors from your theme's files: check recent theme edits, or test with an unedited copy of your theme to see if the error disappears.

WordPress

  1. Update WordPress, your theme and plugins; many errors are fixed in updates.
  2. To find the cause, deactivate plugins one at a time on a staging copy (or with a troubleshooting plugin) until the error stops.

Webflow

  1. Errors usually come from custom code or embeds. Remove or fix scripts in your site and page custom code settings, then republish.

Wix

  1. Errors from your own Velo code or Custom Code settings are yours to fix. Errors from Wix's own scripts are managed by Wix; contact support if a feature is broken.

Squarespace

  1. Remove or fix code in code injection and code blocks. Squarespace suggests removing custom code temporarily (saving a copy) to see whether it causes the problem.

Next.js

  1. Hydration errors (server and client rendered different HTML) are common: avoid reading window, dates or random values while rendering.
  2. Check that every file referenced in your code and metadata exists, and that third-party scripts load with next/script.

Any other site

  1. Open Chrome DevTools → Console, reload the page and click each error to see the line that caused it.
  2. Fix or remove the failing script, and remove references to files that no longer exist.

Check that it's fixed

  • Reload the page with DevTools → Console open: no red errors should appear.
  • Re-run your StudioLNC audit: the issue should be gone.

Find every issue like this on your site

Free audit of performance, accessibility, SEO and security, with fixes for your platform.