diff report — https://code-rage.pages.dev/?ref=vibejam

overall pixel mismatch (default state): 0.01%
overall structural match (default state): 100.00%
states measured: 0
run at 2026-05-07T04:49:22.079Z
Two metrics are reported per viewport: (1) pixel mismatch — fraction of pixels that differ in the above-the-fold screenshot, and (2) structural match — fraction of DOM nodes whose tag/role/framer-name/child-count fingerprint lines up position-for-position. Pixel-diff is sensitive to lazy-loading timing: on sites with IntersectionObserver-driven image loads, the mirror often renders MORE content than the original (assets are local, no network latency) and the mismatch reflects that gap, not infidelity. The structural metric is timing-insensitive — if structural match is high but pixel mismatch is also high, the divergence is almost certainly load-timing rather than a real fidelity gap. Read the two together.

default state

desktop 1440×900 — 0.00% pixel diff (0 px) · 100.00% structural match · nodes orig=58 mir=58 (Δ +0)

original
mirror
diff

tablet 768×1024 — 0.01% pixel diff (65 px) · 100.00% structural match · nodes orig=58 mir=58 (Δ +0)

original
mirror
diff

mobile 390×844 — 0.03% pixel diff (85 px) · 100.00% structural match · nodes orig=58 mir=58 (Δ +0)

original
mirror
diff