How to use this check
Enter a public URL to capture a short TTFB-style timing sample and response status.
The backend records elapsed time around a bounded HTTP request and reports approximate first-byte timing.
Choose an amount before the secure payment page opens.
Performance
Single timing sampleTTFB Checker
Measure bounded first-byte timing for a public URL from one probe runtime.
Pulse score--Single timing sample
Signal checklist
The result shows first-byte timing, total duration and interpretation warnings.
TTFB Check
Enter a public URL to capture a short TTFB-style timing sample and response status.
Result
The result shows first-byte timing, total duration and interpretation warnings.
Support
Keep this free result available
Use the result first. Support and promotional areas stay separate from the useful result.
- Useful result first
- No signup required
- Promotions kept separate
Choose an amount before the secure payment page opens.
Guide and interpretation
How to interpret the result
One high TTFB can be network, CDN, origin or cold-cache behavior; recurring samples are needed for confidence.
Example
A 180 ms first-byte sample for an edge-cached page is usually healthier than a 1800 ms uncached origin path.
Common issues and next steps
Dynamic pages can be fast for logged-in admins and slow for anonymous users behind different cache rules.
Compare cache headers, CDN hit status and origin logs before changing code.
Methodology and limits
This is not Lighthouse, CrUX or a multi-region benchmark.
FAQ
Why is this different from my browser?
Network path, cache state and region differ. Treat it as a single diagnostic sample.
Is history saved?
No. History and alerts are paid task features.