Test your website performance
Enter a website URL to measure its server response time.
Please wait while the server connects to the website.
Website speed results
Performance breakdown
What is a website speed test?
A website speed test measures how quickly a website responds to a request. It can help identify slow server responses, DNS delays, connection problems and other technical performance issues.
Measure server response time
Check how long it takes a server to begin responding to an HTTP request. A slow response can contribute to a slow-loading website.
Inspect connection performance
Review DNS lookup, TCP connection and TLS negotiation timings to understand where connection delays may occur.
Identify performance problems
Use response time and transfer information as a starting point when investigating website performance issues.
Understanding website speed metrics
Different parts of an HTTP request contribute to the overall response time. Understanding these metrics helps you identify possible bottlenecks.
DNS lookup time
DNS lookup is the time required to translate a domain name into an IP address. Slow DNS resolution can delay the beginning of a connection.
TCP connection time
This measures the time required to establish a network connection between the testing server and the target website.
TLS handshake time
HTTPS websites establish an encrypted connection. TLS negotiation contributes to the time before the HTTP response begins.
Time to first byte (TTFB)
TTFB measures the time from the beginning of the request until the first response byte is received. It includes network and server processing delays.
How to improve website speed
If your website has slow response times or poor loading performance, these techniques can help.
Optimize server performance
Review hosting resources, PHP execution, database queries, server configuration and application bottlenecks.
Use caching
Browser caching, page caching and server-side caching can reduce repeated processing and improve response times.
Optimize images and scripts
Compress images, reduce unnecessary JavaScript and CSS, and avoid loading resources that visitors do not immediately need.
Use a content delivery network
A CDN can serve static resources from locations closer to visitors and reduce delivery latency.
Optimize database queries
Improve slow queries, add appropriate indexes and avoid unnecessary database operations.
Monitor real user experience
Compare laboratory tests with real-user measurements to understand how visitors experience your website.
Website speed and Core Web Vitals
Server response time is only one part of website performance. Google Core Web Vitals measure loading experience, responsiveness and visual stability using different metrics.
| Metric | What it measures | Good target |
|---|---|---|
| LCP | Largest Contentful Paint: loading performance. | 2.5 seconds or less |
| INP | Interaction to Next Paint: responsiveness. | 200 ms or less |
| CLS | Cumulative Layout Shift: visual stability. | 0.1 or less |
These are Core Web Vitals targets, not measurements produced by this server-side speed test. For real-user data, use Google Search Console or a browser-based performance testing tool.
Frequently asked questions
How does the website speed test work?
The tool sends an HTTP request from the Grauhirn server to your submitted website and measures connection and response timings using PHP cURL.
What is a good website response time?
Faster responses are generally preferable. As a practical diagnostic guide, this tool labels TTFB up to 800 milliseconds as good, up to 1.8 seconds as needing improvement, and longer responses as slow. These are tool-specific guidelines, not Google's official ranking thresholds.
What is TTFB?
Time to first byte is the time between starting an HTTP request and receiving the first byte of the response. It includes network and server processing time.
Does this tool measure mobile page speed?
No. This version measures a server-side request. It does not emulate a mobile phone, mobile network or browser rendering environment.
Does this tool measure Google Core Web Vitals?
No. It measures HTTP and connection timings. LCP, INP and CLS require browser-based or real-user performance measurements.
Why can my results change between tests?
Network conditions, server load, caching, geographic distance, CDN routing and temporary server activity can all affect response times. Run several tests and compare results rather than relying on one measurement.
Does the test download the entire website?
No. The tool limits the response body to approximately 1 MB and does not load all images, scripts, stylesheets or other browser resources. It is designed to measure the HTTP response, not reproduce a complete browser visit.
Related website tools
Explore other tools to inspect website availability, HTTP responses and technical configuration.