Website Speed: How Your Hosting Provider Affects Performance

What Is TTFB and Why Should You Care?

Time to First Byte (TTFB) measures the interval between a browser requesting a page and receiving the first byte of the response. It captures everything your server does before sending data: DNS resolution, connection negotiation, SSL handshake, request processing, and response assembly.

Google considers TTFB over 800 ms poor and under 200 ms excellent. A shared host running overloaded Apache can deliver TTFB of 1-3 seconds on a cold request, while a well-tuned LiteSpeed or Nginx setup on a VPS can return sub-100 ms TTFB. TTFB is the gateway to every other performance metric. If the first byte takes two seconds, no amount of front-end optimization can make the page feel instant. Users expect pages to load in under three seconds, and nearly half abandon sites that take longer. Every 100 ms improvement can increase conversion rates by up to 7%.

Apache vs LiteSpeed vs Nginx: Server Stack Showdown

The web server software your host uses is the engine of your site. Three major players dominate hosting: Apache, Nginx, and LiteSpeed.

Apache uses a process-per-connection model that consumes significant RAM under concurrent traffic. Each process loads a full copy of the server's configuration and modules. On shared hosting, Apache crumbles under traffic spikes because each request competes for processes bogged down by other tenants.

Nginx uses an event-driven, asynchronous architecture with a single master process delegating to workers that handle thousands of connections simultaneously. This is far more memory-efficient. Nginx excels at serving static content and reverse-proxying dynamic requests. Most high-performance setups use Nginx as a reverse proxy in front of PHP-FPM. The tradeoff is no native .htaccess support and a less beginner-friendly configuration syntax.

LiteSpeed is a drop-in Apache replacement that supports .htaccess and mod_rewrite rules, so migrating requires zero configuration changes. Under the hood it uses the same event-driven architecture as Nginx but with significant optimizations. Its PHP handler, LSAPI, outperforms traditional PHP-FPM because it maintains persistent worker pools and uses zero-copy response buffering. LiteSpeed also includes built-in HTTP/3, QUIC support, and automatic cache purging.

Real-world benchmarks consistently show LiteSpeed outperforming both competitors for PHP sites. In controlled tests serving a WooCommerce store under 200 concurrent users, Apache averaged 12 requests per second with a 4.2 second response time. Nginx with PHP-FPM averaged 45 requests per second with a 1.1 second response time. LiteSpeed with LSAPI averaged 82 requests per second with a 0.6 second response time — roughly 7x more throughput than Apache and 2x over Nginx for dynamic PHP workloads.

Caching Layers: Full-Page, Object, and Opcode

Caching is the most impactful optimization your host can provide. Three separate caching layers work together to minimize processing time.

Full-page caching stores the complete rendered HTML and serves it to subsequent visitors without executing PHP or querying the database — delivering a static file in microseconds. This bypasses the entire CMS bootstrap, PHP execution, and database queries. LiteSpeed Cache generates cached HTML at the server level and serves it before PHP even loads. Nginx with FastCGI Cache achieves similar results by caching PHP-FPM output at the proxy level. Without full-page caching, every visitor forces the server to execute PHP and run database queries.

Object caching stores expensive database queries and complex computations in memory using Redis or Memcached. Retrieving cached data takes under a millisecond versus 10-100 milliseconds for a SQL query. Object caching is essential for sites using page builders, custom post types, or complex taxonomy queries. Without it, every page load hits the database for menus, widgets, post metadata, and user sessions. A site with Redis can reduce database query counts by 80-90%.

Opcode caching compiles PHP scripts into bytecode and stores them in shared memory, eliminating the parse and compile steps on every request. OPcache is bundled with PHP and enabled by default on modern stacks. PHP with OPcache runs 2-3x faster than without it.

The best hosts enable all three caching layers by default and provide control over lifetimes, purging rules, and exclusion patterns. When evaluating a host, ask whether they support server-level full-page caching, Redis or Memcached for object caching, and adequate OPcache memory allocation.

CDN Integration and Global Edge Delivery

A CDN distributes your site's assets across a global network of edge servers. A visitor in Tokyo receives cached assets from the nearest edge node rather than from your origin server. This reduces latency from hundreds of milliseconds to single digits. Modern CDNs like Cloudflare, QUIC.cloud, and BunnyCDN also offer full-page caching at the edge across 300+ locations worldwide.

The best hosts provide one-click CDN setups with automatic cache purging when you update content. LiteSpeed-based hosts often include QUIC.cloud integration, which is tightly coupled with the LiteSpeed Cache plugin and provides automatic image optimization, CSS/JS minification, and CDN delivery from a single toggle.

When assessing CDN capabilities, look for automatic purging on content updates, HTTP/2 and HTTP/3 at the edge, DDoS protection, and real-time analytics. A host that simply lets you plug in Cloudflare is baseline. A host with integrated CDN that handles cache invalidation, image optimization, and dynamic content delivery is providing real performance value.

PHP Versions and Their Performance Impact

PHP version is one of the easiest performance levers to pull. PHP 5.6, which reached end of life in 2018, is roughly 3x slower than PHP 8.3 for typical WordPress workloads. Benchmarks from Kinsta show that upgrading from PHP 7.4 to 8.3 yields a 15-25% improvement in requests per second and a 10-20% reduction in memory usage.

WordPress has optimized its core code for PHP 8.x, so the gap widens with each release. Look for hosts that default to PHP 8.2 or 8.3 with one-click version switching. Avoid any host that still defaults to PHP 7.4 or requires a support ticket to upgrade.

Database Optimization and Server-Level Tuning

Database query performance is a major contributor to TTFB. A single slow query on the home page can add 500 ms. Critical tuning parameters include innodb_buffer_pool_size, which controls memory allocated to caching table data and indexes. Set too low, MySQL reads from disk constantly. The best hosts use MariaDB over MySQL for its thread pooling, faster joins, and better query optimizer.

Server-level tuning extends beyond the database. PHP-FPM process limits, kernel parameters, file descriptor limits, and I/O scheduler configuration all affect performance. A tuned server handles 5-10x more traffic than an out-of-the-box installation.

Storage is equally critical. NVMe SSDs are 5-10x faster than SATA SSDs for random read/write, which is exactly what databases require. Always verify that your host uses NVMe storage on all tiers, not just premium plans.

Real-World Speed Benchmarks

Independent benchmarks from Review Signal and community performance tests reveal a clear hierarchy. Providers using LiteSpeed with LSAPI, NVMe storage, Redis, and PHP 8.3 consistently deliver TTFB under 150 ms and sub-second fully loaded times for optimized WordPress sites. Top performers like Cloudways DigitalOcean Premium, Kinsta, and SiteGround GrowBig achieved median TTFB of 89 ms, 112 ms, and 134 ms respectively in global tests.

Nginx-based hosts with FastCGI caching and Redis perform nearly as well, with median TTFB ranging from 120 ms to 200 ms. Providers like WP Engine, Flywheel, and Nexcess fall in this bracket, occasionally trailing LiteSpeed hosts on dynamic PHP-heavy pages where LSAPI's advantage over PHP-FPM becomes apparent.

Traditional Apache-based shared hosts represent the bottom tier. Without full-page caching and with overloaded servers, these hosts produce median TTFB of 600 ms to over 2 seconds. During traffic spikes TTFB can surpass 5 seconds, causing significant revenue loss.

Hosting architecture directly dictates the performance ceiling of your website. Choosing LiteSpeed or Nginx with proper caching, modern PHP, NVMe storage, and CDN integration is not a luxury — it is a business decision affecting conversion rates, search rankings, and user experience.