What browser evidence helps investigate a website problem

A website problem often appears far from its cause. A clear visitor statement is still the first fact. A small set of browser facts can then show where the visible result and the website source differ.

A visitor-approved screenshot

A screenshot can show the visible state, the selected control, and an error message. The visitor must start the capture, review the image, and approve its inclusion. The visitor can remove the image before submission.

A screenshot can also contain private data. Review the complete image before approval. Do not include an account number, payment value, personal message, or other private record.

Console errors and warnings

A bounded console item can show a safe error message, a source path, and a time. It can help the owner connect the report to one browser failure.

Console text can contain credentials or email addresses. A safe collection must apply redaction and a strict item limit. The item is evidence, not proof of the final cause.

Failed or slow request metadata

Request metadata can show an HTTP method, a path without query values, a status, a duration, and a time. For example, POST /api/profile with status 500 can support the visitor statement.

A safe report does not include request headers, request bodies, response bodies, credentials, query values, or URL fragments.

Metadata-only browser state

A cookie, form field, or local-storage entry can show only three facts:

• The item name.
• Whether the item is present.
• The item size.

The value is never part of the report. This rule protects passwords, payment values, account credentials, and private customer data. A website owner can disable this category, but cannot enable values.

Read the exact widget privacy rules before installation. For a concise report structure, use the website problem report guide.