Microsoft New Outlook Performance Analysis: WebView2 vs Outlook Classic

New Outlook Notification Latency

Clicking a Windows 11 notification for a new email in the new Outlook can take up to 10 seconds to load the specific message. In contrast, Outlook Classic handles the same action almost instantly.

This performance gap is most evident when using notifications: while the new Outlook now opens from the Start menu at speeds comparable to Outlook Classic, the process of transitioning from a notification banner to a specific email involves loading the full inbox first, creating a significant delay. Users can often find and open an email manually from the app faster than waiting for the notification link to resolve.

The Architectural Root Cause: WebView2

The performance disparity stems from the new Outlook's architecture. Unlike Outlook Classic, which is a native Win32 desktop application, the new Outlook is built on WebView2, a Chromium-based rendering engine. Essentially, the app is a browser window loading Outlook.com.

Resource Consumption

The shift to a web-wrapper architecture results in significantly higher system resource usage:

  • Memory (RAM): The new Outlook consumes between 490 MB and 636 MB of RAM while idle, compared to 117 MB to 148 MB for Outlook Classic—a roughly fourfold increase.
  • CPU Usage: Idle CPU usage for the new Outlook is approximately 4%, while Outlook Classic typically remains under 1%.
  • Process Overhead: The new Outlook runs as 10 separate processes in Task Manager (including WebView2 Manager, GPU Process, and Service Worker), whereas Outlook Classic operates as a single compact process.

Execution Chain

Every interaction in the new Outlook requires a browser-like process chain: the app must initialize or resume its web layer, authenticate, and render the mail thread through the Chromium engine. This introduces non-deterministic latencies that are absent in native code. While Microsoft has tested a "Delayed Message Timing" API to diagnose WebView2 performance, it has not resolved the core notification lag.

Feature Parity and Migration Timeline

Despite performance issues, Microsoft is aggressively pushing the new Outlook as the successor to both Outlook Classic and the retired UWP Mail and Calendar apps.

Recent Improvements

  • March 2026 Update: Enhanced folder search and shared mailbox access.
  • May 2026 Update: Added automapped calendar support to prevent loss of shared calendars during migration.
  • June 2026 Update: Introduced expanded .PST support (arriving July 2026) and a Unified Inbox view (arriving August 2026).

Support Deadlines

Microsoft has postponed the forced opt-out deadline for enterprises to March 2027. However, Outlook Classic remains available and supported until April 2029, providing a window for users who prioritize performance over the new web-based feature set.

Community Perspectives and Industry Critique

Technical discussions among users and developers highlight a broader trend of "software bloat" where hardware gains are offset by inefficient architectural choices.

"Modern code has more to do, more fonts, more graphics, more Unicode, but still it has gotten really absurd. 10 seconds on a modern computer is a lot of time."

Critics argue that the move to WebView2 is a choice of developer portability over user experience. Some users have noted similar patterns in other Microsoft products, such as the new Microsoft Teams, which also saw significant launch delays despite architectural updates. Others point to the fact that high-performance web-mail clients like Fastmail exist, suggesting that the new Outlook's slowness is a result of poor implementation rather than an inherent limitation of web technologies.

Future Outlook: The Return to Native

Because the constraints of WebView2 are "baked in," many experts suggest that true performance parity with Outlook Classic can only be achieved through a move back to native code. Reports indicate Microsoft is increasingly committed to WinUI, with initiatives underway to rewrite various Windows 11 components in native code to eliminate the "web app slop" that has degraded the OS experience.

Sources