Skip to content

Performance Issues

Optimize app performance and resolve speed problems.

App pages loading slowly:

Check performance:

  • Expected load time: < 2 seconds
  • Actual: 5-10 seconds

Causes:

  1. Large number of files (1000+)
  2. Slow internet connection
  3. Browser cache full
  4. Too many browser tabs open
  5. Computer resources low

Solutions:

  1. Enable pagination: Settings → Display → Items per page: 50
  2. Clear browser cache: Ctrl+Shift+Del
  3. Close unused tabs
  4. Use Chrome or Firefox (faster)
  5. Filter/search instead of browsing all

Uploads taking very long:

Check upload speed: Test: speedtest.net Required: 5+ Mbps upload Your speed: ? Mbps

Improve:

  1. Use wired connection (not WiFi)
  2. Close bandwidth-heavy apps
  3. Upload smaller batches (20-30 files)
  4. Upload during off-peak hours
  5. Contact ISP if consistently slow

Large files:

  • 1 GB @ 10 Mbps: ~13 minutes
  • 5 GB @ 10 Mbps: ~67 minutes
  • Use FTP for 100+ GB

Customers report slow downloads:

Check CDN: Settings → Performance → CDN Status: Should be “Enabled”

Solutions:

  1. Enable CDN: Settings → Performance
  2. Check file size (compress if >500 MB)
  3. Use optimized formats (MP4 not AVI, PDF not TIF)
  4. Verify R2/storage provider status
  5. Test from multiple locations

Monitor: Analytics → Performance → Download Speed Target: 10+ MB/s average


Search and filters slow:

Symptoms:

  • Search takes 10+ seconds
  • Filters timeout
  • Page hangs

Fix:

  1. Settings → Advanced → Database → Optimize
  2. Rebuild indexes
  3. Clear old data (delete test orders)
  4. Archive old files (>1 year)

Prevention:

  • Regular database maintenance
  • Don’t store test data
  • Archive old orders
  • Enterprise: Read replicas

Browser running out of memory:

Error: “Page unresponsive” or browser crash

Causes:

  • Too many files loaded
  • Memory leak in browser
  • Insufficient RAM

Solutions:

  1. Restart browser
  2. Close other tabs/apps
  3. Enable pagination
  4. Upgrade computer RAM (if old computer)
  5. Use desktop app (if available)

“Too many requests” error:

Error: HTTP 429 - Too Many Requests

Limits:

  • 1000 requests/hour
  • 100 requests/minute burst

Solutions:

  1. Slow down API requests
  2. Implement backoff/retry logic
  3. Cache responses
  4. Upgrade to higher tier (Enterprise)

Code example:

if (response.status === 429) {
const retryAfter = response.headers.get('Retry-After');
await sleep(retryAfter * 1000);
// retry request
}

Contact support for persistent performance issues.