Test Your Website Speed and See Exactly What Is Weighing It Down

TTFB (Time To First Byte) is the time from the request being sent to the first byte arriving from the server. It reflects the speed of your hosting and the software behind the site - not its images or design. Under 0.5 seconds is good. If TTFB is already slow, no amount of image or code optimisation will help much, because the visitor is already waiting before anything has been sent.

Not exactly, and we would rather be straight about it - the two measure different things. PageSpeed Insights runs a real browser to judge the visual experience, such as LCP and CLS. This tool measures from the network side: server response time, page weight, request count, compression and caching. They complement each other, and almost every fix suggested here will also lift your PageSpeed Insights score.

From our server in Indonesia. If your audience is in Europe or North America, treat the response time as indicative rather than exact, since network distance affects it - the same site will test faster from closer by. Page weight, compression, caching, protocol and render-blocking assets are location-independent, so those findings apply wherever your visitors are.

As a rule of thumb, under 1.5 MB is light and over 3 MB is heavy - particularly for visitors on mobile data. Images are almost always the largest contributor, so converting them to WebP usually gives the most noticeable result for the least effort.

Because we actually download each asset to find its real size, rather than guessing from headers. Many servers do not report file size correctly when the response is compressed, so this approach is far more accurate. Assets are capped at 30 files per check to keep it fast and avoid loading the site being tested - if the page has more, the figure is marked with a plus sign.

In order of effort against result: (1) enable gzip or Brotli compression, usually one switch in the hosting panel; (2) set browser caching for images, CSS and JS; (3) convert images to WebP; (4) add defer to JavaScript and loading="lazy" to below-the-fold images. If TTFB is the red one, those first three will not be enough - the hosting is what needs sorting.

Yes, as long as the page is publicly accessible. Comparing response time and page weight against a competitor often gives a quick sense of where you stand - and sometimes shows the problem is not at your end.

Free and no sign-up. Each visitor gets 10 checks per day. Results are only cached on the server for about 15 minutes so the same address is not measured repeatedly.