Skip to content
https://www.perfectmedspa.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
75
GRADE
C
FIX
7
REVIEW
7
PASS
10
INFO
0
Checks
24
10 PASS 7 REVIEW 7 FIX
D
Landmark Structure
Action
5 landmarks
FIX
5 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Page Structure — as a screen reader sees it
BANNER header NAV MAIN (missing!) CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

D
Tap Target Adequacy
Action
26 tap target(s) too small or too close together
FIX
26 tap target(s) too small or too close together
Warning::
26 tap target(s) too small or too close to neighbors
WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModeNo Dark Mode Detected
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
2 navigation landmark(s) detected
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Heading Hierarchy
20 headings, 2 skip(s)
REVIEW
20 headings, 2 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 Lose 10–20 lbs Without Surgery or Downtime
  • H2 Lift, Tighten & Restore — Without Surgery
  • H2 The Future of Longevity & Metabolic Optimization
  • H1 Welcome toPerfect Medspa, Medical Spa in New York City
  • H2 Some of Our Featured Services
  • H4 Perfect Face skipped
  • H4 Perfect Body
  • H4 Perfect Medical
  • H4 Perfect Hair
  • H2 Why Perfect Med Spa In NYC
  • H2 About Perfect Med Spa
  • H4 Licensed Staff skipped
  • H4 Best Technology
  • H4 Personal Touch
  • H4 Customer Integrity
  • H2 Before & After Gallery
  • H2 Glow with Confidence at Perfect MedSpa Located to serve Midtown Manhattan and Long Island
  • H2 See What Our Clients Are Saying
  • H2 Locations:
  • H2 Locations:

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

B
Iframe Accessibility
2/3 iframe(s) missing title; 0 placeholder(s)
REVIEW
2/3 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
B
Mobile-Readable Font Sizes
93% of visible text renders at >= 12 CSS px (3 below threshold)
REVIEW
93% of visible text renders at >= 12 CSS px (3 below threshold)
Info::
3 text node(s) render below 12 CSS pixels on mobile
Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <span> 0.0px ("location"); <span> 0.0px ("whatsapp"); <span> 0.0px ("chat").
C
404 Error Page
Action
Could not test
REVIEW
Could not test
Info::
404 page could not be tested
The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

B
Favicon & Branding
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 5 fail WCAG AA
REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

15 pass 5 fail WCAG AA 2 pass AA only
button Accept All
2.67:1
#FFFFFF
on
#9F9E9E
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span Customize Consent Preferences
1.18:1
#212121
on
#302D2B
needs 4.5:1 (normal text)
16px · above the fold
p We use cookies to help you navigate effi…
2.44:1
#000000
on
#504B48
needs 4.5:1 (normal text)
16px · above the fold
p The cookies that are categorized as "Nec…
1.43:1
#000000
on
#332524
needs 4.5:1 (normal text)
16px · above the fold
button Show more
2.44:1
#000000
on
#634537
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient

2 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Welcome to20.12:13.0:1
#000000
#FAFAFA
Pass
h1 Perfect Medspa, Medi…20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Some of Our Featured…20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Why Perfect Med Spa …20.12:13.0:1
#000000
#FAFAFA
Pass
h2 About Perfect Med Sp…20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Before & After Galle…20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Glow with Confidence…20.12:13.0:1
#000000
#FAFAFA
Pass
h2 See What Our Clients…20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Locations:20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Locations:20.12:13.0:1
#000000
#FAFAFA
Pass
title Aesthetic Services &…9.02:14.5:1
#000000
#D4A151
Pass
p We value your privac…11.70:14.5:1
#212121
#EED9B9
Pass
p We use cookies to en…21.00:14.5:1
#000000
#FFFFFF
Pass
button Customize5.22:14.5:1
#1863DC
#FAFAFA
Pass
button Reject All5.04:14.5:1
#1863DC
#F6F6F6
Pass
button Accept All2.67:14.5:1
#FFFFFF
#9F9E9E
Fail
span Customize Consent Pr…1.18:14.5:1
#212121
#302D2B
Fail
p We use cookies to he…2.44:14.5:1
#000000
#504B48
Fail
p The cookies that are…1.43:14.5:1
#000000
#332524
Fail
button Show more2.44:14.5:1
#000000
#634537
Fail

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

C
Lighthouse Accessibility Audits
Action
Score 70/100 — 9 failing, 22 passed
REVIEW
70

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

