If Google Chrome on your Windows 11 laptop suddenly feels like it’s running through molasses while Microsoft Edge flies, the culprit is often not Chrome itself but Windows’ new “Efficiency mode” and how it interacts with modern Chromium-based browsers.
Background
Windows 11 introduced a new, visible way to throttle background work with the redesigned Task Manager that arrived alongside the 22H2 feature update. That feature—
Efficiency mode—is meant to save power and lower thermal load by telling the OS scheduler and power-management subsystems to treat certain processes as non time‑critical. When a process is marked as efficient, Windows reduces its scheduling priority, may select lower CPU frequencies for its threads, and can prefer energy-efficient cores on hybrid CPUs for those threads. In Task Manager, processes placed into this state are marked with a small green leaf icon; suspended UWP-style processes get a different icon.
At the same time, modern browsers—including Chromium-based browsers such as Google Chrome, Microsoft Edge and several forks—use a multiprocess architecture that spawns dozens (or hundreds) of renderer, utility and extension processes. That design improves stability and security, but it also multiplies the number of targets that Windows’ efficiency heuristics can act on. If many renderer processes are classified as “efficient,” Windows can quietly throttle much of the browser’s work, producing UI stutters, slow tab switches, frame drops in video playback, and laggy typing or scrolling experiences.
Why Efficiency mode makes Chrome feel slow
The scheduler and EcoQoS in plain English
Windows' power and scheduling APIs expose something called Quality of Service (QoS) levels for threads and processes. One of those levels—
EcoQoS—is intended for background, low‑priority work. Processes using EcoQoS are scheduled so they use less peak power: they can be run at lower CPU frequencies, they are easier to preempt, and on hybrid processors Windows can prefer energy‑efficient cores (E‑cores) for them rather than fast performance cores (P‑cores).
Chromium-based browsers contain platform-specific code that interacts with these APIs. In practice, that means a browser can mark some of its background threads or background renderer processes in ways that make Windows treat them as “efficient.” That’s sensible for tabs you aren’t using, but problematic when Windows or the browser’s heuristics become over-aggressive and mark too many active pieces of the browser as background work.
Multiprocess design + aggressive throttling = visible lag
Because Chrome treats tabs, extensions, subframes and GPU work as separate processes and threads, the
apparent cost of a single “efficiency decision” multiplies. If Windows throttles many of those processes at once—moving them to EcoQoS or lowering priority—the browser’s ability to respond to input, paint frames, or decode video can be impaired. The result is the jitter, dropped frames and sluggish tab switching many users have observed.
How to tell if Efficiency mode is the problem
Check this before changing anything: you may be chasing the wrong bottleneck.
- Launch Google Chrome and open a demanding page (for example, a YouTube video or a complex web app).
- Press Ctrl + Shift + Esc to open Task Manager.
- Click More details if the compact view appears.
- Expand the Google Chrome entry by clicking the arrow to its left so you can see the individual chrome.exe processes.
- Look for the small green leaf icon next to one or more chrome.exe processes—this icon means Windows’ Efficiency mode is in effect for that process.
If you see the leaf next to many of Chrome’s child processes at the same time and you’re experiencing stutters or slow responsiveness, Efficiency mode is a plausible cause.
Short-term fixes you can try right away
- Turn Efficiency mode off per-process (temporary): In Task Manager, right‑click a chrome.exe process and uncheck Efficiency mode. That removes the green leaf while that process exists, but Windows and Chrome can reapply the setting the next time the process is launched. Use this as a diagnostic: if turning it off makes Chrome feel normal again, you’ve identified the likely root cause.
- Switch power plan / power slider: If you’re on battery or a power‑saver mode, move the Windows power slider to Best performance or select a high‑performance plan. This doesn’t guarantee the leaf won’t appear, but it reduces the system’s tendency to conserve.
- Keep Chrome’s Memory Saver enabled (and choose a balanced mode): Chrome’s built‑in Memory Saver (or similarly named Memory/Energy controls in recent versions) is specifically designed to manage inactive tabs in a browser‑friendly way—unloading or sleeping tabs without the blunt-force priority reductions Windows applies. In Chrome, open the menu → Settings → Performance (or Performance section) and set Memory Saver to Balanced (or Moderate). This often improves the experience because Chrome’s tab-sleeping is smarter about instantly waking tabs when you interact with them and less likely to throttle the browser’s UI.
Persistent solutions and trade-offs
If the temporary fixes work but the problem returns (for instance, after relaunching Chrome or starting new tabs), you have a few persistent options. Each carries trade‑offs.
1) The Chromium command-line flag (historical, increasingly unreliable)
For a time, Chromium supported a flag that could disable internal code that placed background browser processes into EcoQoS. People used a shortcut addition like:
--disable-features=UseEcoQoSForBackgroundProcess
to launch Chrome without that behavior. That approach helped many users for a while, but the Chromium codebase and shipping builds evolve: in recent months that flag’s effectiveness has been inconsistent, and in some Chromium versions it’s been removed or ignored. If you want to try it, add the flag to Chrome’s shortcut target and relaunch Chrome, but don’t be surprised if it stops working after a browser update.
Risk and note: this method depends on Chromium internals and can break silently after Chrome updates. It is not a reliable long‑term fix.
2) Use Process Lasso (persistent, vendor-supported rules)
A practical, persistent way to keep Windows from treating Chrome processes as efficient is to use a third‑party process manager that can persistently set the Efficiency mode preference for matching processes. One well‑known option adds exactly this capability: it allows you to create a rule that matches chrome.exe and forces Efficiency mode to Off every time Chrome launches. Typical steps in that tool are:
- Install the tool and run it with administrative rights.
- Open Options → CPU → Efficiency Mode (or a similarly named menu).
- Add a new rule: in the Process match field type chrome.exe.
- Set the rule to force Efficiency mode to Off for matches and save/apply.
After applying the rule, Task Manager should no longer show the green leaf for chrome.exe processes. Users report that this approach is persistent across reboots and Chrome updates.
Risk and note: this is a third‑party product, so you must trust the vendor, install the latest official build, and be comfortable running a utility that adjusts process behavior. For laptop users prioritizing battery life, forcing Chrome fully into performance mode will increase power draw and thermal output. Also keep the tool updated; the vendor may change behavior as Windows itself evolves.
3) Lightweight scripting (community approaches)
Enthusiast communities have shared PowerShell scripts or small utilities that monitor chrome.exe and periodically enforce a normal priority on its processes (or remove efficient flags). These are stopgap measures: they can be effective, but they’re brittle, require you to run and maintain a script with administrative rights, and are less elegant than a tested product that integrates with Windows process creation.
Risk and note: scripts have to run continuously and may conflict with security software. They require basic scripting knowledge and a willingness to maintain them after system updates.
What to expect after you disable Efficiency mode for Chrome
If Efficiency mode was the cause, disabling it for Chrome typically:
- Restores smooth tab switching and typing responsiveness.
- Eliminates dropped frames in video playback and reduces audio/video sync problems.
- Reclaims CPU cycles for renderer and GPU work, improving interactive responsiveness.
But you should also expect:
- Increased power consumption and faster battery drain on laptops.
- Higher average CPU usage, which may increase fan noise and device temperature.
- Possible negative effects on multitasking if the system had been relying on Efficiency mode to keep background processes from competing with foreground work.
Why Microsoft added Efficiency mode — and where the conflict comes from
Microsoft’s design goal with Efficiency mode and EcoQoS is sensible: reduce power draw, lower thermal output, and extend battery life by deprioritizing truly background jobs. For many apps and workloads this is a net win.
The conflict arises because browsers are both foreground applications (the UI and active tab) and hosts for many background tasks (background tabs, extensions, prefetchers). When the browser or Windows errs on the side of classifying too much as background, the user-facing portion of the browser suffers. This is especially visible on systems with many tabs or many CPU‑hungry background pages.
It’s also important to note that major browser vendors have been adding their own, browser-specific memory and energy controls precisely to avoid this kind of blunt-force OS throttling. Chrome’s Memory Saver and Edge’s sleeping-tab features are examples: they aim to conserve memory and energy while preserving the immediate responsiveness of the tab you’re actively using.
Practical, prioritized checklist (what to do, in order)
- Diagnose first: open Task Manager and confirm green leaf icons next to chrome.exe processes while you see stutter.
- Try Chrome’s Memory Saver/Balanced mode: Settings → Performance → Memory Saver (set to Balanced). Test responsiveness.
- Test by disabling Efficiency mode manually: right‑click a chrome.exe process in Task Manager and turn Efficiency mode off; if performance improves, you’ve confirmed the cause.
- Try the short-lived flag: add --disable-features=UseEcoQoSForBackgroundProcess to Chrome’s shortcut to see if it helps. If it works, it’s an easy but fragile fix.
- If you need a persistent fix and accept trade-offs, use a controlled tool: install a trusted process-management tool that can persistently force Efficiency mode Off for chrome.exe and configure a rule. Apply cautiously and monitor battery/thermals.
- If you prefer not to use third‑party tools: consider limiting open tabs, disabling unnecessary extensions, or switching power plans when you need responsiveness.
- Keep everything updated: Chrome/Chromium, Windows and any third‑party utilities. Behavior can and does change with updates.
The trade-off: performance vs. power and privacy
- Performance benefit: disabling Efficiency mode for Chrome restores responsiveness and reduces UI stuttering. For power users, creatives, or anyone doing heavy web‑based work, this can be essential.
- Battery and thermal costs: forcing browser processes to run at higher priority and on performance cores consumes more power and increases thermals.
- System-wide fairness: Efficiency mode exists to protect the user experience across all apps. For instance, on a thin-and-light laptop, letting Chrome consume everything while a video render or a game is paused may make the system feel worse overall.
- Third-party risk: if you install a utility to enforce rules, validate the vendor, verify code signing, and understand what the tool modifies.
What vendors are doing (and what to watch for)
Browser vendors are aware of the friction between OS-level power heuristics and web workloads. Chrome has been iterating on Memory Saver and performance detection tools that alert users about misbehaving tabs. The Chromium project has platform hooks that interact with Windows’ EcoQoS API; those hooks and the flags that control them may change between versions. That means a workaround that works today could stop working after a browser update.
Microsoft also continues to evolve scheduling and power heuristics. On hybrid CPUs the scheduler’s decisions about E‑core vs P‑core placement are dynamic and can change with OS updates. Expect the interaction between Windows and browsers to remain a moving target, and check again after major OS or browser updates if you notice new regressions.
Final analysis and recommendation
If Chrome suddenly becomes jittery on Windows 11, don’t blame Chrome outright—start by checking Task Manager for the green leaf. Windows’ Efficiency mode and EcoQoS are doing exactly what they were designed to do in many cases, but they can also overreach and degrade responsiveness for multiprocess apps like modern browsers.
For most users, the best first-line response is to enable Chrome’s internal Memory Saver (Balanced) and ensure your power profile isn’t in a power‑saver mode. If you need consistent, snappy browser performance and are willing to trade battery life for responsiveness, a controlled, vendor‑supported persistence mechanism that forces Efficiency mode Off for chrome.exe gives you the most deterministic result. If you take that route, do so deliberately: install reputable software, understand what it changes, and monitor your laptop’s battery and temperatures afterward.
Ultimately, this is a classic trade‑off between system-wide energy efficiency and per‑app performance. The right choice depends on how you use your machine: on battery and traveling? Prioritize battery. Plugged in or in a performance-critical workflow? Prioritize responsiveness—but accept the cost.
Source: MakeUseOf
This setting is why Chrome is so slow on your Windows 11 PC