Is your site really fast? What TTFB reveals in 1 second

Time to First Byte measures how fast your server responds. Under 800 ms is good, above 1.5 s is a red flag — and most site owners never check.

You can optimize images, minify JavaScript, and enable caching — but if the server takes 3 seconds to respond, none of it matters. The visitor stares at a blank screen. Google records the delay. Your PageSpeed score tanks.

That's what TTFB measures: the time between the browser's request and the very first byte of the server's response. It's the starting gun of every page load. If it's slow, everything that follows is delayed too.

Most site owners never check their TTFB. They focus on the visual — page load, images, layout — without realizing the bottleneck is the server itself. Test #16 in Orilyt measures it automatically and turns it into a clear, actionable finding.

What TTFB actually measures

TTFB stands for Time to First Byte. When your browser sends a request to a server, three things happen:

1. DNS lookup: translating the domain name into an IP address
2. TCP/TLS connection: establishing the secure connection to the server
3. Server processing: the server runs PHP, queries the database, builds the HTML, and sends the first byte back

TTFB is the total time for all three steps. The third step — server processing — is usually where the bottleneck sits. A slow database, an overloaded shared host, or unoptimized PHP can add hundreds of milliseconds.

Google considers TTFB as part of its Core Web Vitals assessment. A slow TTFB directly impacts LCP (Largest Contentful Paint), which is a ranking factor.

How Orilyt scores your TTFB

Test #16 measures the TTFB of the page being audited and scores it based on three thresholds:

1. Under 800 ms → Score 100 — Fast. The server responds quickly, no action needed
2. 800 ms to 1.5 s → Score 80 — Acceptable but could be improved. Worth investigating
3. Above 1.5 s → Score 50 — Slow. The server is a bottleneck. Action required

These thresholds align with Google's recommendations. A TTFB above 1.5 seconds almost guarantees a poor LCP score, which impacts search rankings.

The 5 most common causes of slow TTFB

When TTFB is high, the culprit is almost always server-side. Here are the five most frequent causes:

1. Cheap shared hosting — your site shares CPU and RAM with hundreds of others. Peak hours = slow responses
2. No server-side caching — every request triggers a full PHP execution and database queries. Adding page caching (WP Super Cache, WP Rocket, Redis) can cut TTFB by 80%
3. Slow database queries — unoptimized queries, missing indexes, or a bloated wp_options table. Each extra query adds milliseconds
4. Too many plugins — each plugin hooks into WordPress and adds processing time. 30+ active plugins is a common TTFB killer
5. Geographic distance — if your server is in the US and your visitors are in Europe, the physical distance adds latency. A CDN or closer server solves this

The key insight for freelancers: slow TTFB is usually a hosting problem, not a code problem. This makes it easy to diagnose and recommend — "your hosting is the bottleneck, here's what to change."

TTFB as a selling point

For freelancers and agencies, TTFB is one of the most powerful audit findings. It's measurable, objective, and directly tied to business outcomes:

A slow TTFB means slower page loads, which means higher bounce rates, lower conversions, and worse SEO rankings. Studies show that every 100 ms of delay reduces conversion by 1%.

In the Orilyt report, test #16 generates a structured FIA recommendation:

1. Fact: "TTFB measured at 2.3 seconds — classified as slow"
2. Impact: "Every page load is delayed, affecting user experience, SEO, and conversion rates"
3. Action: "Migrate to a faster host or implement server-side caching — estimated improvement: 60-80%"

The test that reveals your server's true speed

TTFB is often the most overlooked performance metric. Site owners focus on images and scripts, missing the fact that their server adds 2 seconds before anything even starts loading.

With Orilyt's test #16, you get an instant, objective measurement. No manual tools, no terminal commands — just a clear score with actionable recommendations.

If you're auditing client sites, TTFB gives you a concrete data point that's easy to explain and leads to a clear solution. It's the kind of finding that starts conversations — and closes deals.