Public URL check
Check website response
Check a website or page response: HTTP status, response time, final URL, redirects, HTML size, HTTPS and basic server headers.
Website response check by URL
Enter a website or page URL and URLCompass shows whether it responds, which HTTP status the server returns and how long the request took.
Page response details
For a specific page, the report shows final URL, redirects, HTML size, HTTPS, Content-Type and server headers.
Response time and availability
A slow or unstable response can affect user experience, crawler access and debugging after migrations, releases or cache changes.
Focused technical check
This page focuses on URL response: status, time, redirects and headers. For SEO, content, security and technologies, use the full website analysis.
Example result
What the report can show before you open it
The exact values depend on the URL, but the report highlights practical signals instead of a raw technical dump.
Response time, HTML size, Content-Type, caching, compression and Server-Timing.
For example: 200 OK, final URL after redirects, response time and HTML size.
HSTS, CSP, X-Frame-Options, X-Content-Type-Options and Referrer-Policy.
The report groups output into critical issues, recommended fixes and useful context.
Report sections
The scan keeps the result readable
Response time
Server-side response time during a fast public URL check.
Status code
HTTP status for the website or page: success, redirect or error.
Redirects
Requested URL, final URL and basic redirect signals.
Server headers
Content-Type, cache, server, security headers and other public HTTP signals.
FAQ
Common questions
Is response time the same as full page load time?
No. This is a server-side HTML response check. It helps diagnose the response but does not replace browser Core Web Vitals.
Does URLCompass need access to the website admin area?
No. The report is built from public signals available by URL: HTML, headers, DNS, TLS, robots.txt and sitemap.xml.
Can it show exact traffic or private analytics?
No. Exact traffic requires analytics access or paid data sources. URLCompass intentionally separates public checks from private metrics.
What should I do after the report?
Start with failed checks and warnings: indexability, HTTPS/TLS, security headers, page speed, missing metadata and weak DNS/mail protection.
Which URLs can be checked?
Use public http or https pages. Localhost, private IP addresses and closed admin pages are blocked to keep the checker safe.