Grepiac is slow on my phone (or computer)

Try first

Two things that resolve the majority of slow-page reports:

1. Hard refresh (Ctrl/Cmd-Shift-R). Resolves stale-JS issues.
2. Different browser or private window. Rules out browser extensions and corrupted local storage.

Symptom: Specific page is slow, others are fine

Coach dashboard slow with a large roster

If you have 30+ athletes, the roster panel queries can take longer. Workarounds:

• Use the team filter at the top of the dashboard to scope to a subset.
• Narrow the recent-activity feed window if exposed.

Athlete analytics page slow

Sport analytics aggregates across activities. With years of history, the queries get heavier. Workaround:

• Narrow the date window (default 90 days is faster than 365).

Macrocycle dashboard or admin queries

The admin list views fetch large rowsets. Use filters (team, status, athlete) to scope.

Symptom: All pages are slow

• Slow internet: open a speed test. If it is slow there, it is slow here.
• VPN or corporate proxy: try disabling the VPN briefly to test.
• Browser memory pressure: close other tabs. Restart the browser.
• Cloud outage: check the status page or social channels for outages. Grepiac depends on standard cloud services.

Symptom: Activity upload takes minutes

• Large file: a multi-hour FIT file with high-rate data can be 5 to 20 MB. Upload time depends on your connection.
• ZIP file with many activities: the parser processes each file. Progress should show on the upload page.

The parse is usually faster than the upload itself on typical connections.

Symptom: Chart rendering is slow

Sport analytics charts can be heavy when:

• The date window is very long.
• The athlete has thousands of activities.

Narrow the date window or filter by sub_sport (indoor_cycling only, for instance) to lighten the query.

Symptom: Mobile-specific slowness

Grepiac is responsive but not a native mobile app. Some pages are heavier on mobile:

• The coach dashboard.
• Sport analytics with many charts.
• Race planning wizard.

Workarounds:

• Use a tablet or laptop for the heaviest pages.
• On phone, use the lighter pages (wellness log, race list, race detail).

What we are working on

• Lazy-loading of analytics charts.
• Server-side caching on heavier queries.
• A mobile-specific lighter view.

When to escalate

If a specific page is consistently slow even after a hard refresh and a different browser, file a bug with:

• The exact URL.
• What you were trying to do.
• The browser, OS, and approximate time.
• Whether the slowness is consistent or intermittent.

See also: Something is not working, Activity upload troubleshooting.