TL;DR
To check a website for errors, load it the way a visitor does, on desktop and on a phone, and look for five kinds of fault: broken pages and links, failed scripts and console errors, mobile layout problems, slow loading, and accessibility issues, plus missing titles and descriptions for search. The free Website Bug Checker does this in a real browser: it visits your homepage and up to four key pages on desktop and mobile and lists what it finds by priority. Use the 20-point checklist below before any launch or redesign.
| Error type | What visitors notice | How to check |
|---|---|---|
| Script and console errors | Buttons that do nothing, forms that hang, widgets that never load | Browser console, or a bug checker |
| Failed files | Missing styles, fonts or images | Browser network panel, or a bug checker |
| Broken links | Error pages | Broken Link Checker |
| Mobile layout | Sideways scrolling, tiny text, buttons too small to tap | Test on a real phone, or a bug checker at phone width |
| Slow loading | A blank screen for several seconds | Largest Contentful Paint over 2.5 seconds |
| Accessibility | Unlabelled form fields, buttons with no name | An accessibility scan such as axe |
| Search basics | Missing title or description | Meta Tag Checker |
| Security warnings | "Not secure" in the browser bar | Check the certificate and look for mixed content |
Why websites break without anyone noticing
Most website errors are invisible from the inside. You visit your own site on a fast laptop with a warm cache, already logged in and already knowing where to click. Visitors arrive on a phone, on mobile data, from an ad, with ad blockers and old browsers. A chat widget that throws an error, a font that fails to load or a button pushed off screen on small phones can go unnoticed for months while quietly costing sales.
How to check a website for errors
1. Run an automated bug check
The free Website Bug Checker opens your site in a real Chromium browser, on desktop and on a phone-sized screen. It visits the homepage and up to four key pages it finds in your menu, such as pricing, products, contact or sign-up, and reports:
- page errors and console errors, split into your own code and third-party widgets;
- scripts, styles, fonts and other files that fail to load;
- links on the homepage that return errors;
- mobile problems: sideways overflow, a missing viewport tag, small text and tap targets under 24 pixels;
- slow loading, measured as Largest Contentful Paint over 2.5 or 4 seconds;
- serious and critical accessibility issues, unlabelled fields and controls with no name;
- mixed content and certificate errors;
- missing titles and descriptions, and images without alt text.
It merges repeats across pages, adds screenshots and puts the fixes in priority order. It only reads your pages and never fills in or submits forms.
2. Open the browser console yourself
In Chrome, right-click any page, choose Inspect, and open the Console tab. Red messages are errors. Reload the page and click through the main actions (menu, add to basket, contact form) while you watch. Then open the Network tab, reload, and look for rows in red: those are files that failed to load.
3. Test on a real phone
Automated checks catch a lot, but spend five minutes on your own phone too. Try the menu, scroll every key page, tap every main button and fill in your contact or checkout form. Look for anything you have to pinch, zoom or scroll sideways to use.
4. Check what search engines see
Use the free Meta Tag Checker for titles, descriptions and stray noindex tags, and the Indexability Checker to confirm Google can index your key pages. Then check Search Console for errors Google has found.
The 20-point website error checklist
Loading and links
- Every key page returns a 200 status and loads.
- No broken links on the homepage, menu or footer.
- No redirect chains on key URLs (check with the Redirect Checker).
- The 404 page is helpful and returns a real 404 status.
Scripts and files 5. No red errors in the browser console on key pages. 6. All styles, fonts and images load. 7. Third-party widgets (chat, reviews, booking, analytics) load without errors. 8. Forms submit and show a clear confirmation (test these by hand).
Mobile 9. No sideways scrolling at phone width. 10. The viewport tag is set. 11. Text is readable without zooming. 12. Buttons and links are big enough to tap, with space between them.
Speed 13. The main content appears within about 2.5 seconds. 14. Images are compressed and sized for the screen.
Accessibility 15. Every form field has a label. 16. Every button and icon link has an accessible name. 17. Images have alt text that describes them.
Search and security 18. Every page has a unique title and meta description. 19. No noindex on pages you want found. 20. HTTPS everywhere, a valid certificate and no mixed content.
How to prioritise fixes
Fix in this order: anything that stops a visitor buying or contacting you (broken forms, checkout errors, failed scripts on key pages), then mobile layout faults, then speed, then accessibility and search issues. A single error on your checkout page matters more than a dozen small warnings on an old blog post.
Check again after every change
Most errors arrive with a change: a new plugin, a theme update, a new tracking script or a redesign. Run the bug check after each one, and on a regular schedule even when nothing seems to have changed, because third-party widgets update on their own.
Where Ergora helps
The free checkers show what is wrong today. If your site's code lives on GitHub, Ergora's Developer pack and its Developer specialist can help you work through the fixes. For search, the SEO specialist in the Content pack connects to Google Search Console and shows the pages losing clicks and whether each page is in Google's index.
Verdict: Run the free Website Bug Checker before every launch and after every significant change, test the forms by hand on a phone, and fix anything that blocks a sale first.
Frequently asked questions
How do I check my website for errors?
Run an automated bug check in a real browser on desktop and mobile, open the browser console on key pages to look for red errors, test forms by hand on a phone, and check Search Console for errors Google has found.
What is a website error checker?
A tool that loads your site like a visitor and reports problems such as script errors, failed files, broken links, mobile layout faults, slow loading and accessibility issues.
Why does my website work for me but not for customers?
Your own browser has cached files, saved logins and maybe a fast connection. Visitors arrive on different devices, browsers and networks, and third-party widgets can fail for them. Test in a private window and on a phone over mobile data.
How often should I check my website for errors?
Before any launch, after every plugin, theme or code change, and at least monthly, since third-party scripts change without warning.
See the Developer pack, with 50% off your first month.