What the checker captures
We load your homepage in a real Chrome browser, let it settle and record everything the browser's developer console would show, plus every network request that failed. Each problem is listed with its message, the file and the URL involved, so a developer can find it quickly.
- Uncaught JavaScript exceptions that stop scripts from running.
- Console error messages logged by your site or by third-party scripts.
- Broken files: scripts, stylesheets, images or fonts that return 404 or fail to load.
- Failed API calls — fetch or XHR requests answered with 4xx or 5xx status codes.
- Cross-origin (CORS) errors and mixed content, where an https page loads insecure http resources.
Why errors matter even when the page looks fine
A single uncaught exception can stop every script that comes after it. The page may look normal, but the mobile menu does not open, the contact form does not send, the cookie banner never records a choice or the booking widget stays empty. Visitors do not report this; they leave.
Errors also creep in silently over time: a plugin update, an expired API key for a map, a third-party service that changes its address. Because nobody on your team opens the console, they can stay unnoticed for months.
What to do with the results
Start with uncaught exceptions and failed requests on your own domain, since those are most likely to break something visible. Send the report link to your developer; the file names and messages are usually enough to locate the cause. For third-party errors, check whether you still use the service and whether its embed code is current.
Then test the critical journeys by hand: open the menu on a phone, send a test enquiry, book a test appointment. Our scan loads the page but does not click through forms, so it finds errors that occur on load, not those that only appear after interaction.
Preventing errors after updates
Most new console errors appear right after a theme, plugin or third-party script update. Run this check after every update cycle, and ask your developer or maintenance provider to include it in their routine. For sites that change often, an error-monitoring service records errors from real visitors, including those that only happen after interaction.