Slow performance
For: Any userOrg admin
Last reviewed:
Before you report slowness
- Check status. If an incident is declared, it is not local.
- Try in another browser (Chrome incognito) to rule out extensions.
- Try on another network (mobile data vs Wi-Fi). A corporate proxy can add latency.
- If only a specific screen is slow, note the exact URL.
Report taking too long
Some reports consolidate millions of rows. Expected times:
| Report | < 100k members | 100k–500k | > 500k |
|---|---|---|---|
| Church health | < 3 s | < 10 s | up to 30 s |
| Attendance trends (12 months) | < 5 s | < 20 s | up to 60 s |
| Member growth (5 years) | < 10 s | < 30 s | up to 2 min |
| Multi-campus consolidated performance | < 10 s | < 30 s | up to 2 min |
If outside these ranges, open a ticket with the report URL and approximate member count.
Slow initial load
- The first load of the day after a long idle can take 2–3 seconds extra (cold cache). Subsequent loads are immediate.
- If your organization has more than 100 active custom fields in CRM, the member list load can slow down. Consider archiving unused fields.
”Infinite spinner” on a screen
- Refresh with
Ctrl + F5. - If it persists, open DevTools → Network and check for stuck requests. Share the exported HAR when opening a ticket.
When to escalate
- If slowness is generalized and sustained for more than 10 minutes, an incident is likely. Check status and, if not declared, report it from report incident.
Was this helpful?id:
performanceLast updated on