Browser rendering

Before browser rendering

Browser rendering starts after the crawler has chosen an allowed URL. The worker opens the page in a browser runtime so WebRiskOps can observe visible content, JavaScript behavior, console messages, network errors, screenshots and HTML snapshots. Use this page when the scan detail or issue evidence mentions rendering, missing artifacts, timeouts, console errors, network failures or a page that looked different from a normal browser session.

Review rendered page evidence

Follow the path `Scans → Scan detail → Worker readiness → Artifacts → View issues`.

1. Open /scans/{scanRun} from the project or Scans list. Result: the scan detail page shows Status, Worker readiness and artifact availability for the run.
2. Confirm the scan is Completed or read the current Running page. Result: rendered evidence is tied to the correct URL and scan run, not a stale browser session.
3. Check Worker readiness → Artifacts. Result: Screenshot, HTML snapshot and issue evidence availability are visible before interpreting findings.
4. Review Scan coverage notes when they appear. Result: unavailable pages, private areas and evidence gaps are explained before retrying.
5. Open View issues for a page or issue with rendering notes. Result: console, network, screenshot and HTML evidence can be compared together.
6. Retry only after the target is reachable and scope is still accepted. Result: transient browser failures do not expand scope or create duplicate scans.

What rendering records

Rendered evidence should explain what the browser worker saw, not just whether the URL responded.

• Page title, status code and final URL.
• Screenshot availability and screenshot path when a visual capture was stored.
• HTML snapshot availability when the rendered DOM was stored.
• Console error count and network error count.
• Issue evidence that references the rendered page state.
• Coverage notes for unavailable pages, unsupported paths, private areas and evidence gaps.

Rendering blocked states

Do not treat every rendering problem as a scanner bug or a reason to expand scope.

• Browser render failed means the worker could not observe the page reliably.
• Page load timeout means retry only after the customer site is reachable and scope is unchanged.
• Login wall means exclude the page or document scoped access before retrying.
• Blocked resource means inspect [Console and network evidence](/docs/projects/console-and-network-evidence) before deciding whether the page failed.
• Evidence incomplete means the report should use available deterministic signals without inventing screenshots or hidden page content.

Continue to screenshots and HTML snapshots

When the scan detail shows screenshot or HTML availability, continue to [Screenshots and HTML snapshots](/docs/projects/screenshots-and-html-snapshots). That page explains what each stored artifact proves and why an artifact may be missing.