How to check your computer before changing settings

Changing a setting can make a computer feel faster, quieter, or more stable, but it is hard to tell what helped if you do not know how it behaved before. A quick baseline gives you something to compare against and can help you avoid changing several things at once.

Use Test Everything to check your computer step by step and get a report. Write down the conditions and results before you change anything, then repeat the relevant checks afterward.

Run a baseline check

1. Open Test Everything before changing system settings, installing updates, or disconnecting equipment. Follow the test sequence on the page.
2. Allow access only when a test needs it. For example, a camera or microphone check asks for permission first. You can decline a test that you do not need, but note that you did not run it.
3. Keep the setup consistent. Leave the computer plugged in or on battery as appropriate, and keep the same monitor, accessories, network connection, and room setup you plan to use later.
4. Let each test finish and note the result or any error shown in the report. Record unusual symptoms too, such as a fan getting loud, a device disconnecting, or a screen flickering.
5. Write down useful conditions: the browser, whether the computer was charging, which accessories were connected, and whether demanding apps were open. Do not change settings until you have captured this baseline.

The point is not to make every score perfect. You are creating a record of this computer under these conditions. If you later change a setting, repeat the same test with the setup as close as possible to the original.

What the results mean

The checks complete and the results are consistent

This gives you a useful comparison point. It does not prove that every part is fault-free, but it helps show whether a later change coincides with a measurable difference. Keep the report and your notes together so you can compare the same items.

One result looks much worse than expected

A single low score does not automatically mean a part is failing. Background apps, heat, power state, browser behavior, and test timing can all affect performance. If the result matters, close unnecessary apps, let the computer cool, and repeat that check once under the same conditions.

A test is missing or unavailable

That can be a browser or device limitation, not a fault. Some tests need hardware that your computer does not have, and browser access to certain details varies. Note what was unavailable rather than treating it as a failed result.

The computer behaves differently after a change

The difference is a clue, not proof that the setting caused it. Compare the same test and conditions, then restore the previous value if the change made things worse. If several settings changed together, you cannot easily tell which one mattered.

How to compare results fairly

1. Repeat the same test first. If a result is surprising, run it again before changing anything. A one-time dip can happen when another task briefly uses the processor or storage.
2. Keep power conditions the same. A laptop may perform differently on battery than while charging. On Windows 11, check Settings › System › Power & battery › Power mode. On a Mac, check System Settings › Battery for Low Power Mode on supported models.
3. Change one setting at a time. Record the original value, make one adjustment, then repeat the check that relates to it. If you alter several settings together, go back and test them separately to find the cause.
4. Restore the old value if needed. If a display change makes text or images look wrong, check Settings › System › Display on Windows 11 or System Settings › Displays on macOS. Select the previous value you recorded.
5. Restart only when the change calls for it. Some updates and driver changes need a restart, but a restart also changes the test conditions. Note that you restarted, then run the same checks again.
6. Follow up on a persistent failure. If the same device or test keeps failing, narrow the problem to that part, its connection, or its system setting. A general report can point you toward an issue, but it cannot identify every cause or replace a repair diagnosis.

What a browser check can and cannot tell you

Test results are useful for comparing the computer with itself, especially before and after a change. They are not a complete inspection of the operating system or every hardware feature. A browser gets only a rounded hint about RAM size, for example, rather than the exact amount. Some details are restricted by the browser, and a test cannot confirm every hidden hardware fault.

For a fair comparison, note what changed and keep the rest of the setup steady. The speed test exchanges test data with TooLab's server to measure the connection, so network conditions can affect those results.