Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

Web hosting

Website TTFB troubleshooting: find what delays the first byte

Published August 2026 · 2 min read · Updated 2026-09-05

Time to first byte (TTFB) includes connection/TLS and the time the server takes before sending the first response byte. A high TTFB can come from network distance, proxy queueing, application/PHP work, database queries, external APIs, cache misses, or overloaded infrastructure.

Break timing into network and server components

Use curl/browser timing to record DNS, connect, TLS, start-transfer, and total time from more than one client region. Subtracting connection setup from TTFB helps distinguish path latency from origin processing.

Test both cache-hit and cache-bypass URLs when a CDN/page cache exists.

Measure origin application duration

Add server/request logs containing upstream response time or application timing. Profile PHP/runtime, database queries, template rendering, external HTTP calls, filesystem operations, and worker queue time.

A slow remote API can dominate TTFB even while local CPU is idle.

Check queueing and resource pressure

Inspect PHP/app worker saturation, CPU, memory pressure, disk latency, database connections, and load. More workers can reduce queueing only if the rest of the stack has capacity.

Compare slow periods with a normal baseline.

Optimize the longest segment first

Fix expensive application/database work, cache safe responses, move background tasks, or resize the constrained resource based on evidence. Re-run the same timing test after each change. Keep client region and cache state constant between samples so the comparison reflects the server change with the network path held constant.

  • Separate DNS/connect/TLS/server time.
  • Measure origin upstream time.
  • Check worker/database queues.
  • Retest the same URL after changes.

Next step

Break time to first byte into DNS, connection, TLS, proxy, application and database work so slow TTFB is fixed at the layer that actually owns it.

Explore DotMoose web hosting

Keep reading

Related guides.

HTTP 500, 502 and 503 errors explained for website owners

Learn what HTTP 500, 502 and 503 errors usually indicate, which layer to investigate, what evidence to collect, and when restarting a service is not the real fix.

Read the guide

Virtualmin vs cPanel: Which Control Panel Should You Choose?

Virtualmin vs cPanel compared on licensing cost, account and site management, email, DNS, backups and migration, so you can pick the control panel that fits how you host.

Read the guide

How to move web hosting without downtime

Move a website and database with destination testing, final synchronization, controlled DNS cutover, and rollback while preserving separate mail routing.

Read the guide

More web hosting guides

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move