Boxes mark elements that failed a check. Hover or focus an element
in the lists below to highlight it here.
Accessibility — 10 failing checks
1Finding 1:
`[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.
Fix any of the following:
Required ARIA parent role not present: tablist
2Finding 2:
`[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.
Fix all of the following:
ARIA attribute is not allowed: aria-expanded="true"
3Finding 3:
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.
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: bold). Expected contrast ratio of 4.5:1
Fix any of the following:
Element has insufficient color contrast of 2.12 (foreground color: #00a0b6, background color: #afddde, font size: 13.5pt (18px), font weight: bold). Expected contrast ratio of 4.5:1
Fix any of the following:
Element has insufficient color contrast of 3.1 (foreground color: #00a0b6, background color: #fefefe, font size: 13.5pt (18px), font weight: bold). Expected contrast ratio of 4.5:1
Fix any of the following:
Element has insufficient color contrast of 3.1 (foreground color: #00a0b6, background color: #fefefe, font size: 13.5pt (18px), font weight: bold). Expected contrast ratio of 4.5:1
Fix any of the following:
Element has insufficient color contrast of 3.1 (foreground color: #00a0b6, background color: #fefefe, font size: 13.5pt (18px), font weight: bold). Expected contrast ratio of 4.5:1
6Finding 6:
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.
Fix any of the following:
List item parent element has a role that is not role="list"
7Finding 7:
Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
Fix all of the following:
List element has direct children that are not allowed: h3
8Finding 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.
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
9Finding 9:
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.
Fix all of the following:
Document does not have a main landmark
Best Practices — 3 failing checks
11Finding 11:
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.
12Finding 12:
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
13Finding 13:
Missing source maps for large first-party JavaScript
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
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
Measured in a simulated mobile environment. These are
readings, not checks — treat them as context for the performance
score rather than defects to close.
11.1 sFirst Contentful Paint
25.1 sLargest Contentful Paint
730 msTotal Blocking Time
0.102Cumulative Layout Shift
11.1 sSpeed Index
Performance — 22 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.
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
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.
Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.
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.
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.
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: 16 checks passed, 39 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
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.
Touch targets have sufficient size and spacing.
`[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)
Buttons have an accessible name (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)
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)
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)
Elements with `role="none"` or `role="presentation"` do not have conflicts (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: 10 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
Page has the HTML doctype
Properly defines charset
Avoids deprecated APIs
Avoids third-party cookies
No issues in the `Issues` panel in Chrome Devtools
Redirects HTTP traffic to HTTPS (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
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Scanned
· Lighthouse 13.4.1
· resolved to https://polynesia.jp/educational-resources/
111444444555666710
Boxes mark elements that failed a check. Hover or focus an element
in the lists below to highlight it here.
Accessibility — 7 failing checks
1Finding 1:
`[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.
Fix any of the following:
Required ARIA parent role not present: tablist
2Finding 2:
`[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.
Fix all of the following:
ARIA attribute is not allowed: aria-expanded="true"
3Finding 3:
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.
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: 18.0pt (24px), font weight: bold). Expected contrast ratio of 3:1
Fix any of the following:
Element has insufficient color contrast of 2.14 (foreground color: #f19f45, background color: #ffffff, font size: 54.0pt (72px), font weight: bold). Expected contrast ratio of 3:1
Fix any of the following:
Element has insufficient color contrast of 2.12 (foreground color: #00a0b6, background color: #afddde, font size: 13.5pt (18px), font weight: bold). Expected contrast ratio of 4.5:1
Fix any of the following:
Element has insufficient color contrast of 3.1 (foreground color: #00a0b6, background color: #fefefe, font size: 13.5pt (18px), font weight: bold). Expected contrast ratio of 4.5:1
Fix any of the following:
Element has insufficient color contrast of 3.1 (foreground color: #00a0b6, background color: #fefefe, font size: 13.5pt (18px), font weight: bold). Expected contrast ratio of 4.5:1
Fix any of the following:
Element has insufficient color contrast of 3.1 (foreground color: #00a0b6, background color: #fefefe, font size: 13.5pt (18px), font weight: bold). Expected contrast ratio of 4.5:1
5Finding 5:
`[aria-hidden="true"]` elements contain focusable descendents
Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.
Fix all of the following:
Focusable content should have tabindex="-1" or be removed from the DOM
6Finding 6:
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.
Fix all of the following:
Document does not have a main landmark
Best Practices — 2 failing checks
8Finding 8:
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
9Finding 9:
Missing source maps for large first-party JavaScript
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
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
Measured in a simulated desktop environment. These are
readings, not checks — treat them as context for the performance
score rather than defects to close.
1.7 sFirst Contentful Paint
3.1 sLargest Contentful Paint
210 msTotal Blocking Time
0.001Cumulative Layout Shift
1.8 sSpeed 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.
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
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
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.
