Ignoring findings & tuning

Not every finding needs action. A template pack full of hardcoded colors, an intentional design choice, a rule that doesn’t fit your workflow — you can silence these so your scans stay focused on real problems.

Two ways to ignore

Each finding has two ignore options:

• Ignore — hides this specific finding (this element/group). Use it when a particular case is intentional but you still want the rule active elsewhere.
• Ignore rule — hides every finding from that rule, across the whole project. Use it when a rule doesn’t apply to how you build.

Ignored items don’t count against your Health Score, and you can see and undo every ignore under Settings → Ignored.

Turning off whole audits

If an entire category isn’t relevant to a project, toggle it off under Settings → Scan modules. A disabled module is skipped during scans and doesn’t affect the score. Turn it back on any time.

When to ignore vs fix

• Fix when the finding reflects real debt — hardcoded colors on your own site, duplicated styles, mobile overflow.
• Ignore when it’s a deliberate choice — a one-off brand color, a decorative pattern, a third-party template you don’t intend to refactor.

Tuning is normal. A scan you trust is one where every remaining finding is something you’d actually act on.