Technical
Status code, redirects, HTTPS, content type, doctype, language, viewport, canonical, heading hierarchy, document size.
02 / Vector / Diagnosis
VECTOR
Web Clinic
ExamineDiagnosePrescribeImprove
Examine a website. Find the structural problems. Get a prioritised prescription. Run it again and watch the score move.
Examining website
Examination failed
The website could not be examined.
Reason:
Possible causes
Recently examined
Latest score per website, newest first. Only examinations whose requester left the listing option on appear here.
What the engine measures
Measured,
not implied.
Seven analyzers read the live document, its response headers, robots.txt, the sitemap, and a bounded sample of links. Each finding carries its evidence. Scores are deducted from findings only; the methodology is printed with every report.
SEO
Title and description length, canonical, robots meta and X-Robots-Tag, Open Graph, image alt coverage, robots.txt, sitemap.
Performance
Response time, document weight, script and stylesheet counts, render-blocking and third-party scripts, image sizing and lazy loading, compression, caching. Not Core Web Vitals.
Accessibility
Alt attributes, form labels, button and link names, landmarks, skip link, language, generic link text. Contrast needs a rendered page and is not measured.
Security
HTTPS, HSTS, CSP, X-Content-Type-Options, framing protection, Referrer-Policy, version disclosure, mixed content, insecure forms. A header review, not a vulnerability scan.
Links and content
Broken links, redirect chains, insecure internal links, internal link presence; word count, text ratio, headings, paragraph length, placeholder text.
How to audit a website with Vector
Enter the address of any public website and press Examine. The engine fetches the page, runs seven analyzers over the document, its headers, robots.txt, the sitemap, and a sample of links, then scores each category and combines them into one health score. The whole run usually takes ten to twenty seconds and the page shows each stage as it completes.
The report lists every issue ranked from critical to low with four parts: the evidence the analyzer saw, why it matters, the prescription, and the expected impact. The prescription section orders the fixes so the first items move the score most.
What a good score means
Scores are deducted from findings only, so a page with no detected problems scores 100. A score in the eighties usually means a handful of medium issues such as missing security headers or images without dimensions. A score below sixty almost always includes a critical or several high findings: no HTTPS, a server error, a noindex left on a live page, or many broken links.
Because the audit reads the document rather than rendering it, it complements rather than replaces a Core Web Vitals report. Use Vector to find structural and SEO problems, then a field-data tool for loading performance on real devices.
Questions
Is this website audit free?
Yes. Enter any public website address and the examination runs on the engine at no cost, with no account. Public use is rate-limited per visitor to keep it available.
What does the audit check?
Seven areas: technical structure, SEO tags and files, document-level performance, accessibility markup, security headers, a sample of links, and content. Each finding shows its evidence and a fix.
Is the score the same as Google PageSpeed or Lighthouse?
No. Vector reads the HTML document and response headers; it does not run a browser, so it does not measure Core Web Vitals. It is a structural audit, and the methodology is printed with every report.
Can I share the report?
Every examination gets a permanent link. Send it to a colleague or a client, or save it as a PDF from the report.
Will my website appear on the recently examined list?
Only if you leave the listing option on when you run it. Untick it and the domain and score are kept private to the report link.
Architecture
The analysis engine.
A request creates an audit record and returns its id immediately. A worker runs the analyzers in sequence, writing the stage to the record as it goes, then the scoring engine derives category scores and the health score and the prescription is stored. The page polls the record and never waits on the crawl.
- 01Frontend request
- 02FastAPI
- 03Audit job
- 04Analyzers
- 05Scoring engine
- 06PostgreSQL
- 07Diagnostic report
Every outbound request passes an SSRF policy: http and https only, no private, loopback, link-local, or cloud-metadata addresses, DNS results checked, every redirect re-validated, response size and time capped, at most a fixed number of links checked per examination. Public examinations are rate-limited per client.
Research: designing the scoring engine ↗ · Research: the crawler's safety policy ↗
Have a project in mind?