How to use Device benchmark
Open Device benchmark on the phone, tablet, or computer you want to score. Device class, cores, and the memory hint (if the browser shares one) show immediately. Tap Run benchmark and leave this tab in the foreground for about 11 seconds. CPU runs first (about 5 seconds), then JavaScript and layout (about 2 seconds), then graphics (about 4.5 seconds). Progress updates live for each phase. Read the 0–100 score and the subscores. Copy the summary if you want to keep it. This is a rough in-browser score, not a lab benchmark. Nothing is uploaded.
Open the tool
Use the workspace below — no signup is required.
Enter your input
Open Device benchmark on the phone, tablet, or computer you want to score. Device class, cores, and the memory hint (if the browser shares one) show immediately. Tap Run benchmark and leave this tab in the foreground for about 11 seconds. CPU runs first (about 5 seconds), then JavaScript and layout (about 2 seconds), then graphics (about 4.5 seconds). Progress updates live for each phase. Read the 0–100 score and the subscores. Copy the summary if you want to keep it. This is a rough in-browser score, not a lab benchmark. Nothing is uploaded.
Copy the result
Copy text or download a file when the tool offers an export. Local tools keep processing in this tab.
About this tool
Score this phone, tablet, or desktop with a rough 0–100 in-browser benchmark. About 11 seconds on this device: typed-array math, a JSON and layout pass, then a longer WebGL paint (Canvas 2D if WebGL is missing). Live progress, subscores, and a guessed phone, tablet, or desktop label. Cores and the navigator.deviceMemory hint count when the browser exposes them. Not a lab benchmark. Nothing is uploaded. Device benchmark on Omnipus runs in this tab with no upload. No account, watermark, or daily cap.
Related guides
- Reading a privacy badge on Omnipus
What “Runs on your device”, “Fetches a public URL”, and “Uses a public rates API” mean in practice.
