Troubleshooting

If a replay looks “broken” (missing styles, missing images, strange redirects, or a page that doesn’t match what users saw), the most common cause is that some website resources can’t be fetched reliably outside of a normal browser session.

Revisit tries to store the page and its assets so replays stay stable over time. If a site blocks automated downloads, the saved copy may contain placeholders or security pages instead of the real files.

Common symptoms

Missing styles: the replay is unstyled, fonts are wrong, or layout looks “raw”.
Missing images/icons: broken images, missing logos, missing background images.
Unexpected page content: a login page, a “verify you are human” page, or a redirect screen appears in place of the real asset.
Works sometimes: replays look fine for some sessions but not others (often due to rate limits or bot protection rules).

Why this happens

Bot protection / WAF challenges

Some sites protect assets behind bot checks (WAFs, captchas, “security challenge” pages). When a protected file (like a CSS file) is requested by an automated system, the site may return an HTML challenge instead of the asset.

Assets require an authenticated session

If CSS/images/fonts are only accessible after login (or require session cookies), they may not be downloadable later for stable storage.

Network restrictions

IP allowlists, geo restrictions, VPN-only environments, or strict rate limits can block asset downloads.

How to fix it (customer-side checklist)

1) Allow access to public assets

Prefer public/static hosting for CSS, JS, fonts, and images (no login required).
Avoid “verify you are human” challenges for static files whenever possible.

2) Configure your security layer (WAF/CDN)

Allowlist Revisit’s traffic (recommended) so security checks don’t replace assets with challenge pages.
Disable bot checks for static asset paths (for example: /assets/, /static/, *.css, *.woff2).
Reduce aggressive rate limiting for static assets.

Tip: If you use Cloudflare / Akamai / Imperva / Sucuri / Wordfence or similar tools, check whether they’re challenging “non-browser” requests for asset URLs.

3) Test with a clean environment

Try an incognito window and ensure key assets load without login.
Check staging vs production: staging environments often have extra protection that breaks stable asset access.

Still stuck?

Contact support and share the affected page URL and approximate session time. We can help identify which resources are being blocked.

Contact Support