Skip to main content

Dashboard Not Loading? Fix TradeLyser UI

The TradeLyser dashboard is your command center for P&L widgets, sync status, and session overview. When the page stays blank, spins indefinitely, or shows partial widgets, the issue is usually local—browser cache, extensions, network—or account data still importing. This guide walks through dashboard not loading fixes without risking your trade history.

If trades exist but numbers look wrong after the UI loads, switch to Incorrect P&L or Missing Trades.

Symptoms and what they suggest​

SymptomLikely cause
White screen after loginJavaScript blocked; extension conflict; cache corruption
Infinite loading spinnerSlow network; API timeout; heavy date range
Login works, dashboard emptyNo trades imported yet; wrong account selected
Widgets missing but header loadsWidget layout or template issue
Works on phone, not desktopBrowser-specific cache or extension
Error banner with codeServer or account issue—note code for support

Quick fixes (try first)​

  1. Hard refresh — Ctrl+F5 (Windows) or Cmd+Shift+R (Mac).
  2. Incognito / private window — Disables most extensions temporarily.
  3. Different browser — Chrome or Edge recommended.
  4. Check status — Broker or TradeLyser maintenance (support can confirm).
  5. Log out and in — Refreshes session token.

If incognito works, the root cause is almost always cache or an extension.

Detailed causes and solutions​

1. Browser cache and stale assets​

Symptoms: Dashboard broke after a product update; old JavaScript errors in console.

Fix:

  1. Clear cache for app.tradelyser.com (last 24 hours is often enough).
  2. Hard refresh twice.
  3. Avoid “soft” reload only (F5) after deployments.
  4. If on corporate proxy, clear SSL state once if certificates were updated.

After major releases, clearing cache once is normal—see refresh dashboard.

2. Browser extensions and ad blockers​

Symptoms: Blank dashboard; console shows blocked scripts or net::ERR_BLOCKED_BY_CLIENT.

Fix:

  1. Disable ad blockers, privacy badgers, and script blockers for TradeLyser.
  2. Whitelist analytics only if required by your IT policy—do not block core app domains.
  3. Test incognito with extensions disabled by default.
  4. Re-enable extensions one by one to find the culprit.

3. Internet connection, VPN, and DNS​

Symptoms: Timeout; “network error”; partial widget load.

Fix:

  1. Verify general browsing works; try mobile hotspot.
  2. Disable VPN—some routes to CDN or API fail geo checks.
  3. Switch DNS temporarily if only TradeLyser fails.
  4. Corporate firewall may block WebSockets—ask IT to allow app domains.

4. Unsupported or outdated browser​

Symptoms: Layout broken; buttons unclickable.

Fix:

Use current versions of:

  • Google Chrome (recommended)
  • Microsoft Edge
  • Mozilla Firefox
  • Safari (current macOS/iOS)

Update the browser; disable compatibility mode on old Internet Explorer emulations.

5. Account has no data yet​

Symptoms: Dashboard skeleton loads; all metrics zero; new user.

Fix:

  1. Connect broker or import CSV.
  2. Run sync.
  3. Confirm trades on Trades page with All time filter.
  4. Return to dashboard and customize widgets if panels stay empty.

6. Wrong account or heavy filters​

Symptoms: Dashboard worked before; now empty for “today.”

Fix:

  1. Switch to correct trading account (switch accounts).
  2. Widen dashboard date scope.
  3. Reduce simultaneous heavy filters on large histories—very wide ranges on huge datasets load slower.

7. Widget layout corruption​

Symptoms: Header fine; widget grid empty or error per tile.

Fix:

  1. Customize dashboard → reset layout or re-add widgets.
  2. Try switch templates.
  3. Refresh dashboard data source.

8. Session expired​

Symptoms: Redirect loop; login page flash; 401 errors in network tab.

Fix:

  1. Log out completely.
  2. Clear cookies for TradeLyser only if loop persists.
  3. Log in again; enable manage sessions review if suspicious.

9. Local device performance​

Symptoms: Tab freezes; fan spins; millions of trades imported.

Fix:

  1. Close unused tabs.
  2. Narrow default date range for routine use.
  3. Archive very old years to separate account labels if you maintain multiple import buckets.
  4. Prefer desktop for heavy reports.

