Frequent questions

Yes. There is no account, no card and no trial timer. The report is meant to be useful whether or not you ever work with the studio.

We fetch the page once to measure it. The HTML source may be cached for a few days so the report can quote evidence, then it is deleted automatically. We do not crawl the rest of the site unless the audit asks for a small number of internal pages, and the limit is configurable.

Those tools are excellent and we do not replicate them. This audit is wider: it combines availability, TLS, technical SEO, performance signals, accessibility, UX, security headers, content and AI search readiness into one weighted score, and every finding explains why it matters and what to do. We never pretend to have run Lighthouse.

Any public http or https page. Addresses that resolve to localhost, private ranges, link-local or cloud metadata endpoints are refused before any request is made, so the tool cannot be pointed at internal infrastructure.

Because the condition it tests does not exist on that page — a page with no images has no image alt text to check, a page with no forms has nothing to label. Not applicable checks are excluded from the category score instead of being counted as passes or failures.

Qvicom Marketing & Design Studio, a bilingual studio in Miami and Bogotá. If you send the report form with your contact details, we store them to reply to you, and only for that. Consent is never pre-selected, and you can ask for deletion at any time.

No. It is free, it needs no account, and nothing is hidden behind a "contact us to see the rest" wall. The full report, with every check and every measured value, is shown on screen.

Only when source storage is switched on for this installation, and only for a limited number of days, so a finding can be re-read against what was actually served. A maintenance task deletes it afterwards and it is never published.

Any public page. Addresses that resolve to private, internal or reserved ranges are refused before a request is made, and an audit makes one request: it does not crawl, brute-force or probe anything.

Different measurement. Those tools drive a browser, execute JavaScript and repeat tests; this audit reads one real server response — markup, headers, certificate and timing — and scores only what it can verify from that response.

No, and nobody outside those systems does. The AI search readiness checks describe how machine-readable a page is — structured data, clear headings, crawlable content — and promise no position anywhere.

No. It is an automated review of the served HTML. Those checks catch a share of the problems; a manual WCAG 2.2 review, including assistive technology, is still needed before claiming conformance.

After meaningful changes: a new template, a plugin update, a redesign, a move to another host. The result is a snapshot of one request, so running it daily says little unless the site changes daily.

Print it from the browser, or download the self-contained HTML file and open it anywhere. Both keep every measurement; the platform does not invent a designed PDF.

Then the report says so. A blocked, redirected or unreachable request is recorded as the result, with the reason, instead of being turned into a guess.

No. Audit records stay on this server, these pages carry no advertising or analytics trackers, and the studio only sees what you send through a contact form.