Hydration
Server and client disagree? You’ll know where.
React #418–#425, Next.js crashes and Vue/Nuxt mismatches. Public source maps trace each one to the component and line.
A real browser loads your site and records every crash, hydration mismatch, broken link and layout collision. Each one comes traced to the file behind it.
TypeError: Cannot read properties of undefined (reading 'price')
checkout.js:212
Unhandled rejection: Failed to fetch /api/cart
cart.js:48
Widget config missing, falling back
widget.vendor.io
What it catches
HTML-only crawlers never run your JavaScript. BugViso runs all of it, then watches what breaks.
Hydration
React #418–#425, Next.js crashes and Vue/Nuxt mismatches. Public source maps trace each one to the component and line.
Console
Uncaught exceptions and promise rejections, split first party vs. third party, grouped across pages.
Visual regression
SSIM against your approved baseline. Video, carousels, ads and cookie banners are masked.
Layout
Overlapping buttons and text cut off by overflow. Ellipsis and line-clamp count as intentional.
Links & network
404s, soft 404s and failed CORS preflights. Broken internal links come with the page you meant.
Signal, not noise
Flip the switch to see what the report keeps, and why the rest goes.
9 errors · one page load
Scoring
Every penalty is capped, so one noisy script can’t sink your grade.
Finding → fix
AI writes each fix for your actual code, and it ships in the PDF right next to the finding.
Detected
src/components/OrderTime.tsx:18
Why it matters
The server rendered 09:41 UTC; the browser rendered 14:41 local. React discards the server HTML and repaints the tree.
Hurts LCP & CLSFix · in your PDF
tsxfunction OrderTime({ at }: { at: string }) {
const [label, setLabel] = useState<string | null>(null)
// Format in the visitor's timezone after hydration
useEffect(() => setLabel(new Date(at).toLocaleTimeString()), [at])
return <time dateTime={at}>{label ?? at.slice(11, 16)}</time>
}Server and client markup match. #418 is gone.
Where it lands
Every finding, ranked, with AI-written code.
One click makes today’s layout the reference.
Catch the regression the deploy after it ships.
Raw findings for your tracker or tests.
FAQ
React throws #418 when the HTML the server sent does not match what the browser renders during hydration. Common causes are formatting dates in the visitor’s timezone, reading window or localStorage during the first render, Math.random() or Date.now() in markup, and invalid HTML nesting. Move browser-only values into useEffect so the first client render matches the server.
React’s minified error codes #418 to #425 (including the Suspense hydration failures #419, #421, #422 and #424), unminified React messages, Next.js “client-side exception” crashes and Vue/Nuxt hydration mismatch warnings. Next.js, Remix and Gatsby are covered because the errors come from React itself.
Yes, when your source maps are publicly reachable. BugViso downloads the map for the bundle that threw and traces the minified position back to the original file, line and component. Without public maps you still get the bundle URL and line.
Each scan screenshots the page at 1440, 1024, 768 and 390 px wide. The first scan becomes the baseline, and later scans are compared to it with SSIM (structural similarity). Video, carousels, ads and cookie banners are masked so they never count as changes. You approve a baseline from your results, and only a change from an approved baseline lowers the score.
No. Errors are split into first party and third party by the host that threw them, and third-party errors can cost at most 3 points. Failed resource loads are counted once as network failures, known browser noise such as the ResizeObserver loop message is dropped, and the same error on many pages is grouped into one entry.
Every link and image found on the page, checked 50 at a time. Pages the crawl already loaded successfully are not requested again. Pages that return 200 but read as “not found” are flagged as soft 404s, broken internal links come with the closest live URL as a suggested fix, and sites that block automated requests are marked unverified instead of broken.
One URL. Results in about five minutes.