تخطي إلى المحتوى

هذه الصفحة غير متوفرة بلغتك بعد. أنت تقرأ النص الإنجليزي.

Free tools

Hardware and client hints

The number of cores, the memory size, touch points and client hints are read by a site in the first second and compared with each other. Here you see what it gets from your machine.

Your values right now

The values below are read from your browser on this page.

Platform
جارٍ القياس…
Cores
جارٍ القياس…
Memory in gigabytes
جارٍ القياس…
Script heap limit
جارٍ القياس…
Touch points
جارٍ القياس…
Processor architecture
جارٍ القياس…
Bitness
جارٍ القياس…
System version
جارٍ القياس…
Device model
جارٍ القياس…

كل ما في هذه الصفحة يُقاس داخل متصفحك ولا يغادره أبدًا. بلا طلبات ولا سجلات ولا حساب.

What a site compares

Cores and memory come apart but are read together with the graphics card: old integrated graphics beside sixteen cores is a pair that does not occur in laptops.

The browser gives memory as a step rather than an exact number, and the heap limit lands on one of a hundred steps.

Client hints

Architecture, bitness, system version and device model are handed to a site on its request. The model is empty on a desktop machine and named on a phone, and an empty model under a phone signature gives a forgery away.

What ARMANOS does

Cores and memory follow the named graphics card rather than falling out by a separate lot. The heap limit is figured by the same step as in a real browser, and on a phone it is half the desktop one for the same memory.

How to compare two profiles

Open the page in two profiles. Cores, memory and system version have to agree with the declared platform in both, and differ between the profiles.

What this check does not show

  • The exact memory size. The browser rounds it to a step, and no page can answer more precisely.
  • The device model on a desktop machine. It is empty in a live browser there, and that is not a mismatch.
  • Client hints in browsers that do not hand them over. The rows are empty then.

Where this is decided

The readings are measured in your browser, and the promises below are backed by files you can open.

Readings on the page come from an allowed list
apps/web/components/site/LiveReadout.tsx
A hundred memory steps match the engine to the unit
packages/shared/test/ступени-памяти-как-у-движка.js
Cores and memory do not diverge from the named graphics card
apps/desktop/test/fingerprint-consistency.js

Questions

Why is memory rounded?
The browser does that: an exact number would single you out more than any step. A profile answers with the same step as a real browser.
What does an empty model mean?
On a desktop machine the browser does not name a model. An empty string is ordinary here, and on a phone it has to be filled.
Are the values sent anywhere?
No. The page reads them from the browser and shows them to you.

Two profiles give two different answers

In ARMANOS these values are decided inside the browser engine before the page gets anything. Open two profiles, run the check in both and compare.