Back

Performance Neutrality

Caracal Lite is engineered to operate within strict performance budgets to preserve storefront speed, Core Web Vitals stability, and checkout continuity.

1. Payload Budget

  • Compressed Size: < 15KB (gzip or brotli)
  • No External Framework Dependencies
  • No Third-Party Runtime Calls

The engine is self-contained to eliminate waterfall amplification or chained script latency.

2. Execution Model

  • Non-Blocking Initialization
  • Asynchronous Runtime Evaluation
  • Idle-Cycle Utilization (where available)

The engine does not delay First Contentful Paint (FCP), Largest Contentful Paint (LCP), or Time to Interactive (TTI). Execution occurs post-critical rendering path.

3. Delivery Architecture

  • Served via geographically distributed Edge Points of Presence (PoPs)
  • Target TTFB: < 50ms under standard network conditions
  • TLS-enforced delivery

No runtime calls are made after initial load.

4. Caching Strategy

  • Browser Cache-Control: max-age=3600
  • Immutable asset versioning
  • No localStorage, sessionStorage, or cookie persistence

Caching minimizes repeat-request latency while maintaining stateless execution integrity.

5. Performance Boundary

Caracal Lite is designed to be performance-neutral. It does not:

  • Inject layout-shifting DOM elements
  • Perform synchronous blocking operations
  • Initiate background network polling
  • Execute continuous runtime observers beyond defensive scope