ScrapeTraceCHECKS

MOBILE CONFIGURATION OBSERVATIONS

Phone-sized.
Mobile everywhere?

A smaller screen and a touch point can be only part of a mobile configuration. Compare geometry, input capabilities and browser identity in one snapshot.

Waiting for JavaScript execution.

REPORTED CONFIGURATION

Not measured yet

This page must execute before it contains browser readings.

Reported screen

CSS pixels · schematic
Shape follows the reported dimensions. This is not a physical device identification. Page size is compared separately; no OS or browser-bar positions are inferred.

Every reported signal

These readings belong to this execution. Compare exported snapshots from separate desktop and mobile requests to see what changed. Explore screen geometry → · Compare User-Agents across contexts →

JavaScript readings and document request headers
PropertyReported valueReading
How this check interprets mobile signals

This check reports combinations, not a mobile authenticity score. “Compact screen” means its shorter edge is at most 600 CSS pixels. Small desktop screens, resized windows, tablets, foldables, desktop browsing modes and attached keyboards or mice can affect these signals. Touch capability alone is not proof of a phone. A Linux platform string alone does not distinguish desktop Linux from Android; the full UA and client hints supply context.

UA identity uses readable platform markers, not a complete browser parser. Headless is mentioned only if the JavaScript UA contains that marker. JavaScript UA Client Hints may be unavailable; missing is not false. No high-entropy method is called and no permissions are requested.

Request values are the headers received by this server for this document, not inferred JavaScript values. Missing headers stay unavailable. A proxy may rewrite headers, and an in-page rerun keeps the original document request values. Reload to capture a new request. Browser readings are not sent back to the server; they stay in the rendered DOM and local JSON downloads.

Runs automatically once. Wait for navigation load or #probe-complete[data-status="complete"] before saving rendered HTML. Initial HTTP HTML contains request headers and a not-measured message; it contains no browser measurements. The completed result is written to visible tables, #report-json and window.__PROBE_RESULT__. A fresh rerun replaces the snapshot.

UA mobile hint · Touch points · Pointer capability · Source

Complete result JSON
Not measured.