Performance
CoralLedger Comply is built on a server-rendered Blazor architecture that prioritises responsiveness on Caribbean network conditions. This page documents the actual performance properties of the platform rather than aspirational targets.
How the platform is built
Comply runs as a Blazor Server application — UI rendering happens on the server, with the browser maintaining a SignalR connection over which DOM updates flow. This architecture has specific performance properties:
- Initial page renders are server-side, so the browser does not need to download a large JavaScript bundle on first load.
- Subsequent navigation reuses the SignalR connection, so page transitions are fast and feel app-like.
- Real-time dashboard updates push from the server when underlying data changes (e.g. new transaction imported, return state changed) without you needing to refresh.
This is the same architectural pattern as products like Microsoft Teams or GitHub Codespaces — interactive web with server-rendered UI.
What this means for you
Responsive interactivity
Dashboards and lists update without a full-page reload. Filtering a transaction grid, switching businesses, or recalculating a return preview happens in place via the SignalR channel.
Large data handling
Comply is designed to handle large transaction volumes per business without paginating you out of your data:
- CSV imports of thousands of transactions in a single file. The import progress is streamed back over SignalR so you see the row-by-row progress live.
- Returns that cover full fiscal years for businesses with high transaction volumes.
- Server-side filtering and sorting of transaction histories so the browser does not need to hold the full dataset in memory.
Real-time updates
The Client Dashboard maintains a SignalR connection to /dashboardHub. Updates pushed across this connection include:
- Compliance score recalculations after categorisation changes
- New transactions imported by team members
- Status changes on returns (e.g. Awaiting Lodgement → Lodged)
- Compliance alerts firing or clearing
You see these reflect on the dashboard without refreshing.
Caribbean network reality
The platform is tested against the network conditions a typical Bahamian business will experience — including 3G mobile connections and bandwidth-limited periods. Specific accommodations:
- Skeleton placeholders show during data loads so the page feels responsive even when the underlying query is slow.
- Per-page data loading runs in
OnAfterRenderAsyncso the initial render is not blocked by long-running queries. - SignalR retry + reconnect is built in — if the connection drops, the browser reconnects when the network comes back.
Supported Browsers
| Browser | Minimum Version |
|---|---|
| Chrome | 90+ |
| Firefox | 88+ |
| Safari | 14+ |
| Edge | 90+ |
Older browsers may render the platform but interactive features (SignalR live updates, modal dialogs, MudBlazor components) may not work correctly.
Reporting performance issues
If you experience slow performance:
- Clear your browser cache and reload the page
- Check your internet connection speed
- If the issue persists, contact hello@digitalcarib.com with:
- The page URL where slowness occurs
- The action you were taking when slowness started
- Your browser + version (and approximate connection speed if known)