Skip to content

URL Scan Details

The URL Scan Details screen provides in-depth results for a single scanned URL within a specific scan run.

Results are grouped into four tabs - Accessibility, Performance, SEO and Agentic Readiness - and next to them you can switch between Desktop results and Mobile results. Each view displays results specific to the selected metric and platform. If you arrived from Scan Results, the tab you were viewing there is already selected.

The sections below describe the Accessibility tab. For what the other three measure and how their scores are calculated, see Quality Metrics.

Scan Information

Above the tabs, the Scan Information block identifies the page you are inspecting. It describes the page rather than any one metric, so it stays visible whichever tab is active:

  • A visual preview (screenshot) of the scanned page, which helps identify the context in which issues occur. Select it to enlarge it. It is shown only when the scan captured one
  • The URL - the only place the address appears on this screen. It opens the live page in a new tab, and the action beside it opens the page in the Development Assistant
  • Scanned On - the date and time of the scan
  • Status (Success or Failed)

URL Scan Summary

On the Accessibility tab, the Overall Statistics section provides a high-level overview of the results for the selected URL and platform:

  • Platform-specific accessibility score
  • Total number of issues found

Issues by Severity

Detected issues for the selected URL are grouped by severity: Critical, High, Medium and Low.

Each severity card displays both the number of issues and their relative distribution for the URL.

Accessibility Issues

All accessibility issues detected on the selected URL are listed below.

Each row represents a single issue type affecting this URL, and includes:

  • Issue name
  • Severity
  • WCAG violation level (e.g. A, AA, AAA, Best Practice)
  • Element count (number of affected elements on the page)

Each issue can be expanded to view the affected elements.

Affected Elements

For each expanded issue, the affected elements are displayed with detailed technical information:

  • CSS selector
  • HTML markup

Actions on each element open the affected URL directly in the Development Assistant or in the Agora AI Workbench, allowing developers to inspect the issue live and in context on the page.

Performance, SEO and Agentic Readiness

Each of the three remaining tabs shows this page's score for that metric, followed by the individual findings behind it.

  • Performance - the score, this page's LCP, CLS, TBT, FCP and Speed Index, and the findings that explain them: what is slowing the page down, and what could be saved by fixing it.
  • SEO - the score, and the individual checks behind it, such as the page's meta description, document title, link text and hreflang values.
  • Agentic Readiness - the score together with the number of checks passed out of those that applied, and all six named checks, including any that did not apply to this page.

Each finding shows its Status (Pass, Needs improvement, Fail, Informational or Not applicable) and, where the check measures something, a Value - for example a timing or an estimated saving. Expand a row to read what the check evaluates, why it matters, why this page got this result, and the specific resources involved - the scripts, images, requests or page elements to fix, with their URLs, sizes, timings and DOM selectors. The rows behave exactly like the accessibility issues above, and are fully keyboard-operable.

The Performance tab also carries a How to read this score note explaining that the score is measured on a deliberately low-end device profile, and therefore reads as a worst case rather than as an average visitor's experience.

If a metric was not collected for this scan, the tab shows Not scanned instead of a score. If it was collected but the audit did not complete for this page, it shows as failed - which is distinct from a low score, and independent of whether the accessibility scan of the same page succeeded.