Acer · slow

Acer Chromebook Plus 514 is running very slowly

Acer Chromebook Plus 514 is running very slowly: CPU, memory, storage, temperature, updates and one process should be measured instead of cleared blindly. Scoped to CB514 complete suffix required.

Acer Chromebook Plus 514 is running very slowly: Google's Diagnostics app has a CPU section built for this: it shows a graph of CPU usage that can help identify which applications use the most, and its tests (a stress test, a cache test, a floating point accuracy test and a prime search test) can reveal CPU failure or improper cooling. Google warns that CPU tests can stress the device and make regular use difficult, and that a failed memory test may mean faulty memory.

For everyday slowness, Google's video chat article gives advice that applies to any heavy use: update ChromeOS, close browser tabs and apps you are not using, and use only one monitor, since two or more raise the CPU and GPU load. Extensions are the other big cause on a Chromebook, and Safety Reset turns them all off without deleting local data. Chromebook Plus models are described by Google as meeting higher hardware specifications, and this model has 8 GB of memory, so a Chromebook that slows down with a few tabs is worth testing in Diagnostics.

Differential

Likely causes of “Acer Chromebook Plus 514 is running very slowly”, and how to tell them apart

  1. 1

    Too many tabs, apps and extensions

    What separates it The Chromebook is slow with many tabs open because of too many tabs, apps and extensions

    How to confirm Close tabs and apps you do not need and remove extensions

  2. 2

    An out-of-date ChromeOS

    What separates it It has been slow since an update was postponed

    How to confirm Update ChromeOS: Settings, About ChromeOS, Check for updates

  3. 3

    A heavy app

    What separates it The Diagnostics CPU graph shows one app using most of the processor

    How to confirm Close or update that app, and test the speed again

  4. 4

    Too little free memory or a failing memory

    What separates it The Diagnostics memory test fails because of too little free memory or a failing memory

    How to confirm Google says a failed memory test may indicate faulty memory; contact the manufacturer

  5. 5

    A corrupt profile or settings

    What separates it The slowness persists after the steps because of a corrupt profile or settings

    How to confirm Try Safety Reset, then a Powerwash after backing up

Before you touch a setting

Record this first — changing settings destroys the evidence

  • The full model number, ChromeOS version and how many tabs and extensions are open
  • What the Diagnostics CPU graph shows and whether the memory test passes
  • Whether the slowness is at startup, in one app or everywhere
  • Whether it is slow only when hot or on battery

Try in this order

0 of 5 completed
  1. Restart

    Reversible

    Restart the Chromebook, since a restart clears stuck processes that slow it down, and then test again to see whether it helped.

  2. Close tabs and apps

    Reversible

    Close tabs and apps, which is Google's advice for smooth performance on a Chromebook, and then test again to see whether it helped.

  3. Remove extensions

    Reversible

    Turn them off one at a time, or use Safety Reset to disable them all.

  4. Run the memory test

    Reversible

    Run the memory test, in Diagnostics, Memory, and a failure points at faulty memory, and then test again to see whether it helped.

  5. Powerwash last

    Reversible

    Powerwash last, by backing up first, since it erases the drive of the Chromebook, and then test again to see whether it helped.

Model-specific

What is true of this model and not of its siblings

A light operating system
ChromeOS is light and runs fast on modest hardware per the catalog, so persistent slowness is worth testing in Diagnostics before assuming ordinary use.
Repair cost
Slowness is usually storage, tabs or extensions and costs nothing to fix. If a hardware fault is behind it, an independent shop repair is typically $99 to $299 per BadgerLayer, with a free diagnostic.

Stop boundary

When this stops being a self-service repair

  • !If the Diagnostics memory or CPU tests fail, contact Acer Support
  • !If a school or work Chromebook is slow because of policy or extensions, contact your administrator
  • !If it is slow only when hot, see the overheating page

Evidence ledger

Sources behind this answer

Exact questions

Common questions

Can a Chromebook slow after a long uptime?+

Yes. Restart it weekly, since ChromeOS applies updates on restart and clears stuck processes.

Can Linux or Android apps slow it?+

They can if many run at once. Close the ones you are not using and check the Diagnostics CPU graph for the app at the top.

Does a full drive slow a Chromebook?+

Yes. ChromeOS needs free space to work, so clear old downloads and offline files, and keep files in Google Drive rather than on the Chromebook.

Do I need to reinstall apps after Safety Reset?+

No. Google says Safety Reset keeps local data and apps; extensions are disabled and you re-enable the ones you trust afterwards.

How do I see what is using the processor?+

Open Diagnostics under Settings, About ChromeOS and look at the CPU graph, which Google says helps identify the applications using the most CPU.

Will Diagnostics slow my Chromebook?+

Yes, while the CPU tests run. Google warns they can stress the device and make regular use difficult.

Do extensions slow a Chromebook?+

Often. Turn them off one at a time, or use Safety Reset to disable them all.

Does Safety Reset delete my files?+

No. Google says it resets Chrome settings and network and input settings and disables extensions without deleting local data or apps.

How much memory does the Plus 514 have?+

Acer's page lists 8 GB of LPDDR5 memory, and Google's Chromebook Plus category calls for 8 GB or more.

Is a two-monitor setup slower?+

Google says two or more monitors increase CPU and GPU load; use one during video calls.

Wrong device or version?

Match the path before repeating the steps.

Match another device