Review response timing, document structure and essential technical SEO signals from one server-side HTML fetch.
A website audit helps you see whether a public page responds correctly, loads its initial HTML within a reasonable time and includes the basic technical signals search engines and browsers expect. It is a useful first check after publishing a new page, migrating hosting or troubleshooting slow landing pages.
This tool fetches the HTML document from the server and analyses response timing, heading structure, metadata, canonical tags, viewport settings and image alternative text. It does not execute JavaScript or measure full browser rendering, so it complements — but does not replace — lab tools such as PageSpeed Insights.
If response timing looks poor, confirm DNS and routing with the DNS lookup tool and network diagnostics. For metadata drafting, use the SEO metadata generator after fixing structural issues here.
Start with the business symptom, then inspect only the signals that explain that part of the page.
Understand the scope
HTTP status, validated DNS resolution, connection timing, TLS handshake, TTFB and downloaded HTML size.
Headings, links, images, scripts, stylesheets and alternative-text coverage in the returned HTML.
Title, description, canonical, robots, viewport, language, Open Graph and structured-data presence.
This tool does not execute JavaScript or render the page. Use Google PageSpeed Insights for lab-based LCP, INP and CLS analysis.
No. This server-side audit measures the initial HTML response and document structure. It does not execute the full page or calculate browser Core Web Vitals.
Time to First Byte measures how long the audit server waits before receiving the first response byte. Hosting, application processing, caching and geographic distance can affect it.
The tool measures the fetched HTML response, not every image, font, stylesheet and script subsequently loaded by a browser.
No. The score covers selected technical signals only. Content quality, backlinks, crawlability, user experience and search intent still matter.
No. Private, local and reserved network destinations are blocked to protect internal infrastructure.
The audit reads the canonical link tag from the returned HTML only. Relative URLs, staging domains or CMS misconfiguration can make the detected value differ from the live public URL.
Without a viewport meta tag, mobile browsers may scale the page like a desktop site. That hurts readability on phones and is flagged as a basic technical issue.
Prioritise HTTP errors, missing titles, duplicate H1 headings and blocking robots directives first. Cosmetic metadata improvements can follow once the page is reachable and indexable.