Performance
LCP 0.6 s · TBT 0 ms · CLS 0.00
Technical specification
The Engine
Full disclosure of the architecture for enterprise CTOs: how signals from the browser travel through the Service Worker interceptor into IndexedDB and from there sync idempotently against serverless endpoints.
Lighthouse target profile
The performance budget of this platform is set so that all four categories stay at 100/100 permanently.
Accessibility
WCAG 2.2 AA · contrast ≥ 7:1
Best Practices
HTTPS · no console errors
SEO
Semantics · JSON-LD · canonicals
Architecture diagram · data flow
HTML5 Browser APIs
Geolocation, Network Information, Storage Manager and Page Visibility deliver the raw signals directly in the client.
Service Worker interceptor
Fetch events are intercepted: navigations run network-first, hashed assets cache-first. If the network drops, the cache answers without delay.
IndexedDB via Dexie.js
Every record is persisted locally in a transaction and flagged with a synced marker. The queue survives reloads, tab switches and app restarts.
Serverless Supabase endpoints
As soon as connectivity returns, the background sync routine replays the queue idempotently against serverless endpoints — deliberately simulated in this prototype.
Specification in detail
Stack & budget
- Rendering
- SSR + hydration, file-based routing
- Persistence
- IndexedDB (Dexie.js) + LocalStorage
- JS budget
- < 120 kB gzip on the critical route
- Fonts
- self-hosted, variable subsets
- Images
- no raster assets on the critical path
- Interaction
- 0 ms transition and animation delay
Privacy by Design (GDPR)
- Third-party requests
- 0
- Cookies
- 0 — no consent banner required
- Tracking / analytics
- not embedded
- External fonts
- not embedded
- Third-country transfer
- does not occur
- Telemetry storage
- device only