New Outlook's WebView2 architecture makes notification clicks 10x slower than Classic

Microsoft’s web-based “new Outlook” for Windows 11 takes roughly 10 seconds to surface a specific email after you click its notification banner, while the Win32-based Outlook Classic jumps to the same message almost instantly. The gap is so wide that a user can open new Outlook from the Start menu and manually locate the email in about five seconds — finishing before the notification path even loads. Launch times have largely caught up between the two apps, but the notification handoff exposes the real bottleneck.

The root cause is architectural rather than a tunable bug. New Outlook is a WebView2 (Chromium) wrapper around Outlook.com, so every interaction triggers a browser-style chain: resuming the web layer, authenticating, fetching the mail thread, and rendering it. It runs as roughly ten separate processes (GPU, service worker, utility, manager) versus Classic’s single process, idles at 490–636 MB of RAM against Classic’s ~117–148 MB, and burns more CPU at rest. Microsoft has tested a “Delayed Message Timing” API to diagnose WebView2 latency, but it isn’t being applied to the notification flow.

The broader story is forced migration: Microsoft shut down the native UWP Mail and Calendar apps in late 2024 and pushed users onto the web wrapper, with the enterprise opt-out deadline slipping a full year to March 2027. Recent updates have closed feature gaps — shared calendars, PST import, a unified inbox — but performance stays capped by the web-app model. The only real fix floated is a rewrite on native WinUI, which Microsoft is reportedly now committed to, potentially including a future native Outlook.