Cathy Liu
08/13/2026, 1:30 AMkapa.ai
08/13/2026, 1:30 AM/edit with /debug in the URL — this downloads the exact SQL GoodData runs against your database.
• Run that SQL directly on your database to check execution time, heavy joins, or timeouts.
• Try removing metrics one by one to identify which is the heavy driver (the first metric acts as the SQL "driver"). [Performance Debugging]
3. Check for HTTP/1.1 Connection Limits On large dashboards, browsers limit concurrent requests to ~6 per domain. If your hosting environment only supports HTTP/1.1, requests queue up and cause slowness. The fix is to ensure your server supports HTTP/2 or HTTP/3 (e.g., by placing a CDN like CloudFront in front of your app). [HTTP Limits Thread]
4. Collect Information for Support To help GoodData Support investigate further, please gather:
• Trace IDs from the Network tab in browser DevTools during a slow load
• A HAR file captured from Chrome DevTools during the issue
• Exact timestamps (with timezone) of when the slowness occurs
• Whether the issue affects all users or specific ones, and all dashboards or just this one [Support Investigation]
As a quick test, try loading the same dashboard in Firefox — if it's faster there, the issue may be browser-specific.
The GoodData Support team monitors this channel and will jump in if needed. Feel free to share Trace IDs here for further investigation! 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups.
👀 Our Support team monitors all messages and will jump in if needed.Mauricio Cabezas
08/13/2026, 2:07 AMCathy Liu
08/13/2026, 3:32 AMJoseph Heun
08/13/2026, 7:25 AMJoseph Heun
08/13/2026, 8:29 AMJoseph Heun
08/13/2026, 9:18 AMJan Kos
08/13/2026, 3:06 PMCathy Liu
08/13/2026, 10:18 PM