QA reports & scores

Know exactly what to fix, page by page.

Every scan gives each page a score out of 100 and a red, amber or green status, with every issue highlighted on a screenshot. When it's ready, share the report with your client in one link.

Get startedSee pricing
  • Set up in 30 seconds
  • Unlimited scans
  • No code required

Updated

How scores work

Simple to read. Hard to argue with.

  • 100%

    is the only score that counts as passed

  • 75%

    and above is amber, anything lower is red

  • Every

    scan kept on the project for before-and-after

What's in a report

Scores you can actually act on.

  1. 01One score per page

    Weighted by what matters

    Each page's score is based on every issue found across copy, links, forms, alt text and accessibility, relative to how many elements the page has. Major issues count for more than minor ones.

    • Green: 100%, all checks passed
    • Amber: 75% to 99.9%, some issues found
    • Red: below 75%, needs improvement
  2. 02Highlighted on the page

    See every issue where it sits

    Open any page to see its issues listed by check, with major and minor severity, alongside the page itself and its Figma design.

  3. 03Client sharing

    Send your client the real report

    Turn on a share link from any finished scan and your client can open the report without logging in. They see when the site was scanned and by which team, each page next to its Figma design, and every issue grouped by type.

    • No login needed to view
    • Include your markers, or keep them internal
    • Reset or turn off the link at any time
  4. 04History

    Every scan kept

    Every scan stays on the project, so you can compare before and after. The project score is the average across its scans, and failed or cancelled scans count as 0%.

    Broken link checking

Frequently asked questions about QA reports

  • It's based on all the issues found on the page (copy, links, forms, alt text and accessibility) relative to how many elements the page has. Major issues count for more than minor ones.

  • Green is 100%, the only score that counts as passed, labelled “All checks passed”. Amber is 75% to 99.9% (“Some issues found”), and red is below 75% (“Needs improvement”).

  • It's the average across the project's scans. Failed or cancelled scans count as 0%.

  • Yes. Open any finished scan, click Share and turn on the link. Anyone with the link can view the report without logging in, and you choose whether your markers are included. You can reset or turn off the link at any time. Team admins and project leads can share; cancelled or failed scans can't be shared.

  • Yes. Every scan is kept on the project, so you can show a before-and-after.

Explore Frank

See what else Frank does for you.

  1. 01

    Accessibility checks

    Frank flags missing alt text and common accessibility issues on every page, from skipped heading levels to unlabelled form fields.

    Feature
  2. 02

    Broken link checking

    Frank tests every internal and external link on every page, follows redirects, and flags 404s, server errors and dead development links.

    Feature
  3. 03

    Figma design QA

    Map your Figma pages to your live site once, then review every page side by side with its approved design.

    Feature
  4. 04

    For Framer

    Automated QA for Framer sites: check every page and CMS page on your staging or preview URL before you publish to your domain.

    Solution
  5. 05

    For Webflow

    Automated QA for Webflow sites: check every page and CMS template on your webflow.io staging site before you connect the domain.

    Solution
  6. 06

    For WordPress

    Automated QA for WordPress sites: check every page on your staging site for lorem ipsum, broken links and accessibility before launch.

    Solution
  7. 07

    For agencies

    Consistent, automated QA across every project and every team member, with a scored record of every scan.

    Solution
  8. 08

    For freelancers

    A second pair of eyes for solo designers and developers: automated checks on every page, so you can hand over with confidence.

    Solution
  9. 09

    Frank vs BugHerd

    BugHerd collects visual feedback from clients and teams. Frank runs automated QA checks on every page. Here's how they compare.

    Comparison
  10. 10

    Frank vs Pixelay

    Pixelay overlays a Figma design on a live page inside Figma. Frank reviews every page against its design and runs automated QA checks too.

    Comparison
  11. 11

    Frank vs Sitepager

    Sitepager tracks what changes on a site between updates. Frank checks a build before launch and lines it up with the Figma design. Here's how they compare.

    Comparison
  12. 12

    Frank vs manual QA

    Manual QA is slow, inconsistent and easy to skip. Frank automates the repetitive half, so your team keeps the judgement calls.

    Comparison
  13. 13

    Lorem ipsum checker

    Frank checks every block of visible text on every page for Latin filler, in any word order, and flags it before your client sees it.

    Feature
  14. 14

    Team markers

    Pin issues straight onto a scanned page, comment, @mention a teammate and filter by priority, so nothing gets lost between review and fix.

    Feature

More on pre-launch QA

All articles

Know what to fix before launch.

Run your first scan in minutes. Every plan includes unlimited projects and unlimited scans.

Get startedSee pricing
  • Set up in 30 seconds
  • Unlimited scans
  • No code required