SYSTEM & NETWORK TESTS · HELP & TROUBLESHOOTING

Device Info questions, fixes and result guides.

Practical answers for common device info problems, confusing results and setup questions — with a direct path back to the live test.

01
Explain it

What device information can a website actually detect?

A browser can expose limited signals such as screen size, logical CPU count, approximate memory on some browsers, touch capability, language and device-pixel ratio. Exact hardware models and serial identifiers are intentionally restricted.

02
Explain it

Why does device memory show an approximate value?

Browsers that expose deviceMemory intentionally return coarse buckets rather than exact installed RAM. This reduces fingerprinting risk and means the number should be treated as an estimate.

03
Fix a problem

Why is logical CPU count different from my CPU core specification?

navigator.hardwareConcurrency reports logical processors available to the browser, which can include simultaneous multithreading and can be limited by the browser or environment.

04
Fix a problem

Why can't the page show my exact CPU or RAM model?

Modern browsers intentionally limit hardware details for privacy. Logical CPU count and approximate memory may be exposed, but exact models and serial identifiers are not standard web data.

05
Explain it

Is the device information sent to a server?

The displayed hardware/browser capability values are read in the page. The tool does not need to upload them to produce the diagnostic grid.

06
Explain it

How accurate is this device info tool?

Browsers do not expose exact CPU model, serial numbers or precise physical memory.

07
Fix a problem

What should I do if the device info result looks wrong?

If a value is unavailable, that usually means the browser does not expose it. Compare another browser before assuming the hardware itself is missing a capability.