Mike's Notes
I discovered TTFB via an item in Smashing Newsletter.
"Because TTFB precedes user-centric metrics such as First Contentful Paint (FCP) and Largest Contentful Paint (LCP), it's recommended that your server responds to navigation requests quickly enough so that the 75th percentile of users experience an FCP within the "good" threshold. As a rough guide, most sites should strive to have a TTFB of 0.8 seconds or less."
- WebDev
Resources
- https://www.debugbear.com/test/ttfb
- https://en.wikipedia.org/wiki/Time_to_first_byte
- https://developer.mozilla.org/en-US/docs/Glossary/Time_to_first_byte
- https://web.dev/articles/ttfb
- https://web.dev/articles/optimize-ttfb
References
- Reference
Repository
- Home > Ajabbi Research > Library > Subscriptions > Smashing Newsletter
- Home > Handbook >
Last Updated
09/12/2025
Time to First Byte (TTFB)
By: Mike Peters
On a Sandy Beach: 09/12/2025
Mike is the inventor and architect of Pipi and the founder of Ajabbi.
Here are the results of a recent test. The ajabbi.com website is hosted in a data centre in Singapore.
TTFB test by debugbear.com of https://www.ajabbi.com 3/12/2025
| Test Location | TTFB |
|---|---|
| Atlanta, United States | 1211 ms |
| San Francisco, United States | 1167 ms |
| São Paulo, Brazil | 1893 ms |
| Sydney, Australia | 574 ms |
| Tokyo, Japan | 632 ms |
| Singapore, Singapore | 315 ms |
| Bangalore, India | 986 ms |
| Dubai, United Arab Emirates | 1692 ms |
| Brussels, Belgium | 1369 ms |
| Helsinki, Finland | 1222 ms |
