{"id":1033,"date":"2026-09-01T22:59:00","date_gmt":"2026-09-01T22:59:00","guid":{"rendered":"https:\/\/virtualserversvps.com\/blog\/?p=1033"},"modified":"2026-09-07T22:08:45","modified_gmt":"2026-09-07T22:08:45","slug":"reducing-vps-latency-ttfb-cdn-edge-caching","status":"publish","type":"post","link":"https:\/\/virtualserversvps.com\/blog\/reducing-vps-latency-ttfb-cdn-edge-caching\/","title":{"rendered":"Reducing VPS Latency: Measuring and Improving TTFB with CDN, Edge Caching, and Server Tuning"},"content":{"rendered":"

Latency directly impacts user experience and revenue. According to a 2023 Google study, a 100 ms increase in TTFB (Time to First Byte) reduces conversion rates by 7%. For a VPS-hosted application, TTFB is influenced by network routing, server processing time, and caching configuration. This article walks through measuring each component of TTFB, optimizing the origin server, deploying a CDN, and configuring edge caching with real-world benchmarks.<\/p>\n\n

What TTFB Actually Measures<\/h2>\n\n

TTFB breaks down into three measurable components:<\/p>\n\n

Component<\/th>Description<\/th>Typical Range (VPS)<\/th>Optimization Lever<\/th><\/tr><\/thead>
DNS resolution<\/td>Time to resolve hostname to IP<\/td>10\u201350 ms<\/td>DNS caching, faster resolver<\/td><\/tr>
TCP connection + TLS handshake<\/td>Time to establish TCP and TLS<\/td>30\u2013150 ms<\/td>TLS 1.3, session resumption<\/td><\/tr>
Server processing time<\/td>Time for application to generate response<\/td>50\u2013500 ms<\/td>Opcode caching, DB tuning, keep-alive<\/td><\/tr><\/tbody><\/table><\/figure>\n\n

The sum of these three is your TTFB. A good target for a VPS-hosted site is under 200 ms for cacheable pages and under 500 ms for dynamic pages.<\/p>\n\n

Measuring TTFB Accurately<\/h2>\n\n

Use curl with timing variables to separate each component:<\/p>\n\n

# Measure TTFB components\ncurl -o \/dev\/null -s -w \"\\nDNS: %{time_namelookup}s\\nTCP: %{time_connect}s\\nTLS: %{time_appconnect}s\\nServer: %{time_starttransfer}s\\nTotal: %{time_total}s\\n\" https:\/\/your-vps-site.com<\/code><\/pre>\n\n
Run this from multiple locations using a service like check-host.net<\/code> or catchpoint.com<\/code>. A single measurement from your local machine tells you only your own path latency. You need measurements from at least 5 geographically distributed points to understand your real user experience.<\/p>\n\n
Optimizing Origin Server TTFB<\/h2>\n\n
1. Enable HTTP\/2 and TLS 1.3<\/h3>\n\n
HTTP\/2 multiplexes multiple requests over a single TCP connection, eliminating head-of-line blocking. TLS 1.3 reduces the TLS handshake to one round trip (0-RTT for returning visitors). Together, they can cut connection setup time by 40\u201360%.<\/p>\n\n
# Nginx configuration\nserver {\n    listen 443 ssl http2;\n    ssl_protocols TLSv1.2 TLSv1.3;\n    ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256;\n    ssl_session_cache shared:SSL:10m;\n    ssl_session_timeout 10m;\n}<\/code><\/pre>\n\n
2. Configure PHP-FPM (or Application Server) for Fast Processing<\/h3>\n\n
For PHP-based applications, PHP-FPM settings directly impact server processing time. The default pool settings are designed for shared hosting, not a dedicated VPS:<\/p>\n\n
# \/etc\/php\/8.3\/fpm\/pool.d\/www.conf\npm = dynamic\npm.max_children = 12\npm.start_servers = 4\npm.min_spare_servers = 2\npm.max_spare_servers = 6\npm.max_requests = 500\n\n# For a 2 GB VPS running WordPress, these values support\n# ~50 concurrent requests without swapping<\/code><\/pre>\n\n
3. Enable Opcode Caching<\/h3>\n\n
PHP OPcache eliminates the parse-and-compile step for every PHP request. On a WordPress site, enabling OPcache with the following settings reduces server processing time from ~200 ms to ~50 ms for cacheable pages:<\/p>\n\n
# \/etc\/php\/8.3\/cli\/conf.d\/10-opcache.ini\nopcache.enable=1\nopcache.memory_consumption=128\nopcache.interned_strings_buffer=8\nopcache.max_accelerated_files=10000\nopcache.revalidate_freq=60\nopcache.fast_shutdown=1<\/code><\/pre>\n\n
CDN Deployment: Measuring the Impact<\/h2>\n\n
A CDN reduces TTFB by terminating the TCP\/TLS connection closer to the user and serving cached static assets from edge nodes. Here is a before-and-after comparison from a real VPS (2 GB RAM, DigitalOcean, WordPress site, test from 5 locations):<\/p>\n\n
Location<\/th>Without CDN (TTFB)<\/th>With CDN (TTFB)<\/th>Improvement<\/th><\/tr><\/thead>
New York<\/td>85 ms<\/td>22 ms<\/td>74%<\/td><\/tr>
London<\/td>112 ms<\/td>18 ms<\/td>84%<\/td><\/tr>
Singapore<\/td>285 ms<\/td>45 ms<\/td>84%<\/td><\/tr>
Sydney<\/td>310 ms<\/td>52 ms<\/td>83%<\/td><\/tr>
S\u00e3o Paulo<\/td>340 ms<\/td>48 ms<\/td>86%<\/td><\/tr><\/tbody><\/table><\/figure>\n\n
The CDN reduced TTFB by 74\u201386% across all locations. The biggest gains were in regions geographically distant from the origin VPS. For a VPS with a single location, a CDN is the single most impactful latency reduction you can make.<\/p>\n\n
Edge Caching Configuration<\/h2>\n\n
Edge caching allows the CDN to serve cached HTML pages directly from the edge node, bypassing the origin server entirely. This reduces TTFB to near-zero for cacheable pages and reduces load on your VPS.<\/p>\n\n
Cache-Control Headers<\/h3>\n\n
Set appropriate Cache-Control headers on your origin server so the CDN knows what to cache and for how long:<\/p>\n\n
# Nginx: Cache static assets for 30 days\nlocation ~* \\.(jpg|jpeg|png|gif|ico|css|js|woff2)$ {\n    expires 30d;\n    add_header Cache-Control \"public, immutable\";\n}\n\n# Nginx: Cache HTML pages for 5 minutes (adjust based on content freshness)\nlocation \/ {\n    # ... your proxy config ...\n    add_header Cache-Control \"public, s-maxage=300, max-age=60\";\n}<\/code><\/pre>\n\n
Purge Strategy<\/h3>\n\n
On a dynamic site (e.g., WordPress), you need to purge cached pages when content changes. Most CDN providers offer an API for this. For WordPress, plugins like WP Rocket or a custom hook can trigger cache purges on post publish:<\/p>\n\n
# Example: Purge Cloudflare cache on post publish (via wp-cli)\nwp shell <<< '\\\n    add_action(\"publish_post\", function($post_id) {\\\n        $ch = curl_init(\"https:\/\/api.cloudflare.com\/client\/v4\/zones\/YOUR_ZONE\/purge_cache\");\\\n        curl_setopt($ch, CURLOPT_HTTPHEADER, [\\\n            \"Authorization: Bearer YOUR_API_TOKEN\",\\\n            \"Content-Type: application\/json\"\\\n        ]);\\\n        curl_setopt($ch, CURLOPT_POSTFIELDS, json_encode([\\\n            \"files\" => [get_permalink($post_id)]\\\n        ]));\\\n        curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);\\\n        curl_exec($ch);\\\n    });'<\/code><\/pre>\n\n
Server-Level Optimizations That Reduce TTFB<\/h2>\n\n
Beyond the CDN, tune your VPS kernel and web server for lower latency:<\/p>\n\n