PCC · Site audit

Prepared by PXP — opens pxp.dev in a new tab

All pages

Iosepa Voyaging Canoe

https://www.polynesia.com/iosepa-canoe-voyage , opens in a new tab

Scores

Performance
34 mobile
70 desktop
Accessibility
66 mobile
67 desktop
Best Practices
50 mobile
54 desktop
SEO
85 mobile
85 desktop

Findings

Full-page screenshot of Iosepa Voyaging Canoe as rendered during the mobile scan.
Boxes mark elements that failed a check. Hover or focus an element in the lists below to highlight it here.

Accessibility — 9 failing checks

Finding 1: `[aria-*]` attributes do not match their roles

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.

critical weight 10 1 element How to fix , opens in a new tab

Show the 1 element at fault
  • div#dropdownMenus > div.mobile-top > div.mobile-top__search-container > div#nav-search-bar 
    <div aria-expanded="true" class="search-bar search-bar--mobile" id="nav-search-bar">

    Fix all of the following: ARIA attribute is not allowed: aria-expanded="true"

Finding 2: Elements with an ARIA `[role]` that require children to contain a specific `[role]` are missing some or all of those required children.

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

critical weight 10 1 element How to fix , opens in a new tab

Show the 1 element at fault
  • div.footer__row-flex > div.medium-8 > div.row > ul.accordion 
    <ul class="accordion footer__accordion" data-accordion="e67ntq-accordion" data-allow-all-closed="true" role="tablist">

    Fix any of the following: Element has children which are not allowed: li

Finding 3: `[role]`s are not contained by their required parent element

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

critical weight 10 1 element How to fix , opens in a new tab

Show the 1 element at fault
  • div.row > ul.accordion > li.accordion-item > a#aokkqr-accordion-label 
    <a class="accordion-title footer__accordion-title" href="#" aria-controls="aokkqr-accordion" role="tab" id="aokkqr-accordion-label" aria-expanded="false" aria-selected="false">

    Fix any of the following: Required ARIA parent role not present: tablist

Finding 4: Image elements do not have `[alt]` attributes

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

critical weight 10 1 element How to fix , opens in a new tab

Show the 1 element at fault
  • li.primary-nav-menu-dropdowns__title > div.primary-nav-menu-dropdowns__menuItem > div.primary-nav-menu-dropdowns__menuIcon > img 
    <img src="data:image/svg+xml,%3Csvg height='6.69' width='11' viewBox='0 0 11 6.69' x…">

    Fix any of the following: Element does not have an alt attribute 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 Element's default semantics were not overridden with role="none" or role="presentation"

Finding 5: Form elements do not have associated labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

critical weight 10 1 element How to fix , opens in a new tab

Show the 1 element at fault
  • div#nav-search-bar > div.search-bar__container > form#searchform > input#search-input 
    <input class="search-bar__input-box search-bar__input-box--mobile" id="search-input" name="s" type="text" value="">

    Fix all of the following: Form element has explicit <label> that is hidden

Finding 6: Touch targets do not have sufficient size or spacing.

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.

serious weight 7 15 elements How to fix , opens in a new tab

