Boxes mark elements that failed a check. Hover or focus an element
in the lists below to highlight it here.
Accessibility — 3 failing checks
1Finding 1:
Links do not have a discernible name
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.
Fix all of the following:
Element is in tab order and does not have accessible text
Fix any of the following:
Element does not have text that is visible to screen readers
aria-label attribute does not exist or is empty
aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
Element has no title attribute
div.wpb_wrapper > div.nectar_icon_wrap > div.nectar_icon > a
Fix all of the following:
Element is in tab order and does not have accessible text
Fix any of the following:
Element does not have text that is visible to screen readers
aria-label attribute does not exist or is empty
aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
Element has no title attribute
div.wpb_wrapper > div.nectar_icon_wrap > div.nectar_icon > a
Fix all of the following:
Element is in tab order and does not have accessible text
Fix any of the following:
Element does not have text that is visible to screen readers
aria-label attribute does not exist or is empty
aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
Element has no title attribute
div.wpb_wrapper > div.nectar_icon_wrap > div.nectar_icon > a
Fix all of the following:
Element is in tab order and does not have accessible text
Fix any of the following:
Element does not have text that is visible to screen readers
aria-label attribute does not exist or is empty
aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
Element has no title attribute
div.wpb_wrapper > div.nectar_icon_wrap > div.nectar_icon > a
Fix all of the following:
Element is in tab order and does not have accessible text
Fix any of the following:
Element does not have text that is visible to screen readers
aria-label attribute does not exist or is empty
aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
Element has no title attribute
div.wpb_wrapper > div.nectar_icon_wrap > div.nectar_icon > a
Fix all of the following:
Element is in tab order and does not have accessible text
Fix any of the following:
Element does not have text that is visible to screen readers
aria-label attribute does not exist or is empty
aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
Element has no title attribute
2Finding 2:
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Fix any of the following:
Element has insufficient color contrast of 4.28 (foreground color: #e62525, background color: #f9f9f9, font size: 10.5pt (14px), font weight: normal). Expected contrast ratio of 4.5:1
Fix any of the following:
Element has insufficient color contrast of 3.05 (foreground color: #ffffff, background color: #ff5a5f, font size: 10.5pt (14px), font weight: normal). Expected contrast ratio of 4.5:1
3Finding 3:
Heading elements are not in a sequentially-descending order
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.
Measured in a simulated mobile environment. These are
readings, not checks — treat them as context for the performance
score rather than defects to close.
7.2 sFirst Contentful Paint
12.1 sLargest Contentful Paint
460 msTotal Blocking Time
0Cumulative Layout Shift
7.2 sSpeed Index
Performance — 12 opportunities
Font display
Consider setting `font-display` to `swap` or `optional` to ensure text is consistently visible. `swap` can be further optimized to mitigate layout shifts with font metric overrides.
A forced reflow occurs when JavaScript queries geometric properties (such as `offsetWidth`) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Accessibility: 21 checks passed, 42 not applicable
`[aria-*]` attributes match their roles
ARIA attributes are used as specified for the element's role
Deprecated ARIA roles were not used
`[aria-hidden="true"]` is not present on the document `<body>`
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Image elements have `[alt]` attributes
Links are distinguishable without relying on color.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
Skip links are focusable.
Touch targets have sufficient size and spacing.
Document has a main landmark.
Elements with `role="none"` or `role="presentation"` do not have conflicts
`[accesskey]` values are unique (not applicable)
`button`, `link`, and `menuitem` elements have accessible names (not applicable)
Elements with `role="dialog"` or `role="alertdialog"` have accessible names. (not applicable)
ARIA input fields have accessible names (not applicable)
ARIA `meter` elements have accessible names (not applicable)
ARIA `progressbar` elements have accessible names (not applicable)
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children. (not applicable)
`[role]`s are contained by their required parent element (not applicable)
Elements with the `role=text` attribute do not have focusable descendents. (not applicable)
ARIA toggle fields have accessible names (not applicable)
ARIA `tooltip` elements have accessible names (not applicable)
ARIA `treeitem` elements have accessible names (not applicable)
The page contains a heading, skip link, or landmark region (not applicable)
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements. (not applicable)
Definition list items are wrapped in `<dl>` elements (not applicable)
ARIA IDs are unique (not applicable)
No form fields have multiple labels (not applicable)
`<frame>` or `<iframe>` elements have a title (not applicable)
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute. (not applicable)
Input buttons have discernible text. (not applicable)
`<input type="image">` elements have `[alt]` text (not applicable)
Form elements have associated labels (not applicable)
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`). (not applicable)
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements (not applicable)
The document does not use `<meta http-equiv="refresh">` (not applicable)
`<object>` elements have alternate text (not applicable)
Select elements have associated label elements. (not applicable)
No element has a `[tabindex]` value greater than 0 (not applicable)
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table. (not applicable)
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe. (not applicable)
`[lang]` attributes have a valid value (not applicable)
`<video>` elements contain a `<track>` element with `[kind="captions"]` (not applicable)
`autocomplete` attributes are used correctly (not applicable)
SVG elements with an `img` role have an accessible text alternative (not applicable)
Tables have different content in the summary attribute and `<caption>`. (not applicable)
All heading elements contain content. (not applicable)
Uses ARIA roles only on compatible elements (not applicable)
Image elements do not have `[alt]` attributes that are redundant text. (not applicable)
Identical links have the same purpose. (not applicable)
Elements with visible text labels have matching accessible names. (not applicable)
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption. (not applicable)
`<td>` elements in a large `<table>` have one or more table headers. (not applicable)
Best Practices: 13 checks passed, 1 not applicable
Uses HTTPS
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Allows users to paste into input fields
Displays images with correct aspect ratio
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
Avoids deprecated APIs
Avoids third-party cookies
No browser errors logged to the console
Page has valid source maps
No issues in the `Issues` panel in Chrome Devtools
Redirects HTTP traffic to HTTPS (not applicable)
SEO: 9 checks passed
Page isn’t blocked from indexing
Document has a `<title>` element
Page has successful HTTP status code
Links have descriptive text
Links are crawlable
robots.txt is valid
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`
Agentic Browsing: 2 checks passed, 3 not applicable
Cumulative Layout Shift
llms.txt follows recommendations
WebMCP form coverage (not applicable)
WebMCP tools registered (not applicable)
WebMCP schemas are valid (not applicable)
Scanned
· Lighthouse 13.4.1
111111223
Boxes mark elements that failed a check. Hover or focus an element
in the lists below to highlight it here.
Accessibility — 3 failing checks
1Finding 1:
Links do not have a discernible name
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.
Fix all of the following:
Element is in tab order and does not have accessible text
Fix any of the following:
Element does not have text that is visible to screen readers
aria-label attribute does not exist or is empty
aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
Element has no title attribute
div.wpb_wrapper > div.nectar_icon_wrap > div.nectar_icon > a
Fix all of the following:
Element is in tab order and does not have accessible text
Fix any of the following:
Element does not have text that is visible to screen readers
aria-label attribute does not exist or is empty
aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
Element has no title attribute
div.wpb_wrapper > div.nectar_icon_wrap > div.nectar_icon > a
Fix all of the following:
Element is in tab order and does not have accessible text
Fix any of the following:
Element does not have text that is visible to screen readers
aria-label attribute does not exist or is empty
aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
Element has no title attribute
div.wpb_wrapper > div.nectar_icon_wrap > div.nectar_icon > a
Fix all of the following:
Element is in tab order and does not have accessible text
Fix any of the following:
Element does not have text that is visible to screen readers
aria-label attribute does not exist or is empty
aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
Element has no title attribute
div.wpb_wrapper > div.nectar_icon_wrap > div.nectar_icon > a
Fix all of the following:
Element is in tab order and does not have accessible text
Fix any of the following:
Element does not have text that is visible to screen readers
aria-label attribute does not exist or is empty
aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
Element has no title attribute
div.wpb_wrapper > div.nectar_icon_wrap > div.nectar_icon > a
Fix all of the following:
Element is in tab order and does not have accessible text
Fix any of the following:
Element does not have text that is visible to screen readers
aria-label attribute does not exist or is empty
aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
Element has no title attribute
2Finding 2:
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Fix any of the following:
Element has insufficient color contrast of 4.28 (foreground color: #e62525, background color: #f9f9f9, font size: 10.5pt (14px), font weight: normal). Expected contrast ratio of 4.5:1
Fix any of the following:
Element has insufficient color contrast of 3.05 (foreground color: #ffffff, background color: #ff5a5f, font size: 10.5pt (14px), font weight: normal). Expected contrast ratio of 4.5:1
3Finding 3:
Heading elements are not in a sequentially-descending order
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.
Measured in a simulated desktop environment. These are
readings, not checks — treat them as context for the performance
score rather than defects to close.
0.8 sFirst Contentful Paint
2.9 sLargest Contentful Paint
780 msTotal Blocking Time
0.057Cumulative Layout Shift
1.1 sSpeed Index
Performance — 13 opportunities
Font display
Consider setting `font-display` to `swap` or `optional` to ensure text is consistently visible. `swap` can be further optimized to mitigate layout shifts with font metric overrides.
A forced reflow occurs when JavaScript queries geometric properties (such as `offsetWidth`) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
