1. Source
Live server-side HTTP fetch. The result identifies where its evidence came from.
Measure server-side HTTP fetch time and response status for any public URL. See real timing without fabricated browser TTFB or Core Web Vitals.
Submit a public URL, domain, or keyword. Novaverb will show only the evidence this tool can actually retrieve or measure.
Each free check separates measured evidence from interpretation, and interpretation from the deeper work available in a connected workspace.
Live server-side HTTP fetch. The result identifies where its evidence came from.
The duration includes server-side DNS, connection, TLS, and response-header time. It is not browser TTFB, LCP, CLS, or INP.
Use the finding to verify a problem, then connect a workspace when you need history, monitoring, or site-wide analysis.
Speed is not just a user experience requirement; it is a critical ranking factor in Google's algorithm. Slow-responding web servers consume too much crawl budget, prompting Googlebot to crawl fewer pages. Time to First Byte (TTFB) measures the connection latency and server-side processing time before a single byte of HTML is received by the client.
Excellent response speed. Googlebot and users will experience a snappy connection.
High latency. Indicates slow backend processing, unoptimized code, or database bottlenecks.
Yes. You can run the public check without creating an account. A connected workspace is required only for saved evidence, monitoring, and deeper product workflows.
Live server-side HTTP fetch. The duration includes server-side DNS, connection, TLS, and response-header time. It is not browser TTFB, LCP, CLS, or INP.
No. If the required evidence is unavailable, the tool returns an unavailable or incomplete state instead of inventing a metric.
Connect the target to a Novaverb workspace to keep evidence, run site-wide analysis, monitor changes, and move findings into an accountable workflow.