Product tour · Epsilon Delta Gemini · Website monitoring

TTFB and server response time monitoring

Server details splits the time before the first byte into DNS, connection, SSL and backend time, so you can tell whether a slow start comes from your server or the network.

Server details connection phases before the first byte

“Is the delay in DNS, connection, SSL or the backend?”

  • Sample data
  • Last 24 hrs
  • All platforms
  • Median
  • shop.example.com
DNS
0.05 sec
▼ 3% vs last week
Connect
0.12 sec
▼ 27% vs last week
SSL
0.08 sec
▼ 36% vs last week
Response
0.60 sec
▲ 4% vs last week
Total
0.85 sec
all phases combined

Connection phases

median · seconds Combined · Response · SSL · Connect · DNS
  • Redirect
  • DNS
  • Connect
  • SSL
  • Server response
00:0004:0008:0012:0016:0020:00

Top pages · server response

bar = share of traffic
  • shop.example.com · /product/:id0.58 s
    60% · p90 1.01 s · 986K views
  • shop.example.com · Home0.86 s
    22% · p90 1.36 s · 362K views
  • shop.example.com · /search0.57 s
    12% · p90 1.10 s · 197K views
  • shop.example.com · /payments0.16 s
    2.3% · p90 0.29 s · 38K views

Sample data on example domains (shop.example.com). Your dashboard shows your own sites and apps.

What you can see on Server details

  • DNS, TCP, SSL and server phases
  • TTFB trend by page and platform
  • Redirect time
  • Comparison across domains

Questions about Server details

What is a good TTFB?

0.8 seconds or less is considered good.

Is a slow TTFB always the backend?

No. DNS, connection setup and SSL can add hundreds of milliseconds before the server starts any work.

Last updated 6 Nov 2026 · Reviewed by [Name], [Role]