Using browser developer tools (optional)​

For power users and support tickets:

  1. Open Developer Tools (F12).
  2. Console tab — red errors (copy text).
  3. Network tab — reload; filter failed (red) requests.
  4. Note failing URL, status code (403, 500), and time.

Send screenshots to support—do not post API tokens from headers.

Isolation workflow​

Incognito test
    ├─ Works → disable extensions / clear cache
    └─ Fails → network / account / service issue
         ├─ Trades page loads? → widget/layout focus
         └─ Trades page empty? → import/sync focus

Mobile vs web​

If mobile dashboard works but web does not, prioritize web cache and extensions. If both fail, suspect account or service-wide issue.

When dashboard loads but sync button fails​

That is not a dashboard rendering issue—follow Trades Not Syncing or Connection Failed.

Prevention and performance habits​

  • Clear cache after announced major releases.
  • Keep one primary browser profile for trading.
  • Avoid running dozens of realtime widgets you do not use.
  • Sync before opening dashboard on slow connections.
  • Use widget preferences to reduce load.

Contact support​

Email support@tradelyser.com or use Pro chat with:

  • Screenshot or screen recording of blank/spinner state
  • Browser name and version
  • OS (Windows 11, macOS, etc.)
  • Whether incognito worked
  • Console error text if available
  • TradeLyser login email and approximate time (IST)

Frequently asked questions​

Is dashboard down for everyone?​

Check with support or community channels; if incognito on multiple networks fails, it may be incident-level.

Will clearing cache delete my trades?​

No—trades live on the server. You may need to log in again.

Why only P&L widget broken?​

Reset widget layout or switch template; other widgets may still fetch data.

Does dark mode cause loading issues?​

Rarely; switch theme to test if custom CSS extensions inject styles.

Can firewall allowlist fix this?​

Yes—IT must allow HTTPS and WebSocket endpoints used by the app.

Dashboard slow but loads—is that the same guide?​

Partially—see performance section and reduce filters; not a hard failure.

Widget-by-widget troubleshooting​

If the shell loads but individual tiles fail:

Widget typeCheck
P&L summaryDate range; account; trades exist for period
Performance chartEnough closed trades; try narrower window
Open positionsBroker connected; live P&L sync
Win rateTags/filters not excluding losses
Calendar heatmapTrades assigned to journal days

Remove and re-add the widget from add widgets. Switch to a simpler template to confirm data exists.

After login redirect issues​

Some users bookmark an old dashboard URL or land on a cached route after deploy:

  1. Navigate from the app menu: Dashboard (not a saved deep link).
  2. Update bookmarks to app.tradelyser.com root after login.
  3. If your organization uses SSO or email magic links, complete the full redirect chain without blocking cookies.

Coordinating with broker maintenance windows​

Broker maintenance often coincides with dashboard “empty” feelings—widgets depending on live quotes may show stale zeros while historical trades still exist under Trades. Separate UI load failure (this guide) from live data unavailable (wait for broker API or use closed-trade widgets only).

Desktop vs mobile troubleshooting matrix​

TestDesktop webMobile app
Incognito / fresh sessionPrimary isolation stepForce-close app; reinstall only if persistent
NetworkDisable VPN; try hotspotToggle Wi‑Fi / mobile data
Account dataTrades page All timeSame account logged in
ExtensionsDisable ad blockersN/A
CacheClear site dataApp cache from OS settings

If desktop fails but mobile works, focus on browser cache and extensions. If both fail, prioritize connection and sync over widget settings.

When to stop refreshing and contact support​

Stop after two full isolation cycles (incognito + cache clear + second browser) if the dashboard still shows a blank shell with console errors referencing 500 or 403 codes. Include the error text and whether Trades page loads—support routes UI-only bugs differently from account-wide data issues.

Accessibility and zoom settings​

Browser zoom above 200% or OS display scaling can occasionally clip widget grids on small laptops. Reset zoom to 100% (Ctrl+0) and reload. If layout returns, increase font size inside TradeLyser preferences instead of browser zoom where available (UI preferences).

Keep your browser updated to the latest stable channel—security patches also fix rendering bugs that mimic dashboard failures.

Table of Content