Show the 15 elements at fault
  • div#splide01 > ul.splide__pagination > li > button.splide__pagination__page 
    <button class="splide__pagination__page" type="button" aria-controls="splide01-slide01" aria-label="Go to slide 1">

    Fix any of the following: Target has insufficient size (8px by 8px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 4px instead of at least 24px.

  • div#splide01 > ul.splide__pagination > li > button.splide__pagination__page 
    <button class="splide__pagination__page" type="button" aria-controls="splide01-slide02" aria-label="Go to slide 2">

    Fix any of the following: Target has insufficient size (8px by 8px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 4px instead of at least 24px.

  • div#splide01 > ul.splide__pagination > li > button.splide__pagination__page 
    <button class="splide__pagination__page" type="button" aria-controls="splide01-slide03" aria-label="Go to slide 3">

    Fix any of the following: Target has insufficient size (8px by 8px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 4px instead of at least 24px.

  • div#splide01 > ul.splide__pagination > li > button.splide__pagination__page 
    <button class="splide__pagination__page" type="button" aria-controls="splide01-slide04" aria-label="Go to slide 4">

    Fix any of the following: Target has insufficient size (8px by 8px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 4px instead of at least 24px.

  • div#splide01 > ul.splide__pagination > li > button.splide__pagination__page 
    <button class="splide__pagination__page" type="button" aria-controls="splide01-slide05" aria-label="Go to slide 5">

    Fix any of the following: Target has insufficient size (8px by 8px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 4px instead of at least 24px.

  • div#splide01 > ul.splide__pagination > li > button.splide__pagination__page 
    <button class="splide__pagination__page" type="button" aria-controls="splide01-slide06" aria-label="Go to slide 6">

    Fix any of the following: Target has insufficient size (8px by 8px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 4px instead of at least 24px.

  • div#splide01 > ul.splide__pagination > li > button.splide__pagination__page 
    <button class="splide__pagination__page is-active" type="button" aria-controls="splide01-slide07" aria-label="Go to slide 7" aria-current="true">

    Fix any of the following: Target has insufficient size (11.2px by 11.2px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 4px instead of at least 24px.

  • div#splide01 > ul.splide__pagination > li > button.splide__pagination__page 
    <button class="splide__pagination__page" type="button" aria-controls="splide01-slide08" aria-label="Go to slide 8">

    Fix any of the following: Target has insufficient size (8px by 8px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 4px instead of at least 24px.

  • div#splide01 > ul.splide__pagination > li > button.splide__pagination__page 
    <button class="splide__pagination__page" type="button" aria-controls="splide01-slide09" aria-label="Go to slide 9">

    Fix any of the following: Target has insufficient size (8px by 8px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 4px instead of at least 24px.

  • div#splide01 > ul.splide__pagination > li > button.splide__pagination__page 
    <button class="splide__pagination__page" type="button" aria-controls="splide01-slide10" aria-label="Go to slide 10">

    Fix any of the following: Target has insufficient size (8px by 8px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 4px instead of at least 24px.

  • div#splide01 > ul.splide__pagination > li > button.splide__pagination__page 
    <button class="splide__pagination__page" type="button" aria-controls="splide01-slide11" aria-label="Go to slide 11">

    Fix any of the following: Target has insufficient size (8px by 8px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 4px instead of at least 24px.

  • div#splide01 > ul.splide__pagination > li > button.splide__pagination__page 
    <button class="splide__pagination__page" type="button" aria-controls="splide01-slide12" aria-label="Go to slide 12">

    Fix any of the following: Target has insufficient size (8px by 8px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 4px instead of at least 24px.

  • div#splide01 > ul.splide__pagination > li > button.splide__pagination__page 
    <button class="splide__pagination__page" type="button" aria-controls="splide01-slide13" aria-label="Go to slide 13">

    Fix any of the following: Target has insufficient size (8px by 8px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 4px instead of at least 24px.

  • div#splide01 > ul.splide__pagination > li > button.splide__pagination__page 
    <button class="splide__pagination__page" type="button" aria-controls="splide01-slide14" aria-label="Go to slide 14">

    Fix any of the following: Target has insufficient size (8px by 8px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 4px instead of at least 24px.

  • div#splide01 > ul.splide__pagination > li > button.splide__pagination__page 
    <button class="splide__pagination__page" type="button" aria-controls="splide01-slide15" aria-label="Go to slide 15">

    Fix any of the following: Target has insufficient size (8px by 8px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 4px instead of at least 24px.

Finding 7: 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.

serious weight 7 3 elements How to fix , opens in a new tab

Show the 3 elements at fault
  • div.primary-nav-menu__advert > a > div.primary-nav-menu-advert > p.primary-nav-menu-advert__header 
    <p class="primary-nav-menu-advert__header">

    Fix any of the following: Element has insufficient color contrast of 2.94 (foreground color: #ffffff, background color: #f46e39, font size: 11.3pt (15px), font weight: normal). Expected contrast ratio of 4.5:1

  • div.primary-nav-menu__advert > a > div.primary-nav-menu-advert > p.primary-nav-menu-advert__sub-header 
    <p class="primary-nav-menu-advert__sub-header">

    Fix any of the following: Element has insufficient color contrast of 2.94 (foreground color: #ffffff, background color: #f46e39, font size: 8.3pt (11px), font weight: bold). Expected contrast ratio of 4.5:1

  • div.rich-content-block__container > div.rich-content-block__item > p > a.button 
    <a class="button button__orange" href="/packages">

    Fix any of the following: Element has insufficient color contrast of 2.97 (foreground color: #ffffff, background color: #f16e42, font size: 10.8pt (14.4px), font weight: normal). Expected contrast ratio of 4.5:1

Finding 8: 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.

serious weight 7 3 elements How to fix , opens in a new tab

Show the 3 elements at fault
  • li > ul.primary-nav-menu-dropdowns-subMenu > li.primary-nav-menu-dropdowns-subMenu__item > a 
    <a href="https://apps.apple.com/us/app/polynesian-cultural-center/id6467809333">

    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

  • li > ul.primary-nav-menu-dropdowns-subMenu > li.primary-nav-menu-dropdowns-subMenu__item > a 
    <a href="https://play.google.com/store/apps/details?id=com.thechurchmobileapp">

    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.row > ul.footer__icons > li.footer__icons-brand > a 
    <a target="_blank" href="https://www.thehawaiistore.com/">

    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

Finding 9: List items (`<li>`) are not contained within `<ul>`, `<ol>` or `<menu>` parent elements.

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

serious weight 7 3 elements How to fix , opens in a new tab

Show the 3 elements at fault
  • div.medium-8 > div.row > ul.accordion > li.accordion-item 
    <li class="accordion-item columns footer__accordion-item medium-4" data-accordion-item="">

    Fix any of the following: List item parent element has a role that is not role="list"

  • div.medium-8 > div.row > ul.accordion > li.accordion-item 
    <li class="accordion-item columns footer__accordion-item medium-3" data-accordion-item="">

    Fix any of the following: List item parent element has a role that is not role="list"

  • div.medium-8 > div.row > ul.accordion > li.accordion-item 
    <li class="accordion-item columns footer__accordion-item medium-5" data-accordion-item="">

    Fix any of the following: List item parent element has a role that is not role="list"

Best Practices — 5 failing checks

Finding 10: Uses deprecated APIs

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

unrated weight 5 1 warning found 0 elements How to fix , opens in a new tab

Finding 11: Uses third-party cookies

Third-party cookies may be blocked in some contexts. Learn more about preparing for third-party cookie restrictions.

unrated weight 5 1 cookie found 0 elements How to fix , opens in a new tab

Finding 12: Serves images with low resolution

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.

unrated weight 1 1 element How to fix , opens in a new tab

Show the 1 element at fault
  • div.primary-nav-menu__container > div.primary-nav-menu__mobile-menu > div.primary-nav-menu__mobile-menu-container > img.lazy-skip 
    <img alt="menu" class="lazy-skip" src="/static/images/menu__mobileHamburger.png" width="21" height="14">

Finding 13: Browser errors were logged to the console

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

unrated weight 1 0 elements How to fix , opens in a new tab

Finding 14: Issues were logged in the `Issues` panel in Chrome Devtools

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

unrated weight 1 0 elements

SEO — 2 failing checks

Finding 15: Image elements do not have `[alt]` attributes

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

critical weight 1 1 element How to fix , opens in a new tab

Show the 1 element at fault
  • li.primary-nav-menu-dropdowns__title > div.primary-nav-menu-dropdowns__menuItem > div.primary-nav-menu-dropdowns__menuIcon > img 
    <img src="data:image/svg+xml,%3Csvg height='6.69' width='11' viewBox='0 0 11 6.69' x…">

    Fix any of the following: Element does not have an alt attribute 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 Element's default semantics were not overridden with role="none" or role="presentation"

Finding 16: Links are not crawlable

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

unrated weight 1 3 elements How to fix , opens in a new tab

Show the 3 elements at fault
  • body > div#localize-widget > div#localize-widget-langs > a 
    <a data-lang="ja" style="color: rgb(255,255,255) !important;">
  • body > div#localize-widget > div#localize-widget-langs > a 
    <a data-lang="ko" style="color: rgb(255,255,255) !important;">
  • body > div#localize-widget > div#localize-widget-langs > a 
    <a data-lang="zh-Hans" style="color: rgb(255,255,255) !important;">

Lab metrics

Measured in a simulated mobile environment. These are readings, not checks — treat them as context for the performance score rather than defects to close.

12.0 s First Contentful Paint
29.0 s Largest Contentful Paint
950 ms Total Blocking Time
0.011 Cumulative Layout Shift
13.3 s Speed Index

Performance — 18 opportunities

Avoid enormous network payloads

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Total size was 10,956 KiB score 50 How to fix , opens in a new tab

Duplicated JavaScript

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Est savings of 134 KiB score 0 How to fix , opens in a new tab

Forced reflow

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.

score 0 How to fix , opens in a new tab

Image elements do not have explicit `width` and `height`

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

score 50 How to fix , opens in a new tab

Improve image delivery

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Est savings of 986 KiB score 0 How to fix , opens in a new tab

LCP request discovery

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

score 0 How to fix , opens in a new tab

Legacy JavaScript

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

Est savings of 54 KiB score 0 How to fix , opens in a new tab

Max Potential First Input Delay

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.

310 ms score 33 How to fix , opens in a new tab

Minify CSS

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Est savings of 17 KiB score 50 How to fix , opens in a new tab

Minify JavaScript

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Est savings of 239 KiB score 0 How to fix , opens in a new tab

Minimize main-thread work

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

6.7 s score 0 How to fix , opens in a new tab

Network dependency tree

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.

score 0 How to fix , opens in a new tab

Reduce JavaScript execution time

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

4.3 s score 0 How to fix , opens in a new tab

Reduce unused CSS

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.

Est savings of 150 KiB score 0 How to fix , opens in a new tab

Reduce unused JavaScript

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Est savings of 2,259 KiB score 0 How to fix , opens in a new tab

Render-blocking requests

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Est savings of 8,930 ms score 0 How to fix , opens in a new tab

Time to Interactive

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

39.9 s score 0 How to fix , opens in a new tab

Use efficient cache lifetimes

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Est savings of 960 KiB score 0 How to fix , opens in a new tab

Performance: 5 checks passed, 1 not applicable
  • Document request latency
  • Font display
  • Optimize viewport for mobile
  • Avoid multiple page redirects
  • Initial server response time was short
  • INP breakdown (not applicable)
Accessibility: 21 checks passed, 34 not applicable
  • 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
  • `<frame>` or `<iframe>` elements have a title
  • Heading elements appear in a sequentially-descending order
  • `<html>` element has a `[lang]` attribute
  • `<html>` element has a valid value for its `[lang]` attribute
  • Input buttons have discernible text.
  • Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
  • `[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
  • No element has a `[tabindex]` value greater than 0
  • 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 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)
  • No form fields have multiple labels (not applicable)
  • `<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute. (not applicable)
  • `<input type="image">` elements have `[alt]` text (not applicable)
  • Links are distinguishable without relying on color. (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)
  • Skip links are focusable. (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)
  • 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: 8 checks passed, 2 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
  • Page has the HTML doctype
  • Properly defines charset
  • Page has valid source maps
  • Redirects HTTP traffic to HTTPS (not applicable)
  • Mitigate clickjacking with XFO or CSP (not applicable)
SEO: 8 checks passed
  • Page isn’t blocked from indexing
  • Document has a `<title>` element
  • Document has a meta description
  • Page has successful HTTP status code
  • Links have descriptive text
  • robots.txt is valid
  • Document has a valid `hreflang`
  • Document has a valid `rel=canonical`

Scanned · Lighthouse 13.4.1