How to check a CPU score on a public library computer

A public library computer feels slow, and you want to know whether its processor is the reason. You can check a browser-based CPU score without installing anything, but a shared computer needs a little extra care.

Test Everything runs TooLab’s tests step by step and provides a report. Because it checks more than the processor, it may take longer and run tests you do not need. If you only want a CPU score, the focused Processor Test is a better choice when the library allows it.

Check the CPU score

1. Check the library’s computer-use rules first. Ask staff if you are unsure whether you can run hardware tests or if the computer is needed by someone else.
2. Open TooLab in the browser already installed on the computer. Choose the Test Everything tool if you want the full check, or open the Processor Test for a CPU-only result.
3. If you chose Test Everything, follow its on-screen steps. It runs each test in turn, so wait for the processor step and its result. Some tests may request camera, microphone, or other permissions. On a public computer, do not grant a permission unless you understand why it is needed and library policy allows it.
4. Let the processor test finish without switching away from the page or starting other tasks. If the computer is busy, wait until it is idle or stop rather than adding load while someone else is using it.
5. Read the processor score in the report. The Processor Test gives a score out of 100. Note the score only if you need it, then close the TooLab page and end your library computer session as the library instructs.

Test Everything can take longer than a processor-only check because it runs every test step by step. Some steps may place a heavier load on the computer. On a shared library PC, do not start the full suite without permission, and avoid it if the computer is already warm, noisy, or in use.

What the score means

The processor test finishes and gives a score

The browser completed its CPU workload and produced a result. A score out of 100 is a benchmark result from this test, not a percentage of the processor’s maximum capacity and not a rating of the entire computer. It also does not tell you by itself whether the library PC is broken.

The score seems low or the computer feels slow

A single result is a snapshot. Other browser tabs, active programs, power-saving behavior, heat, and the computer’s age can affect performance. A low score can point to limited CPU performance during that run, but it does not identify the cause. You may not have permission to inspect or change system settings on a public computer, so ask library staff if the machine is consistently slow.

The test is blocked or does not finish

The library may restrict websites, browser features, or hardware workloads. The computer may also be busy, or its browser may not support a feature the test needs. A blocked test is not proof of a faulty processor. Do not try to bypass library restrictions or install another browser.

The full report shows other results too

Test Everything checks more than CPU performance. Its report can include results from other hardware and connection tests, so do not treat the whole report as a CPU score. If you only need processor performance, use the focused Processor Test instead of running unrelated checks.

What to do if the check is slow or interrupted

1. Use the focused test. Open the Processor Test instead of running every check. It gives you the CPU result without requiring a full hardware run.
2. Wait for an idle computer. If many tabs or programs are open, the score may reflect that extra activity. Do not close other people’s work or programs. Ask staff whether there is a quieter time to use the computer.
3. Keep the browser in the foreground. Let the test run on its page. Switching tabs or starting other work can interrupt the run or affect the result.
4. Do not change managed settings. Library computers may use centrally managed power, security, and browser settings. If the browser blocks the test or the PC stays slow, tell staff rather than changing settings or attempting to work around restrictions.
5. Stop if the computer behaves unusually. If it becomes very hot, makes a new loud noise, or stops responding, end the test if you can and tell library staff. Do not repeatedly run a heavy workload on a shared machine.

Keep the public computer session private

Use a browser session provided for guests if the library offers one. Avoid signing in to personal accounts just to run a CPU test. Do not save a report or photograph it if it contains device or browser details you do not want to share. When you finish, close your pages and sign out or end the session using the library’s normal process.

If staff need to investigate a slow computer, tell them what you noticed and whether the test completed. A score alone cannot diagnose the cause.