Performance

Performance philosophy

Most CMS platforms accumulate performance debt — bloated plugins, unoptimized queries, and render-blocking assets. Whoopix minimizes overhead by design:

• No plugin architecture adding runtime weight
• Optimized database queries with indexing for large catalogs
• Minimal PHP execution per request in headless/API mode
• Frontend team controls asset loading and rendering strategy
• Built-in caching layers at multiple levels

See the Performance feature page for product positioning.

Caching layers

Whoopix supports multi-level caching for production environments:

CDN integration

Whoopix integrates with CDN providers for global edge delivery:

• Cloudflare — recommended; cache rules, SSL, DDoS protection, and auto-purge via webhook
• Static assets — CSS, JS, images served from CDN with long cache headers
• API responses — cacheable GET endpoints with Cache-Control headers
• Auto-purge — webhook triggers CDN cache clear when content publishes

Core Web Vitals

Whoopix architecture supports strong Core Web Vitals scores:

The Insights module in the admin panel provides performance monitoring data to track improvements over time.

Scaling at volume

Whoopix handles sites with thousands of programmatic pages without performance degradation:

• Database indexing optimized for large page and product catalogs
• Paginated admin lists — no loading 10,000 rows in a single view
• Batch sitemap generation via cron, not on every request
• API pagination and filtering for frontend consumption at scale
• Horizontal scaling — add app servers behind load balancer with shared Redis cache

Recommended production stack

Whoopix runs on standard LAMP/LEMP stacks — no proprietary runtime required. See hosting partners for recommended providers.