DNSResolve
Free tool, no account required
Free Global Website Response Test
Compare HTTP response timing from available probe locations and inspect DNS, connection, TLS and first-byte timing where the selected probe provides them.
Also known as: TTFB, page speed waterfall, DNS/TLS timing
Evidence shown with sourceNo account requiredNo invented metrics
One URL, five measured phases
See the connection before the page can render
The Germany probe follows HTTP redirects, measures every request, then visualizes the final document response without inventing browser or Core Web Vitals data.
TCPConnect
TLSSecure
First byteRespond
HTMLTransfer
Public targets only, live request from Germany, no estimated timing
Evidence model
Know what the result proves
This check reports the request timings supplied by the selected live probe. Novaverb's own probe separates available DNS, connection, TLS, request-wait and document-transfer phases; community probes may provide only the phases they measure. None of these results includes browser rendering or subresource loading.
1. Source
Novaverb's Germany probe or selected community probes. The result identifies where its evidence came from.
2. Boundary
Each number comes from the selected probe. Novaverb's Germany mode follows redirects and captures up to about 3 MB; community-probe mode measures the exact submitted URL. Neither mode measures rendering, Core Web Vitals or real users.
3. Next action
Use the finding to verify a problem, then connect a workspace when you need history, monitoring, or site-wide analysis.
What does the Website Performance Test measure?
It measures DNS, TCP, TLS, request-to-first-byte and document transfer for a public URL. Choose Novaverb's Germany direct probe, one Globalping community location, or compare ten cities across Asia, Europe, the Americas, Africa and Oceania.
Measurement methods, locations and free limits
Choose the Novaverb direct probe for a controlled measurement, one Globalping city for a regional check, or all ten cities for a five-region comparison. The two methods stay separate because they have different redirect, capture and retention boundaries.
🇩🇪 Germany location
- Runs on Novaverb infrastructure over a fresh HTTP/1.1 connection.
- Follows up to five HTTP redirects and shows the final response waterfall.
- Captures the response body up to about 3 MB and keeps declared length separate.
- Does not consume third-party probe tests.
🌍 One city or all 10
- A currently online probe in the selected city requests the exact submitted URL.
- Returns DNS, TCP, TLS, first-byte, download and total timing with city and timing evidence.
- Does not follow Novaverb's redirect loop; test a returned 3xx destination separately.
- Probe identity metadata is intentionally hidden from the public result.
- The target and measurement are processed by Globalping and may remain retrievable for up to seven days.
How free use is limited: each selected city runs one live request. Comparing every location runs several requests, so temporary capacity limits may apply. If a probe is unavailable, Novaverb leaves that location unmeasured instead of estimating a result.
How the performance waterfall works
DNS lookup
Resolve the hostname, while the connection remains pinned to the validated public IP.
TCP connect
Open a fresh connection; no previous socket is reused.
TLS handshake
Negotiate HTTPS with SNI and HTTP/1.1 when the URL is secure.
First byte
Measure from sending GET until the first response bytes arrive.
HTML transfer
Measure from first byte through the captured document body, up to about 3 MB.
How to read the TTFB guide bands
web.dev gives 800 ms or less as a rough good TTFB target and above 1,800 ms as poor. Novaverb applies those guide bands to the final response's connection-to-first-byte sample, not to the complete redirect journey.
Repeat from user-relevant regions before concluding the URL is consistently fast.
Use the waterfall to identify whether setup or request wait dominates.
Retest, compare cache states and investigate the largest repeated phase.
What this result includes - and what it does not
Measured in this run
- Fresh DNS, TCP and TLS setup for every request
- Request-to-first-byte and captured body transfer
- HTTP redirects, status and final response headers
- Body bytes received and declared Content-Length kept separate
- One measuring region: EU, Germany
Not measured or proven
- CSS, JavaScript, images, fonts or third-party resources
- Browser parsing, rendering, visual completion or interaction readiness
- LCP, INP, CLS, FCP or a Lighthouse performance score
- Real-user percentiles, uptime or sustained-load behavior
- Pure origin execution time separated from CDN and network latency
How to improve the dominant phase
High DNS time
Review authoritative DNS latency and reliability; compare multiple runs because resolver cache state varies.
High TCP time
Reduce distance with an edge or CDN and investigate route quality or packet loss.
High TLS time
Check certificate chain, modern TLS support and connection reuse in actual browsers.
High first-byte wait
Inspect CDN cache misses, database work, external calls and application or origin contention.
High HTML transfer
Reduce document size and verify appropriate content encoding, while remembering this test captures only the document.
Standards and measurement guidance
W3C, Navigation TimingDefines navigation phases including requestStart, responseStart and responseEnd.
W3C, Resource TimingDefines response timing and distinguishes transferred and encoded body sizes.
web.dev, Optimize TTFBExplains the rough 800 ms and 1,800 ms guide bands.
RFC 9110, HTTP SemanticsDefines the HTTP methods, status and response semantics used by the probe.
Globalping, API specificationDefines community probe selection, HTTP timing fields, polling, free limits and result retention.
Website performance test questions
Is this a complete page-speed test?
No. It measures connection and document-response timing only. A complete browser test must also load dependencies, execute scripts and render the page.
Why is this different from Chrome or Lighthouse?
The probe runs from a server in Germany over a fresh HTTP/1.1 connection. Your browser can use another route, protocol, cache and reused connection, then perform rendering work this test never attempts.
Does it follow redirects?
Yes, up to five HTTP redirects. Each hop is independently measured with a fresh request; the main waterfall is the final response.
Does total time mean page load time?
No. It is the sum of connection phases and captured document transfer for one request. It excludes subresources, code execution, rendering and interaction readiness.
Why can downloaded bytes differ from Content-Length?
Content-Length is a server-declared header. Body received is what this bounded probe actually captured; large responses may stop near the 3 MB safety limit.
Why do results change between runs?
DNS and CDN cache state, origin load, network routing and shared infrastructure vary. Diagnose patterns across repeated samples and real-user data, not one run.
Each number is a single synthetic request from the selected probe; it does not measure browser rendering, Core Web Vitals or real users.
Get the right answer
What to submit - and what to avoid
Submit the exact public address you want measured, including its path and query when relevant. Redirect behavior depends on the selected mode and is stated with the result. A private host is refused. Every location is one synthetic sample, so compare repeated runs before treating a difference as persistent.
Use it like this
yourdomain.comAny address form works. http or https, with or without www, a bare domain or a full path - we normalize it for you.A URL that redirectsFine - we trace every hop first, then measure the final destination.Avoid this
Expecting full page-load / render timeThis times the server and connection phases (TTFB), not browser rendering of the whole page.Expecting your users' field numbersIt is one synthetic request from a fixed location - use Core Web Vitals for real-user field data.Public methodology
Exactly how this result is produced
The address is normalised and the redirect chain is followed per HTTP semantics to the final URL. DNS, TCP, TLS, time to first byte and content transfer are then timed as standard navigation-timing phases, and the TTFB is banded against public field guidance so the stage responsible for the delay is visible rather than averaged away.
- We submit the exact public URL to the selected live probe and retain that probe's location with the result.
- We show only the timing phases returned by that probe; Novaverb's own probe provides the most detailed split.
- We label each location as one synthetic sample and exclude browser rendering, subresources and real-user field data.
Built on public standards
The international standards this check applies
Three public references define this measurement. W3C Navigation Timing defines the phase model the timings follow, RFC 9110 defines the HTTP semantics used to walk the redirect chain, and Google's web.dev TTFB guidance supplies the band. The phases are reported individually because a single total hides which stage a fix belongs in.
W3CNavigation Timing
Navigation & Resource Timing
Labels available request phases using the common DNS, connection, TLS, wait and transfer model.
Read the specificationIETFRFC 9110
HTTP Semantics
Follows the redirect chain per HTTP semantics before the final measurement.
Read the specificationGoogleweb.dev TTFB
Time to First Byte guidance
Bands the measured TTFB against public field guidance.
Read the specificationWe list a standard only where this tool genuinely reads or measures against it. Where a signal is outside a live check, the result says so instead of implying coverage.
Common questions
Website Performance Test FAQ
What does the Novaverb Website Performance Test measure?
It measures the full connection waterfall for a URL, DNS lookup, TCP connect, TLS handshake, Time To First Byte, and HTML transfer, from Novaverb's Germany probe or selected community probes placed across world regions.
How is this different from the single-location speed check?
The speed check runs only from Germany. This performance test can additionally run from community probes in multiple world regions, letting you compare connection timing across geographies rather than from one fixed vantage point.
Does this test measure Core Web Vitals or rendering?
No. Each number reflects network and server connection timing only. It does not run a browser, so it cannot measure Largest Contentful Paint, layout shift, interactivity, JavaScript execution, or anything about how the page visually renders.
What is the connection waterfall in this test?
It is the ordered breakdown of a request: DNS resolves the hostname, TCP establishes the connection, TLS negotiates encryption, TTFB captures server wait, and HTML transfer downloads the initial document. Each stage exposes where time is spent.
Why are timings different from each probe location?
Each probe is a separate physical location, so distance to your server and CDN edge changes DNS, connection, and transfer times. Regions far from your hosting or without nearby edge nodes will consistently show higher latency.
What is a good TTFB across regions?
Aim for under roughly 500 milliseconds in your primary markets and reasonably consistent numbers elsewhere. Large gaps between regions usually indicate missing CDN coverage or origin-only serving for distant users, which a content delivery network can flatten.
How do I improve performance for distant regions?
Put a CDN in front of your origin so static assets and cached HTML serve from edge nodes near users. Also enable modern protocols and caching so far-away regions are not paying full origin round-trips.
Is one probe measurement reliable on its own?
Treat each number as a single sample from one probe at one moment, subject to transient network conditions. Run repeated checks and compare trends across regions rather than drawing conclusions from any isolated measurement.
Does this test represent what real users experience?
Not exactly. Probes approximate network paths but are not your actual visitors on their devices, browsers, and connections. Use this for comparing server and network delivery across regions, and pair it with field data for true real-user performance.
Why compare response time across regions?
Distance and routing can change connection and first-byte time. Regional probes help locate delivery gaps, but they do not measure browser rendering, real users or search-engine behavior.
More free checks
Explore all Novaverb Free Tools
Website SEO CheckerCrawl coverage, indexable pages, and internal links
Keyword Research ToolCheck the exact query's available search volume, keyword difficulty and …
SERP CheckerInspect the returned organic results for a keyword and country, …
Website Security CheckerAudit website security posture, TLS/SSL certificates, HTTP security headers, and …
WordPress Security Configuration CheckerCheck eight externally observable WordPress configuration areas: XML-RPC, wp-login.php, debug …
Server Response Time CheckerMeasure server Time to First Byte (TTFB), DNS lookup, TCP …
Backlink CheckerExplore backlinks, referring domains, dofollow links, and domain authority for …
Robots.txt CheckerTest and validate robots.txt rules, User-Agent directives, blocked paths and …
Sitemap CheckerDiscover sitemap declarations, inspect the root document and fetch a …
Meta Tag CheckerCheck page title length, meta description, H1 heading structure, Open …
HTTP Status & Redirect CheckerTrace HTTP status codes (200, 301, 302, 404, 500) and …
Website MonitorRun one live availability check and retain an evidence sample …
HTTP/2 TestCheck whether the exact submitted hostname negotiates HTTP/2 through TLS …
HTTP/3 TestTest whether your web server supports HTTP/3 over QUIC with …
GEO CheckerInspect observable page signals that support retrieval, answer extraction, attribution …
Core Web Vitals CheckerCheck 75th-percentile real-user LCP, INP and CLS from Chrome field …
PageSpeed CheckerRun one Lighthouse lab audit to inspect performance, accessibility, best-practices …
Website Safety CheckerCheck whether a domain or URL is flagged for malware, …
Knowledge Graph CheckerLook up matching entities for a brand, person, product or …
Keyword Gap CheckerFind ranking keywords observed for a competitor and not observed …
Competitor Top PagesFind the pages with the highest estimated organic traffic in …