Slow loading and performance tips

MobilityManager is a web application built on Angular and a .NET API. If pages load slowly, freeze, or fail to refresh, the cause is often local, such as a stale browser session, network latency, or an outdated tab. This article gives practical steps to restore responsiveness.

Quick fixes to try first

1. Reload the page. A hard refresh (hold Shift while reloading, or press Ctrl+Shift+R, or Cmd+Shift+R on macOS) forces the browser to fetch the latest application files instead of a cached copy.
2. Sign out and back in. Your session token is valid for 8 hours; if it is close to expiry, background requests can stall or fail. A fresh sign-in issues a new token.
3. Close unused tabs. Several open MobilityManager tabs each hold their own data and can compete for memory and network.
4. Try a private or incognito window. If the app is fast there, a browser extension or a corrupted cache in your normal profile is the likely culprit.

Keep your environment healthy

• Use a current, supported browser. Modern evergreen browsers receive the performance and security updates the app is built for. See the related article on supported browsers.
• Clear the browser cache for the site if the interface looks broken or half-loaded after an update.
• Disable ad blockers or privacy extensions for the application's address; they can delay or block legitimate requests.
• Check your network. A slow or unstable connection, a saturated VPN, or a restrictive proxy can add latency to every request.

Work with large data sets efficiently

Long lists such as vehicles, bookings, or expense documents are paginated and filterable. To keep screens responsive:

• Apply filters and date ranges to narrow results rather than scrolling through everything.
• Move between pages instead of requesting the largest possible page size.
• Let exports and reports finish before starting another; running several heavy operations at once slows them all.

Tip: If only one module is slow while the rest of the app is fast, note which module and roughly how long it takes. That points support at a specific area rather than the whole system.

When to contact support

If slowness persists across browsers, devices, and networks, and affects more than one user, it may be a server-side issue. When you report it, include:

• What you were doing and which page or module was affected.
• The approximate time it happened, in your time zone.
• Any trace ID shown in an error message, which lets support locate the exact request in the logs.

Related

• Supported browsers
• Understanding trace IDs in error messages
• A document will not download
• Where my data is stored: multi-tenant isolation explained