TEST GUIDE
Test your phone performance online with live browser FPS and a short JavaScript workload. Use the results to investigate slow or uneven browser behavior before buying a used phone, not as a hardware health certificate.
FPS estimates how often the browser runs animation callbacks. It is not a measurement of a game's FPS or a guarantee of the panel's maximum refresh rate. Browser limits, power-saving settings and background activity can change it.
K means thousands of loop iterations completed during this specific workload. A higher number means more iterations in this test, not an industry-standard CPU score. Compare using the same test, browser version and similar conditions; cross-browser scores are not directly comparable.
Let the phone cool, check power-saving settings and repeat with unnecessary apps closed. A low score alone does not diagnose damaged hardware. If slow behavior persists in ordinary use, investigate with the manufacturer's diagnostics or a repair technician.
Record three runs with the same browser, power mode and test conditions. If one run differs sharply, check whether another app opened or the tab lost focus, then repeat. There is no device ranking or calibrated pass threshold here; consistency and your experience in everyday apps are more useful than a single best score.
This is not an internet speed test, native GPU benchmark, battery-health measurement or proof that the phone has original parts. Combine it with screen, battery, camera and ownership checks.
Checking a used phone? Follow the Android inspection guide or iPhone inspection guide for checks this browser test cannot cover.
COMMON QUESTIONS
Open this page on the phone, observe the browser FPS, then run the short workload. Keep the browser visible and repeat under consistent conditions. No app installation is required.
There is no universal pass mark for this browser workload. Browser engine, version, device temperature and power settings affect the result. Compare repeat runs under matching conditions rather than using a fixed healthy/unhealthy threshold.
The JavaScript workload occupies the browser's main thread for about 0.9 seconds, delaying animation callbacks. A drop during that interval is expected and is not evidence of a hardware fault.
You can observe their behavior, but different browser engines and power-management policies affect the scores. Treat cross-platform results as browser-specific observations, not a definitive hardware ranking.
This short test only samples browser animation and one JavaScript workload. It cannot rule out app-specific problems, slow downloads, limited free storage or battery-related issues. Identify where the slowdown happens and compare normal app use with repeat browser runs.