1. 01Open the page to see the current UA, system environment and screen/viewport data.
2. 02Check the WebGL vendor, renderer, version and WebGL2 support — the browser may blur these fields for privacy reasons.
3. 03When the browser exposes the Battery API, read the charge level and charging state.
4. 04Read the capability matrix, or copy the current information as a JSON report.

• Every field is limited to what the browser publishes to a web page; privacy reduction, permission policy, virtual machines and browser spoofing can all blur or remove values.
• The WebGL renderer is read from the debug extension where available; a browser may deliberately return a generic GPU name.
• The Battery API is not a universally available standard capability, so battery data is shown only where it actually exists.
• Capability detection means “the property or interface exists”, not a real call; a supported label does not mean the user has granted access or that the hardware works.
• The page watches browser state such as navigator.onLine, but it never contacts an external server to verify real internet connectivity.

The page never uploads the device report to a server; “Copy JSON” only writes to your clipboard. Which fields the browser exposes is decided by its own privacy policy.