Server Response Time (TTFB)
Checks Time To First Byte — how fast your server responds.
What this check measures
We measure time from request to first response byte. TTFB over 600ms is flagged — usually server-side rendering or DB queries are the bottleneck.
Why it matters
TTFB directly affects LCP and overall perceived speed. Google's Core Web Vitals don't measure TTFB directly, but slow TTFB makes LCP targets impossible to hit.
How our audit detects it
Measure elapsed time from request start to first byte. Take multiple samples, report the median.
Typical findings
- error_outlineTTFB > 1s — unoptimized SSR with heavy DB queries.
- error_outlineTTFB > 500ms from a CDN — geographic distance to origin.
- error_outlineCold start on serverless function adds 2-3s to first request.
How to fix
Cache SSR output where possible. Use a CDN closer to users. Reduce DB query count per request. Upgrade from shared hosting to serverless/container if applicable.
Frequently asked questions
What is a good TTFB?expand_more
Want this checked on your site?
Pantra runs the full audit (SEO, Security, GEO, Performance, Schema, Technical, Images) in 10 seconds and generates stack-specific fix prompts.
Scan my siteRelated checks
SSR / Pre-rendering
Checks if the page is server-rendered or statically pre-rendered.
TechnicalHTTP Status Codes
Checks that pages return proper status codes — 200 for live, 404 for missing, 301 for moved.
TechnicalNo Client-Side Redirects
Checks that redirects happen server-side, not via JavaScript.
TechnicalViewport Meta Tag
Checks for <meta name="viewport" content="width=device-width, initial-scale=1">.