Server & TTFB Audit
See when the first response byte arrives.
Measure a public URL from the EduGuestPost hosting server. Follow the connection milestones and cache headers with clear limits—not an invented speed score.
A timing sample with its boundaries attached
The checker first reads robots instructions, then makes one bounded GET sample with manually checked, same-origin redirects. It verifies public destinations, pins a public IPv4 address and retains a limited response body. It does not request page assets, click links, submit forms, log in, bypass robots instructions or execute the target’s JavaScript.
Read milestones and phases differently
Connection, TLS, pre-transfer and first-response-byte milestones all start at the beginning of that hop’s transfer. Derived TCP, TLS and post-setup wait phases are differences between compatible milestones. Post-setup wait includes network, protocol and server effects; it does not isolate backend processing. The pinned-lookup milestone is not an external DNS latency benchmark.
Observed transfer duration may stop at the body cap. Overall collection elapsed time includes robots, safety checks and redirects; it is not TTFB. A cooperative scheduling deadline limits further requests, but blocking hostname resolution may extend wall-clock time. Unknown timings remain unknown, including ambiguous informational-response cases.
Use the context before changing a site
This single sample comes from the EduGuestPost hosting server, whose geographic location is unverified. Different routes, cache state, load and later runs can differ. Cache-related response headers are reported as declarations, not proof of a cache hit or an origin benchmark. Combine the sample with your own repeated controlled measurements and real-user performance evidence.
Private by default in this module
Reports stay in this browser page until reset or navigation. When enabled, JSON preserves the complete returned report and CSV includes its field paths, timing values, scope and unknowns. This module does not create report history.
Frequently asked questions
Is this a browser speed test or a Core Web Vitals score?
No. This is one server-side GET sample from the EduGuestPost hosting server. It does not load assets, execute target JavaScript, measure field performance or assign a speed score.
What does first response byte mean?
The timing starts when the transfer begins and ends when cURL receives its first response byte. It includes connection and protocol setup; it is not isolated backend processing time or necessarily the first final HTML-body byte. Ambiguous informational responses remain unknown.
Is the DNS timing a real DNS lookup benchmark?
No. The request pins a public IP after safety checks. The cURL pinned-lookup milestone is not an uncached external DNS measurement.
Why can a result be partial or unavailable?
Robots instructions, request failures, redirect limits, response caps or unsupported timing evidence can prevent a complete sample. Unknown values are not zero and are not a performance pass.
Do I need a paid API?
No paid API is required. This bounded check uses the hosting server and the existing protected transport. Reports are not saved by this module; JSON and CSV downloads are available when enabled.