A performance report based on what can genuinely be measured about a website from a browser: HTTP status, redirects, response headers, DNS records, network timing and a clearly explained diagnostic score. Measurements that are not possible (like Cross-Origin Core Web Vitals) are reported as “Not available in this test” instead of being invented.
Test a website URL
The test makes three server-side requests through the microLink API, one DNS query via Google Public DNS, and attempts a direct browser load of the page (only possible when the target allows cross-origin access). Allow 20–60 seconds; heavy comparisons may take longer.
Limitations & transparency
CORS rules prevent this page from loading another website inside its own session, and it cannot render pages like Chrome's lab tools do. Those restrictions are respected, never bypassed. Round-trip times always include more than just the target site (your connection + the API provider), and each measurement row carries its source label so you always know who measured it.
The tested URL is sent to microLink and dns.google. This site stores nothing. See the Privacy Policy.
FAQ
Why is TTFB missing for my site?
TTFB is read from the Resource Timing API, which only reports it when the target server allows cross-origin timing (Timing-Allow-Origin header). Most servers do not send it, so the browser deliberately can't see it. The report says so instead of estimating.
Is the Website Diagnostic Score a Google score?
No — and it says so on the report. It is a simplified 0–100 score computed only from the checks this page performed (HTTPS, status, redirects, round-trip time, DNS, content type). Every factor, maximum weight and measured value is shown in a table.
Why did my WordPress site score lower after I slowed the test with 3 requests?
The score uses the average of three round trips so a single slow response doesn't skew it. A bad average usually reflects server load or a slow host — which is exactly what the round-trip factor is meant to surface.
How fast should my site be?
As a rough practical guide: under ~2 seconds to first meaningful content feels fast to most visitors. This page cannot measure that directly, but the checks it performs (status, redirects, TTFB when allowed, DNS health) cover the common speed killers.