Documentation

Everything you can do in Orilyt: run audits, read reports, manage your account and use the REST API.

Run an audit

Orilyt audits any website from its URL — WordPress, Shopify, Wix, Webflow, PrestaShop, custom sites. No plugin, no admin access. Read-only.

Two entry points

  • Public page (home page): enter a URL, a full report is generated instantly. No account needed.
  • Dashboard (logged in): enter a URL, a full report is generated and saved in your audit history.

Orilyt is read-only. It does not modify the audited site, does not set any cookies on the target site, and requires no installation.

Supported CMS

  • Universal tests apply to all CMS and static sites (performance, security, SEO, UX, compliance).
  • 9 additional tests are WordPress-specific (exposed version, plugins, XML-RPC, readme.html, etc.).

The tests

Tests are grouped into 5 categories:

  • Performance — compression, cache, HTTP/2, images, lazy loading, TTFB, page weight
  • Security — SSL, HSTS, security headers, Safe Browsing, IP reputation, cookies
  • SEO — meta title, canonicals, Open Graph, structured data, sitemap, robots.txt
  • UX — mobile friendly, navigation, readability, keyboard accessibility, favicon
  • GDPR / Legal — legal pages, secure forms, cookie consent, third-party trackers

Drawers (details)

Each test in the report has a drawer — a detail panel that opens when you click the test row. Same structure for all tests.

Drawer structure

  1. Facts (observed) — the values actually measured or detected on the page.
  2. Interpretation — the one-line, decision-ready verdict.
  3. What to do (recommended) — the fix to apply, with priority, risk and estimated effort.
  4. Optional — advanced or complementary steps, when they apply.
  5. Verification — how to confirm the fix worked.
  6. Glossary — No-code mode only: definitions of the technical terms used in the drawer.

In Agency mode, some drawers include server-configuration snippets (a box with a Copy button). Use them as-is, but test on a staging environment when possible. In No-code mode these snippets are replaced by step-by-step plugin instructions.

Drawer access

Drawers are open to everyone. The public report shows the full detail of every check, with no account and no share link.

Limits

What the audit can measure, and what it cannot.

Technical limits

  • Audits are based on what is reachable over HTTP at scan time (timeouts, WAF, blocks can affect results).
  • Some tests are not measurable on a given sample (example: no images means lazy-loading cannot be evaluated).
  • Scores are indicators. Use them to prioritize, then verify with the verification steps in drawers.
  • Timeout per test: 15 seconds. Global audit timeout: 5 minutes.

Glossary

Definitions of terms used in Orilyt and in this documentation.

Terms

Audit

Automated analysis of a website covering performance, security, SEO, UX and compliance. Run from a URL, no admin access required.

Drawer

Detail panel associated with each test. Contains observed facts, interpretation, recommendation and verification steps.

Public report

A report reachable without authentication. It shows the scores and the full detail of every drawer.

Score

Rating out of 100 calculated from weighted results of each test. Available as global score and per-section scores.

Read-only scan

The audit does not modify the target site, does not set any cookies, and requires no installation or admin access.