Learn6 min read
Is 340 ms slow?
It depends on what you measured and where the request started.
A simple guide to deciding whether 340 ms is fast or slow for a website, API, static file, or AI response.
Published August 24, 2026Read article
Learn
These articles help you figure out where, why, and what to do about it.
It depends on what you measured and where the request started.
A simple guide to deciding whether 340 ms is fast or slow for a website, API, static file, or AI response.
Your laptop says the API is fast. Your users on the other side of the world are telling you something else.
A practical guide to checking API latency from several regions, understanding what the numbers mean, and turning that into an infrastructure decision.
You've probably never measured it. It's probably the biggest performance problem you have.
Time to First Byte controls when rendering can begin, which is why it quietly drags down LCP, Core Web Vitals, and search performance.
The answer used to be simple. It isn't anymore.
The Google Fonts answer changed after shared browser caches disappeared. The real decision now is where your server lives.