Most dashboard slowness comes from one of three sources: query-side, network-side, or browser-side. Diagnosing which one is the culprit takes about 60 seconds.
Step 1 — Check if it's just one tab
Open the dashboard in a fresh incognito/private window. If it's fast there but slow in your usual session, it's a browser-side issue (extensions, cached state, accumulated tabs). Skip to Step 4.
If it's slow in incognito too, it's server-side or network-side. Continue to Step 2.
Step 2 — Check the date range
Pulling a wide window of high-traffic data is genuinely heavy. The dashboard query has to scan a large slice of events. If you opened the dashboard with All time (or a long custom range) selected on a high-volume site, the first render takes longer the more history you have:
- A year-plus of history on a high-volume site (1M+ events/month) → a 5-10 second initial load is normal.
- Two years (the Pro retention window) → up to 15 seconds for the first render; subsequent renders are cached and instant.
- Four years (the Scale retention window) → up to 30 seconds for the first render on very high-traffic sites.
Quick fix: in the period selector, switch to Last 30 days. The dashboard re-loads in under 2 seconds. Use a wider window only when you actually need it.
Step 3 — Check the filter complexity
Each active filter adds a JOIN and a WHERE clause to the query. With 5+ active filters on a wide date range, queries can compound to 30+ seconds.
Quick fix: in the filter bar, click Clear all and re-add the most important 1-2 filters. The dashboard reloads almost instantly.
Step 4 — Browser troubleshooting
Common browser-side culprits:
Extensions
Some privacy extensions (uBlock Origin with aggressive lists, Privacy Badger in strict mode) intercept requests to app.zenovay.com or api.zenovay.com. The dashboard hangs because requests are silently blocked.
Fix: allowlist app.zenovay.com and api.zenovay.com in your extension. Or open the dashboard in incognito where extensions are usually disabled.
Stale localStorage
The dashboard caches query results in your browser's localStorage so revisits load instantly. Over a long-running session this cache can grow large enough to slow the first render.
Fix: sign out, clear app.zenovay.com localStorage in DevTools (Application → Storage → Local Storage), sign back in.
Too many tabs
The dashboard keeps a real-time connection open for live visitor updates. With many Zenovay tabs open at once, those connections and the background refreshes can compete for resources and make individual tabs feel sluggish.
Fix: close tabs you're not actively using. The dashboard reconnects automatically when you focus a tab again.
Step 5 — Network troubleshooting
Open DevTools → Network → reload the dashboard. Look at the slowest request:
- If it's a request to
app.zenovay.com(HTML/JS), CDN cache is your issue. Reload the page; usually clears on second load. - If it's a request to
api.zenovay.com/api/...(JSON queries), the database is slow. This is server-side. - If multiple requests are slow regardless of host, your local network is the issue (corporate VPN, captive portal, ISP routing).
Step 6 — Check status page
Open status.zenovay.com. If there's an active incident affecting "Dashboard performance" or "Database queries", it's not your environment — wait for the all-clear.
When to email support
If you've exhausted Steps 1-6 and the dashboard is still slow:
- Email [email protected] with: domain, date range you were viewing, browser/OS, and a HAR file from DevTools (Network → right-click → Save as HAR with content).
We can pull the relevant query traces from our side and identify whether it's a query-plan regression, a hot-key contention, or something on your specific account.
Does my plan affect load time?
Your plan doesn't give some accounts faster queries than others. What it does change is how far back you can look:
- Free: 1 year of history
- Pro: 2 years
- Scale: 4 years
- Enterprise: custom
A wider retention window means more data to scan when you select a long date range, so the first render of a multi-year view on a high-traffic site takes longer than a 30-day view. The fix is the same on every plan: narrow the date range to what you actually need, then widen it only when necessary.