[Bug] Opening a broken or unavailable link redirects to my account, but loads much slower than direct access

[Biyakuga]

Description:

When I open a MEGA link that is broken, down, or otherwise unavailable for reasons such as deleted content, expired links, disabled links, account issues, or a missing decryption key. I'm redirected to my own MEGA account automatically. However, the loading process in this case is much slower compared to simply opening a new tab and going directly to my MEGA account.

Example:

• Direct access to MEGA account: Loads in under 1 minute.
• Redirect after opening a broken/unavailable link: Takes 5 to 10 minutes to fully load the account.

It seems like the MEGA web client may be bypassing cache or reinitializing the session completely when redirected from an invalid link, resulting in a much longer load time.

Steps to Reproduce:

1. Open a MEGA link that is broken or unavailable.
2. Most of the time, you will see a message indicating that the link is unavailable, along with a button such as "OK, got it" click this button to proceed.
3. Wait to be redirected to your personal MEGA account.
4. Observe the significantly slower loading time compared to a direct visit.
5. Important: This issue is most noticeable with large accounts (e.g., 10TB or more of data, and 2 million+ files). Please test with a similarly sized account to reproduce the behavior accurately.

Expected Behavior:

Redirecting from a broken or unavailable link should load the user's account with the same performance as a direct visit, ideally using cached resources or session data where applicable.

Environment:

• Operating System: Windows 11 25H2 (latest version as of October 2025)
• Browsers Tested:
  • Microsoft Edge (latest stable release)
  • Google Chrome (latest stable release)
• MEGA Browser Extension: Installed and up to date on both browsers and no other browser extensions or third-party apps in use only the official MEGA extension
• Account Size: Affects large accounts (e.g., 10TB+ storage and over 2 million files)
• Behavior Consistency: Issue has been consistently reproducible across both browsers for over a year and a half