ARIA

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
 location div.et_pb_module_inner > ul.dsm_icon_list_items > li.dsm_icon_list_child > div.dsm_icon_list_tooltip
 whatsapp div.et_pb_module_inner > ul.dsm_icon_list_items > li.dsm_icon_list_child > div.dsm_icon_list_tooltip

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.dvmm_menu_inner_container > div.dvmm_content > div.dvmm_element > button.dvmm_icon div.dvmm_menu_inner_container > div.dvmm_content > div.dvmm_element > button.dvmm_icon

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.et_pb_column > div.et_pb_module > div.et_pb_code_inner > iframe.perfmatters-lazy div.et_pb_column > div.et_pb_module > div.et_pb_code_inner > iframe.perfmatters-lazy

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.dvmm_content > div.dvmm_element > div.dvmm_mobile__menu > a.dvmm_mobile_menu_toggle div.dvmm_content > div.dvmm_element > div.dvmm_mobile__menu > a.dvmm_mobile_menu_toggle
div.et_pb_section > div.et_pb_module > div.et-pb-slider-arrows > a.et-pb-arrow-prev div.et_pb_section > div.et_pb_module > div.et-pb-slider-arrows > a.et-pb-arrow-prev
div.et_pb_section > div.et_pb_module > div.et-pb-slider-arrows > a.et-pb-arrow-next div.et_pb_section > div.et_pb_module > div.et-pb-slider-arrows > a.et-pb-arrow-next

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
SCULPTRA $599 (REG $800) div.et_pb_module_inner > div.dsm_card_wrapper > div.dsm_card_carousel_child_description > p
BOOK NOW div.et_pb_row > div.et_pb_column > div.et_pb_button_module_wrapper > a.et_pb_button

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Perfect Face div.et_pb_module > div.et_pb_module_inner > div.dsm_flipbox_wrapper > h4.dsm-title
LICENSED STAFF div.et_pb_module > div.et_pb_blurb_content > div.et_pb_blurb_container > h4.et_pb_module_header

These are opportunities to improve keyboard navigation in your application.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
1 div.et_pb_section > div.et_pb_module > div.et-pb-controllers > a
2 div.et_pb_section > div.et_pb_module > div.et-pb-controllers > a.et-pb-active-control
3 div.et_pb_section > div.et_pb_module > div.et-pb-controllers > a
Botox div.et_pb_module > div.et_pb_text_inner > p > a
Coolsculpting div.et_pb_module > div.et_pb_text_inner > p > a
Morpheus8 div.et_pb_module > div.et_pb_text_inner > p > a
PDO Thread Lift div.et_pb_module > div.et_pb_text_inner > p > a
Fotona 4D Facelift div.et_pb_module > div.et_pb_text_inner > p > a
DiamondGlow Facial div.et_pb_module > div.et_pb_text_inner > p > a
Dermal Fillers div.et_pb_module > div.et_pb_text_inner > p > a
PRP Hair Restoration div.et_pb_module > div.et_pb_text_inner > p > a
NightLase (Snoring) div.et_pb_module > div.et_pb_text_inner > p > a
Ultherapy div.et_pb_module > div.et_pb_text_inner > p > a
Blog div.et_pb_module > div.et_pb_text_inner > p > a
Our Philosophy div.et_pb_module > div.et_pb_text_inner > p > a
Reviews div.et_pb_module > div.et_pb_text_inner > p > a
Patient Sign Up div.et_pb_module > div.et_pb_text_inner > p > a
Our Med Spa Team div.et_pb_module > div.et_pb_text_inner > p > a
Gallery div.et_pb_module > div.et_pb_text_inner > p > a
Our Specials div.et_pb_module > div.et_pb_text_inner > p > a
Payment Plans div.et_pb_module > div.et_pb_text_inner > p > a
Contact Us div.et_pb_module > div.et_pb_text_inner > p > a
Sitemap div.et_pb_module > div.et_pb_text_inner > p > a
Privacy Policy div.et_pb_module > div.et_pb_text_inner > p > a
Terms Of Use div.et_pb_module > div.et_pb_text_inner > p > a
HIPAA div.et_pb_module > div.et_pb_text_inner > p > a

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.js html.js

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Image elements have `[alt]` attributes
●Form elements have associated labels
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○No form fields have multiple labels
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
A+
Heading Text Quality
All 20 heading(s) have substantive, well-formed text
PASS
All 20 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 21 images OK
PASS
All 21 images OK
Info::
6 decorative image(s) correctly marked
Info::
15 image(s) with good alt text
21 images 15 good alt text 6 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 9 controls have issues
PASS
1 of 9 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" name="s">
Info::
8 control(s) properly labeled
9 controls
8 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
ak_hp_textareatextareaΔnone
#input_2_8textLinkedInfor/id
#input_2_1_3textFirstfor/id
#input_2_1_6textLastfor/id
#input_2_2emailEmail(Required)for/id
#input_2_3telPhone(Required)for/id
#input_2_4textareaMessage(Required)for/id
#input_2_5_1checkboxI agree to the terms of use.for/id
ssearch(Search ...)placeholder only

Placeholder text disappears on focus and is not a reliable label.

<input type="search" name="s">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

A+
Form Input Types
9 form control(s) checked, no type mismatches
PASS
9 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
9 form control(s) checked, no input-semantic issues
PASS
9 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "en-US"
PASS
Lang attribute set to "en-US"
Info::
<html lang="en-US"> is set and valid
Got: en-US
A+
Tabindex Anti-Patterns
6 explicit tabindex attribute(s) checked, no anti-patterns
PASS
6 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
No `<meta name="theme-color">` -- browser chrome falls back to default
Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback