Page speed
Measures server response and HTML loading time from the scan region, then compares those observations with mobile Lighthouse performance data.
Free technical website audit
Website Health Scanner
Enter a public website URL and get a practical repair report for speed, mobile usability, forms, links, SEO basics, and Core Web Vitals.
No account required. The scanner checks public pages only.
Recent scans
No scans saved yet.
Ready for your first scan
The report crawls a sample of internal pages and checks speed, images, forms, buttons, mobile signals, links, metadata, and Core Web Vitals risks.
What the audit covers
Eight checks that turn technical signals into repair work
The scanner combines a small same-site crawl with page metadata, asset checks, and mobile PageSpeed data when it is available. Each result explains the signal, its likely impact, and a practical next action.
Image weight
Samples image files for unusually large downloads, missing lazy loading, outdated formats, and missing alternative text.
Forms
Checks whether forms have plausible actions, named fields, useful methods, and a visible way for a visitor to submit the form.
Buttons
Looks for important controls that are hidden, empty, or missing readable labels that people and assistive technology can understand.
Mobile layout
Reviews viewport configuration, fixed-width elements, text sizing signals, and relevant mobile usability audits from PageSpeed.
Broken links
Tests a controlled sample of links and reports failed destinations, redirect problems, and pages the crawler could not reach.
Search metadata
Checks page titles, meta descriptions, heading structure, canonical hints, and indexing signals that help search engines interpret a page.
Core Web Vitals
Explains Largest Contentful Paint, Interaction to Next Paint, and Cumulative Layout Shift using field or lab data when available.
From report to repair
Use severity as a starting point, not as a verdict
A critical result points to a strong technical signal, but it still needs human review. Start with failures that block visitors: unreachable pages, broken contact paths, severe mobile layout problems, and very slow loading. Then handle warnings that affect discoverability or repeated page templates.
The repair plan ranks up to five findings by severity. Fix one item, deploy the change, and scan again. A second scan is most useful when it confirms a specific change rather than chasing a perfect score.
Read the step-by-step website repair guidePractical resources
Keep the work moving after the scan
Use these hands-on guides to verify an important visitor journey, diagnose a report finding, and document what changed. They are written to support the scanner, not to inflate a score.
Website repair guidePrioritize fixes for speed, images, mobile layouts, links, and search basics.
Manual audit checklistWork through the essential visitor journey before a launch or redesign.
Contact form testing guideTest a real inquiry from validation through successful delivery.
Core Web Vitals guideSeparate LCP, INP, and CLS problems before changing a template.
Read results correctly
What an automated audit can and cannot prove
It finds reproducible signals
The audit is good at identifying status codes, heavy files, missing metadata, measurable layout hints, and patterns in the pages it crawls. The report records the scan region so network distance is not confused with the visitor experience everywhere in the world.
It does not replace a real inquiry
A form can look technically valid and still fail after submission. A button can exist in the HTML and still be covered by a cookie banner. Always complete a real mobile visit, submit a test inquiry, and review important pages in a browser.
Results are a time-stamped sample
Websites and third-party services change constantly. A crawl covers a limited number of same-site pages and links, so a passing result is useful evidence, not a permanent guarantee for every URL.