FrankenPHP vs Traditional WordPress Hosting

Published April 21, 2026

FrankenPHP vs Traditional WordPress Hosting

For two decades, WordPress hosting meant Apache or Nginx plus PHP-FPM. FrankenPHP changes the equation fundamentally. Here's what's different and why it matters for your site's performance.

The Traditional Stack

In a typical WordPress setup:

1. A web server (Apache or Nginx) receives the HTTP request
2. It passes PHP requests to PHP-FPM via a socket or TCP connection
3. PHP-FPM manages a pool of PHP worker processes
4. A worker processes the request and returns HTML
5. The web server sends the response to the client

This architecture has two process managers communicating across a socket. Each hop adds latency, and managing two separate systems adds operational complexity.

The FrankenPHP Approach

FrankenPHP embeds PHP directly into Caddy, a modern web server written in Go:

1. Caddy receives the HTTP request
2. PHP runs as threads within the same process
3. Response is sent directly to the client

No socket communication, no separate process manager. PHP and the web server are one process.

Performance Difference

• Time to First Byte: 30-50% faster due to eliminated inter-process communication
• Memory efficiency: One process instead of two reduces baseline memory usage
• Concurrency: Go's goroutine model handles thousands of concurrent connections efficiently
• HTTPS: Caddy's automatic TLS with zero configuration

Real-World Impact

On SiteICO, WordPress sites served via FrankenPHP consistently achieve sub-200ms TTFB for uncached dynamic pages. Cached pages serve in under 50ms. For comparison, a typical shared hosting Apache setup delivers 500-2000ms TTFB for the same pages.

Stability and Maturity

FrankenPHP reached version 1.0 in 2024 and has been production-stable since. It's maintained by Dunglas (creator of API Platform) and supported by a growing ecosystem. At SiteICO, we've been running FrankenPHP in production for all WordPress sites with excellent reliability.

Should You Switch?

If you manage your own server, migrating to FrankenPHP requires learning Caddy's configuration format (Caddyfile). If you use managed hosting, choose a host that's already made the switch. SiteICO runs all WordPress sites on FrankenPHP by default, so you get the performance benefits without any configuration.