핵심
A page is not healthy just because the server returns 200. The browser still has to load, hydrate, fetch data, and render content.
어떻게 동작하나요
FixWeb listens for console errors, request failures, and low-text renders while the headless browser loads each crawled page.
피해 범위
Runtime failures can break forms, analytics, menus, personalization, and content extraction across entire templates.
// fixweb가 어떻게 테스트하나요
FixWeb가 어떻게 테스트하나요
The crawler captures console error/warning messages, failed request URLs, response status, and rendered text volume.
확실한 방어
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.