The hook
A page is not healthy just because the server returns 200. The browser still has to load, hydrate, fetch data, and render content.
How it works
FixWeb listens for console errors, request failures, and low-text renders while the headless browser loads each crawled page.
The blast radius
Runtime failures can break forms, analytics, menus, personalization, and content extraction across entire templates.
// how fixweb tests for it
How FixWeb tests for it
The crawler captures console error/warning messages, failed request URLs, response status, and rendered text volume.
Ironclad defenses
Fix thrown production errors, broken asset paths, failed API calls, CORS/load failures, and blank shell states. Add browser-level smoke tests for important templates.