Webmaster Website Audit

Run a deeper technical audit for performance, on-page SEO, crawlability, link authority signals, canonical health, structured data, social previews, security headers, and accessibility basics.

Webmaster performance, SEO, and crawl audit

Test a Website URL

Prioritized issues, category scores, canonical checks, internal link samples, robots, sitemap, schema, and security signals.

Enter a public URL to test the page response.

Overall Score

Page Summary

Final URL-

Status-

Redirects-

Content type-

-Performance

-SEO

-Link Authority

-Accessibility

-Security

0Critical

0High

0Medium

0Low

0/0Checks Passed

Priority Issues

Speed Metrics

TTFB-

Total fetch time-

HTML size-

Compression-

Cache-Control-

Page Structure

Word count-

Scripts-

Stylesheets-

Images-

Preloads-

Third-party script hosts-

On-Page SEO

Title-

Meta description-

Canonical-

Meta robots-

Structured data-

Canonical health-

Headings and Accessibility

H1 count-

Heading outline-

Missing image alt-

Images missing size-

Lazy images-

Language-

Link Authority Proxy

Internal links-

External links-

Nofollow links-

Anchor-only links-

Internal crawl sample-

Google PageRank is not public. This score estimates crawl depth and internal link strength from the scanned HTML.

Crawlability and Security

robots.txt-

sitemap.xml-

Social preview

Favicon / hreflang-

HSTS-

CSP-

X-Content-Type-Options-

Webmaster Checks

Sampled Internal URLs

Recommendations

Browser lab note: This scan does not execute JavaScript, capture filmstrips, or measure live Core Web Vitals. Use it as a fast technical audit before Lighthouse, GTmetrix, or field data.

What This Webmaster Website Audit Measures

This test fetches the HTML of a public URL from Speedtest.now and reports practical technical signals: HTTP status, redirect chain, time to first byte, total fetch time, response size, compression, cache headers, script and stylesheet counts, image usage, title, meta description, canonical tag, robots directives, structured data, heading outline, internal links, robots.txt, sitemap.xml, and security headers. If the issue looks network-related rather than page-related, compare it with an internet speed test and a DNS speed test.

How It Differs From GTmetrix or Lighthouse

GTmetrix and Lighthouse run a full browser render, execute JavaScript, capture Core Web Vitals, and analyze render-blocking resources. This tool is lighter and faster: it checks whether the server responds quickly and whether the raw HTML gives search engines, browsers, and crawlers a healthy starting point. Use it as a technical triage step before deeper browser lab testing.

PageRank and Link Authority Signals

Google PageRank is not public, so no third-party tool can show the real PageRank for a URL. This scan gives a link authority proxy by checking contextual internal links, external links, nofollow usage, canonical tags, robots.txt, sitemap availability, and redirect depth. Strong internal linking helps important pages receive more crawl attention and pass relevance through the site.

How to Use the Results

Start with TTFB and redirects. If TTFB is high, improve hosting, caching, CDN routing, or backend work. If HTML is large, reduce server-rendered markup and inline payloads. If compression or cache headers are missing, fix those at the web server or CDN. Then review SEO, headings, schema, image alt text, and body links so the page is both fast and understandable. If the page only feels slow on your own connection, run a loaded latency test to check whether local bufferbloat is involved.

What Is a Good Website Speed Score?

A score above 85 usually means the first HTML response and technical foundation are healthy: the server answers quickly, the page is compressed, metadata is present, crawl signals are clean, and internal links support discovery. A score from 70 to 84 is usable but worth improving. Below 70 usually means the page has a clear performance, crawlability, content, security, or HTML weight issue.

Common Website Speed Problems

Slow pages usually come from one of five places: high TTFB, too many redirects, uncompressed text, weak cache headers, or too many render-critical assets. DNS can also add delay before the browser connects, so use the DNS test if page loads feel slow across many sites. If only one site is slow, the bottleneck is more likely the website itself.

Website Speed and SEO

Search engines need a clean HTML foundation before they can evaluate content quality. This page checks the basics that often break at the same time as performance: title, meta description, canonical, headings, schema, robots, sitemap discovery, and internal links. For broader technical SEO cleanup, combine this test with the testing accuracy guide, methodology, and your own crawl data.