Site Speed Test

Measure TTFB, DNS, TLS and total response time — get a grade and clear improvement tips.

Example: www.uzmantescil.com.tr

Speed grade

https://www.google.com/

DNS

61 ms

TLS

119 ms

TTFB

130 ms

İndirme

562 ms

TTFB: 310 ms
DNS: 61 ms
TLS: 119 ms
Total time: 872 ms
Page size: 31.8 KB
Compression: Off / unclear
Cache header: Present
HTTP: 200

Improvement tips

Sıkıştırma (gzip/brotli) kapalı görünüyor; HTML/CSS/JS için açın.

All tools Look Up

What the speed test measures

The test splits the time spent fetching the first HTML document. DNS, TCP, TLS, TTFB, download and total sit side by side. The bars do not add up to the total. TTFB already includes DNS and the handshake. Total also includes the download. The chart shows where time accumulates.

The grade runs from A to F using TTFB and total time. Compression and a cache header are flagged separately. This is not a lab score of every image and third-party script. It is one HTML request.

Field	Meaning	Comfortable range
DNS	Resolving the name to an IP	Tens of milliseconds
TCP	Opening the connection	A short step after DNS
TLS	HTTPS handshake	Over 300 ms hints at distance or the certificate
TTFB	Time until the first byte	200–400 ms is healthy, over 800 ms is a slow server
Download	From the first byte until the document ends	Grows with a large HTML file
Total	The whole request	Under 1.5 seconds is comfortable

How to read the chart and the grade

The longest bar is the bottleneck. A long DNS bar points at resolution or TTL. A long TTFB points at PHP, the database or a cold cache. A long download points at bloated HTML. A and B mean the basic response is quick. C and below mean the visitor waits before any content.

Turn on a page cache so dynamic HTML is not built on every hit.
If gzip or Brotli is off, enable it. The compression field says so.
This test does not time images, but images dominate real loads. Use WebP and real dimensions.
A distant location inflates TTFB. If visitors are in Turkey, host nearby.

Speed and SEO

Google knows a slow page sends people back. Speed alone does not set rank, but between two pages that answer the same intent the faster one is abandoned less. Bring TTFB down first, then images and scripts. The SEO analyzer reads title and H1. This page reads time. Use both.

Frequently asked questions

What does the speed test measure?

DNS, TCP, TLS, TTFB, download and total time in milliseconds, drawn as bars. It also checks compression and a cache header.

What is TTFB?

Time To First Byte is how long until the first byte arrives. A high TTFB usually comes from the app, the database or an uncached page.

Do I add the bars together?

No. TTFB includes earlier stages, and total includes the download. The bars are a comparison, not a stack.

Is an A the same as PageSpeed 100?

No. This test times the HTML response. Lighthouse also scores images, scripts and layout shift.

How do I make it faster?

Cache, NVMe storage, gzip or Brotli, and fewer plugins lower TTFB. Strip data embedded in the template if the HTML is huge.

Is the number the same for every visitor?

No. The test runs from this server. City and momentary load change the result.