Skip to main content

SDLA Quick Fix Idea · Chromebook

The Chromebook Is Running Slowly

Reduce current workload first, identify the tab or extension using resources, and clear only the browsing data that is actually needed.

Teacher

The Chromebook is slow, tabs keep refreshing, or classroom apps take a long time to respond. What should I try without disrupting the student's account or district settings?

Quick Fix

Protect student work first: Before closing tabs, ending a process, restarting, or clearing data, save or submit any open work. Ending a task can discard unsaved changes. Do not remove district-required extensions or clear passwords, cookies, or site data unless local support directs you to do so.

Start with workload, not deletion

Too many tabs, video meetings, background apps, low storage, or one heavy extension can slow a Chromebook. Closing what is not needed is safer and often more useful than immediately deleting all browsing data.

Work through these steps in order and test after each one.

  1. Close unused tabs and apps

    Save work, then close unused tabs with Ctrl + W. End video calls, Android apps, and extra windows that are no longer part of the lesson. Restart the Chromebook if it has been running for many days.

  2. Find a resource-heavy task

    Press Shift + Esc to open Chrome Task Manager. Sort by memory when available. If one optional tab, app, or extension is using unusually high resources, select it and choose End Process. Unsaved work in that task will be lost.

  3. Review extensions carefully

    In Chrome, open More > Extensions > Manage extensions. Disable or remove only an unnecessary extension the user is authorized to manage, especially one added shortly before the slowdown began. A managed extension may be locked on by district policy; document it for support rather than trying to bypass management.

  4. Clear cache only when it fits the symptom

    Press Ctrl + H to open History, then choose Delete browsing data. Select an appropriate time range and Cached images and files. Leave passwords, autofill, cookies, and other site data unchecked unless there is a specific reason and local guidance. Cache clearing is most useful for a misbehaving site; it is not the first fix for every slow Chromebook.

  5. Check updates, storage, and Diagnostics
    • Open Settings > About ChromeOS and check for updates when district policy permits.
    • Open Settings > System preferences > Storage management and look for very low free space.
    • Search the Launcher for Diagnostics to review CPU and memory behavior. CPU stress tests can temporarily make the device slower, so do not run them during instruction.

Performance improves after tabs closeReopen only the resources needed for the lesson. If one website consistently causes the slowdown, record its URL, activity, and the number of affected students.

One optional extension is responsibleLeave it disabled if authorized and report the finding. If the extension is required or managed, ask technology staff to review its policy and version.

The device is low on storageMove needed local files to the district-approved cloud location before deleting anything. Follow local retention and privacy rules.

Diagnostics fails or slowness affects every userSubmit the Chromebook for support with the test result, device asset number, and the conditions under which the slowdown occurs.

Copy-and-paste support request

Subject: Chromebook remains slow after basic troubleshooting Device asset number: [asset number] Date/time and class activity: [details] Websites or apps open: [names] Approximate number of tabs: [number] Restart completed: [yes/no] High-usage task or extension observed: [name/details] Managed extension involved: [yes/no/unknown] Available storage, if checked: [amount] Diagnostics CPU or memory result: [result] Other students affected: [yes/no and approximate number] Please review device performance and applicable managed policies. No student password is included.

Official guidance