Mixpanel report building performance is very slow—how can I improve UI responsiveness?

tobias.willhauck · 2026-06-08T09:51:14.343Z

Lately the performance i experience when using Mixpanel - especially when building reports - is very bad. The UI reacting is extremely slow to input - sometimes I need to wait for several seconds for every action (click, drag&drop, mouseover) i try to do. Is this an overall problem or is there anything I can do on my side?

Mixpanel report building performance is very slow—how can I improve UI responsiveness? | Mixpanel Community

1 comment

· Sorted by Oldest

kapa.ai
APP
·
(edited)·
Mixpanel’s public docs don’t mention any current, general UI performance incident, so I can’t say whether there’s an ongoing widespread issue. They do describe a few things that can make reports feel slow and what you can do about them.
1. Check for known incidents and contact Support
Mixpanel recommends checking the status page and contacting Support if you’re seeing persistent issues:
Status page: https://www.mixpanelstatus.com/
Support form (logged in or not): https://mixpanel.com/get-support
Response times depend on your plan (Free, Growth, Enterprise, etc.), but all plans can open tickets and get help diagnosing performance problems (including account‑specific ones). [Response times]
2. Things you can try in reports
Some performance issues come from very heavy queries rather than the UI itself. Mixpanel suggests:
Reduce breakdowns / segments: High-cardinality breakdowns can hit segment limits and strain query capacity. Narrow the time range, add filters, or reduce the number of breakdowns to keep segment counts lower. [Segment limits]
Use CSV export for very large segment sets: If you truly need many segments, exporting to CSV has higher limits and can be more efficient. [Segment limits]
Leverage query result caching: If you’re re-running the same heavy query, Mixpanel caches results for up to 1 hour–14 days depending on the date range, so re-opening the same report should be fast. If you need fresh data, use “Refresh Data,” but be aware that forces a full recompute. [Query caching]
If you’re on Enterprise with very large data: Enable Query Time Sampling (lightning bolt icon) to run reports on a 10% user sample for much faster iteration, then turn it off once you’ve finalized the query. [Query sampling]

3. If it feels like general UI lag (clicks, drag & drop, mouseover)
The docs and blogs emphasize that Mixpanel invests heavily in backend performance and interactive speeds, but they don’t provide specific troubleshooting steps for front‑end lag on a single account or browser. [Product analytics you can afford] Because of that, I don’t have official guidance on browser-specific fixes (e.g., clearing cache, extensions, etc.) in the knowledge sources. Given your description (multi‑second delay on basic UI actions), this is not expected behavior and is best handled as a Support case so they can:
Check if your project is hitting any internal limits (e.g., hot shards, extreme cardinality) that might slow queries. [Hot shard limits]
Verify whether there’s any ongoing incident affecting your region or org.
Look at your specific reports and environment.
You can open a ticket from within Mixpanel via Help → Contact Support, or via https://mixpanel.com/get-support, and describe:
That the UI itself is lagging (not just query results),
Rough time window and your region,
Whether it happens across all reports/browsers or only some.
If you’d like, paste an example of a “slow” report configuration (events, breakdowns, date range) and I can help you simplify it using the documented best practices.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

kapa.ai
APP
·
(edited)·
Mixpanel’s public docs don’t mention any current, general UI performance incident, so I can’t say whether there’s an ongoing widespread issue. They do describe a few things that can make reports feel slow and what you can do about them.
1. Check for known incidents and contact Support
Mixpanel recommends checking the status page and contacting Support if you’re seeing persistent issues:
Status page: https://www.mixpanelstatus.com/
Support form (logged in or not): https://mixpanel.com/get-support
Response times depend on your plan (Free, Growth, Enterprise, etc.), but all plans can open tickets and get help diagnosing performance problems (including account‑specific ones). [Response times]
2. Things you can try in reports
Some performance issues come from very heavy queries rather than the UI itself. Mixpanel suggests:
Reduce breakdowns / segments: High-cardinality breakdowns can hit segment limits and strain query capacity. Narrow the time range, add filters, or reduce the number of breakdowns to keep segment counts lower. [Segment limits]
Use CSV export for very large segment sets: If you truly need many segments, exporting to CSV has higher limits and can be more efficient. [Segment limits]
Leverage query result caching: If you’re re-running the same heavy query, Mixpanel caches results for up to 1 hour–14 days depending on the date range, so re-opening the same report should be fast. If you need fresh data, use “Refresh Data,” but be aware that forces a full recompute. [Query caching]
If you’re on Enterprise with very large data: Enable Query Time Sampling (lightning bolt icon) to run reports on a 10% user sample for much faster iteration, then turn it off once you’ve finalized the query. [Query sampling]

3. If it feels like general UI lag (clicks, drag & drop, mouseover)
The docs and blogs emphasize that Mixpanel invests heavily in backend performance and interactive speeds, but they don’t provide specific troubleshooting steps for front‑end lag on a single account or browser. [Product analytics you can afford] Because of that, I don’t have official guidance on browser-specific fixes (e.g., clearing cache, extensions, etc.) in the knowledge sources. Given your description (multi‑second delay on basic UI actions), this is not expected behavior and is best handled as a Support case so they can:
Check if your project is hitting any internal limits (e.g., hot shards, extreme cardinality) that might slow queries. [Hot shard limits]
Verify whether there’s any ongoing incident affecting your region or org.
Look at your specific reports and environment.
You can open a ticket from within Mixpanel via Help → Contact Support, or via https://mixpanel.com/get-support, and describe:
That the UI itself is lagging (not just query results),
Rough time window and your region,
Whether it happens across all reports/browsers or only some.
If you’d like, paste an example of a “slow” report configuration (events, breakdowns, date range) and I can help you simplify it using the documented best practices.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

1 comment

1. Check for known incidents and contact Support

2. Things you can try in reports

3. If it feels like general UI lag (clicks, drag & drop, mouseover)

1. Check for known incidents and contact Support

2. Things you can try in reports

3. If it feels like general UI lag (clicks, drag & drop, mouseover)