// docs / what mykavo monitors //
Reducing false positives
A monitor you stop trusting is worse than no monitor. MyKavo stabilises pages before capture, normalizes the DOM, and gives you ignored selectors and screenshot masks for the regions that change by design - so alerts stay rare enough to be worth reading.
Last updated: September 20, 2026
What MyKavo does automatically
- Waits for DOMContentLoaded, for fonts where possible, and for a bounded network-quiet period - never waiting indefinitely.
- Disables CSS animations and transitions, and hides text cursors, so nothing mid-animation is captured.
- Captures at a fixed viewport, device scale factor, locale and timezone, so identical pages produce identical bytes.
- Normalizes the DOM before hashing: comments, volatile attributes, nonces and framework hydration markers removed.
- Applies a noise threshold so sub-1% visual differences are ignored rather than reported.
What you can configure
Ignored selectors
Elements matching these CSS selectors are removed before comparison entirely. Use them for live counters, "last updated" timestamps, rotating testimonials and anything personalised.
Screenshot masks
Elements matching these selectors are painted over with a solid block in the screenshot only. The mask colour is fixed, so a masked region is byte-identical between scans regardless of what was underneath. Use them for ad slots and third-party embeds you cannot control.
Baseline approval
The strongest tool of the four. Approving an expected change moves the reference point, so a redesign produces one round of changes you approve rather than a permanent stream of differences against a state that no longer exists.