Site Audit Module
The Site Audit module catches problems on your website before your visitors do — broken buttons, slow-loading pages, missing SEO tags, and security weak points — by scanning the whole site the way a real visitor would, on desktop and mobile. Every scan comes back as a full report with a screenshot of each page and exactly what needs fixing.
Main sections
- New Audit — Enter a URL, choose which devices and test categories to run, and start a scan.
- Sites — Websites you have audited before, for quick re-runs.
- Schedules — Set up an audit to run automatically on a recurring schedule, with the report emailed to you.
- History — Every audit you have run, with its score and a link to the full report.
- Credits — Your available audit credits and usage.
Test categories
- QA + UX + UI — Page load health, headings, calls to action, layout overflow, fonts, and tap target sizing.
- Functionality — Buttons, forms, dropdowns, tabs, accordions, and modals.
- Core Web Vitals — Real browser performance timing (how fast the page feels to a visitor).
- SEO + Headers + Privacy — Meta tags, social sharing tags, structured data, security headers, and cookie consent.
- Images + Accessibility — Image formats, lazy-loading, alt text, color contrast, and screen-reader support.
- Security suite — Common vulnerability and authentication checks.
- Screenshots — Full-page and annotated screenshots saved per page and device.
How credits work
Each audit costs credits based on how many pages, devices, and test categories you choose. Roughly speaking, one credit covers one test category run against one page-and-device combination. Credits are only deducted for scans that actually complete — if an audit fails, it is refunded automatically. Your remaining credit balance is shown on the Credits page before you start a new audit.
Most test categories are charged per page and per device, since results can differ between a desktop screen and a phone — for example, running Functionality checks on 10 pages across 3 devices uses more credits than running it on the same pages with just 1 device selected. Security and Kol One Service are charged once per page regardless of how many devices you pick, since those checks do not change by screen size.
| Example | Pages | Devices | Credits |
|---|---|---|---|
| Small smoke test | 8 | 1 | ~16 |
| Typical full check | 20 | 3 | ~140 |
| Full enterprise audit | 50 | 3 | ~800 |
How to run your first audit
- Open the Site Audit module from your app navigation.
- Click New Audit in the top menu.
- Enter the URL of the website you want to scan (e.g.
https://yoursite.com). - Choose which devices to test on — Desktop, Mobile, or both.
- Select the test categories you want to run. Not sure? Enable all of them for a full picture.
- Review the estimated credit cost shown at the bottom, then click Start Audit.
- The scan runs in the background. You will get an email when it is ready — or check History to see its progress.
- Open the finished report and click any page row to see its screenshot and the full list of findings.
Reading a report
When the audit finishes, the report opens automatically. Here is what each part of the report means:
Scores run from 0–10. Green (8+) means passing, orange (6–7.9) needs attention, red (below 6) has serious issues. Click a card to filter the findings list to that category only.
| URL | Score | Issues | Screenshot |
|---|---|---|---|
| / (Home) | 9.6 | 2 Critical | 🖼 |
| /pricing | 7.4 | 5 High | 🖼 |
| /contact | 5.1 | 8 Critical | 🖼 |
Click any row to expand findings for that page. The 🖼 icon opens the full-size screenshot — annotated versions mark exactly where each issue appears on the page.
/pricing · Mobile · Functionality
/ (Home) · Desktop · Core Web Vitals
/contact · SEO + Headers
Each finding shows the severity, what the problem is, and which page and device it was found on. Click a finding to jump to its annotated screenshot.
Credits — history and the "+" sign
Open the Credits tab to see your balance, usage, and the full transaction ledger.
Your balance is shared across your whole team. All members spend from the same pool.
| Date | Type | Amount | Note |
|---|---|---|---|
| 23 Sep 2025 | Top-up | +500 | Package purchase |
| 22 Sep 2025 | Spend | −140 | Audit #2041 — yoursite.com (20 pages) |
| 21 Sep 2025 | Refund | +38 | Audit #2039 failed — credits returned |
| 20 Sep 2025 | Spend | −38 (+38 back) | Audit #2039 — failed.com (failed) |
What does the green "(+38 back)" mean? Credits are charged upfront based on what you requested, then automatically adjusted once the scan finishes. Two situations trigger a refund:
- Audit failed completely — the site could not be reached or the scan crashed. You get a full refund of every credit that was charged.
- Fewer pages than requested — if you asked to scan 20 pages but the site only has 10, only 10 pages were actually scanned. The credits for the 10 pages that were never scanned are refunded automatically.
The original Spend row stays in the ledger for transparency, and the refunded amount appears next to it in green so you can see exactly what was taken and what came back. A separate Refund row also appears to confirm the credit was returned to your balance.
Was this article helpful?