Slow Dashboard or Timeout Errors

Dashboard is slow to load

The VisibilityIQ dashboard is a single-page application served via Cloudflare’s global edge network. If it’s loading slowly, the most common causes are:

Large audit result sets — Projects with very large crawls (10,000+ pages) may take a few extra seconds to load the findings view. Use filters to narrow the finding scope before loading detailed views.

Connector sync in progress — While a connector is syncing, certain views that depend on that data may be temporarily unavailable or slower than usual. Check Project → Connectors to see if a sync is running.

Browser extension conflicts — Ad blockers and privacy extensions sometimes interfere with the dashboard’s API calls. If you’re seeing loading spinners that never resolve, try disabling extensions temporarily.

Audit API timeouts (504)

If you see a 504 error while triggering an audit or fetching results, it usually means:

• A crawl is already running for this project (only one crawl can run at a time per project)
• The server is processing a large result set

Wait 30 seconds and try again. If timeouts persist, contact support — we may need to manually reset a stuck crawl.

”Something went wrong” errors

If you see a generic error message, open your browser’s developer tools (F12), go to the Console tab, and look for red error messages. Note the URL and error message text and include them in your support report — they dramatically speed up diagnosis.

Connector data not updating in the UI

If a connector sync completed but data isn’t reflected in the UI, try a hard refresh (Ctrl+Shift+R or Cmd+Shift+R). If data still isn’t showing, the sync may have succeeded at the transport layer but failed during processing. Check Project → Connectors for any error indicators and contact support if the issue persists.

Site audit not loading issue list

If the audit completes but the issue list shows a spinner indefinitely:

1. Hard refresh the page
2. Check if the project has more than 50,000 findings (very large crawls can stress the rendering layer)
3. Apply a severity filter to reduce the result set before loading

Contacting support for performance issues

Include:

• Your browser and OS version
• The project name and URL
• The approximate time the issue occurred
• Any error messages or console output

Email support@visibilityiq365.com.