Am I the only one who finds the FortiSASE portal painfully slow after the last update?

I've been navigating the FortiSASE portal for the better part of a year now, managing a deployment that spans several hundred remote users and a handful of cloud workloads. Historically, it's been... fine. Not snappy, but tolerable. The latency was something you could chalk up to the usual overhead of a security-focused SaaS console.

Then the last major update landed, presumably with a host of new features and security enhancements that the release notes glorified in the usual vague, marketese-laden paragraphs. Since that update, the performance has degraded from "tolerable" to "genuinely painful." We're talking about multi-second delays on basic interactions: clicking from the dashboard into a user's detail page, expanding the policy list, even applying a simple filter to the event logs. The JavaScript console in my browser is littered with warnings about long-running tasks and slow network responses from their APIs.

What's particularly galling is that this is a tool we're supposed to use for operational oversight and rapid response. When an alert fires, waiting 8-10 seconds for the portal to render the full context of an incident is an operational anti-pattern. I've started timing it. A trivial sequence—navigate to `Security Events > Filter by High Severity > Select an event > View Forensic Details`—can take upwards of 30 seconds to complete, with multiple loading spinners appearing in sequence. This isn't a bandwidth issue on my end; other SaaS consoles (even far more complex ones) are responsive.

I'm curious if this is a widespread experience or if my tenant is somehow uniquely cursed. Has anyone else observed a significant performance regression? More importantly, has anyone found a workaround beyond the classic "clear your cache and cookies" advice from support? I've already engaged our account team, and the response was the predictable "we've noted the feedback and escalated to the product team," which is corporate speak for radio silence.

If you're also suffering, share your metrics. How many endpoints are under management? What's the geographic location of your primary console access? Any pattern to the slowness (e.g., policy editing vs. reporting)? Let's see if we can collectively pinpoint whether this is a global backend issue, a regional problem, or related to scale.

-- Cam