Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
/js/sharethis.js?ver=2.3.8	600.0 s	46.9 KiB
www.google-analytics.com/analytics.js	7200.0 s	20.9 KiB
/cdn-cgi/challenge-platform/h/b/scripts/jsd/0b8fb825cb67/...	14400.0 s	12.4 KiB
buttons-config.sharethis.com/js/6449816e7cd8060012f2aa97.js	60.0 s	1.4 KiB
platform-cdn.sharethis.com/img/twitter.svg	0.0 ms	822 B
/v2.0/get_counts?cb=window.__sharethis__.cb&url=https%3A%...	10800.0 s	869 B

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.

title: Preconnected origins

value: no origins were preconnected

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

value: No additional origins are good candidates for preconnecting

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
www.oasis-open.org/wp-includes/css/dist/components/style.min.css?ver=6.9.4	15.0 KiB	300 ms
www.oasis-open.org/wp-includes/css/dist/block-editor/style.min.css?ver=6.9.4	16.9 KiB	150 ms
www.oasis-open.org/wp-includes/js/jquery/jquery.min.js?ver=3.7.1	31.1 KiB	450 ms
www.oasis-open.org/wp-includes/css/dashicons.min.css?ver=6.9.4	34.7 KiB	150 ms
/wp-content/themes/oasis-2020/build/style-8842b748cf3b4c1...	21.7 KiB	150 ms
/wp-content/plugins/save-as-pdf-by-pdfcrowd/public/css/sa...	754 B
/wp-content/plugins/gutentor/dist/blocks.style.build.css?...	27.0 KiB	150 ms
/wp-content/plugins/save-as-pdf-by-pdfcrowd/public/css/sa...	965 B
www.oasis-open.org/wp-includes/js/jquery/jquery-migrate.min.js?ver=3.4.1	5.2 KiB
www.oasis-open.org/wp-includes/css/dist/editor/style.min.css?ver=6.9.4	10.5 KiB	300 ms
www.oasis-open.org/wp-includes/css/dist/reusable-blocks/style.min.css?ver=6.9.4	556 B
/wp-content/plugins/save-as-pdf-by-pdfcrowd/public/css/sa...	730 B
/wp-content/plugins/save-as-pdf-by-pdfcrowd/public/js/sav...	1.1 KiB
www.oasis-open.org/wp-includes/css/dist/preferences/style.min.css?ver=6.9.4	759 B
/wp-content/plugins/save-as-pdf-by-pdfcrowd/public/js/sav...	1.0 KiB
www.oasis-open.org/wp-includes/js/underscore.min.js?ver=1.13.7	7.7 KiB
/wp-content/plugins/gutentor/assets/library/wpness-grid/w...	3.6 KiB	150 ms
/wp-content/plugins/save-as-pdf-by-pdfcrowd/public/js/sav...	2.2 KiB
/wp-content/plugins/sharethis-share-buttons/css/mu-style....	454 B
www.oasis-open.org/wp-includes/css/dist/patterns/style.min.css?ver=6.9.4	1.0 KiB	150 ms
/wp-content/plugins/gutentor/assets/library/fontawesome/c...	12.5 KiB
/wp-content/plugins/contact-form-7/includes/css/styles.cs...	1.3 KiB	150 ms
/wp-content/uploads/pum/pum-site-styles.css?generated=175...	3.8 KiB
/wp-content/plugins/gutentor/assets/library/animatecss/an...	4.8 KiB
/css2?family=Poppins%3Aital%2Cwght%400%2C400%3B0%2C500%3B...	1.1 KiB	832 ms
/js/sharethis.js?ver=2.3.8	46.9 KiB	1.2 s
fonts.googleapis.com/css?family=Montserrat:100	658 B	176 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
div.wp-block-column > figure.wp-block-image > a > img.wp-image-12391 `div.wp-block-column > figure.wp-block-image > a > img.wp-image-12391`	www.oasis-open.org/wp-content/uploads/2024/12/DAD-CDM-rotating-banner.png	147.0 KiB	90.7 KiB
div.wp-block-column > figure.wp-block-image > a > img.wp-image-13360 `div.wp-block-column > figure.wp-block-image > a > img.wp-image-13360`	www.oasis-open.org/wp-content/uploads/2025/11/OEMF-rotating-banner.png	75.1 KiB	46.3 KiB
div.wp-block-column > figure.wp-block-image > a > img.wp-image-11887 `div.wp-block-column > figure.wp-block-image > a > img.wp-image-11887`	www.oasis-open.org/wp-content/uploads/2024/08/CoSAI-rotating-banner-1.png	73.1 KiB	45.1 KiB
div.wp-block-column > figure.wp-block-image > a > img.wp-image-12724 `div.wp-block-column > figure.wp-block-image > a > img.wp-image-12724`	www.oasis-open.org/wp-content/uploads/2025/03/DPS-rotating-banner.png	68.0 KiB	42.0 KiB
div.wp-block-image > figure.aligncenter > a > img.wp-image-5568 `div.wp-block-image > figure.aligncenter > a > img.wp-image-5568`	www.oasis-open.org/wp-content/uploads/2020/11/not-for-profit@2x-150x150-1.png	12.4 KiB	8.8 KiB
div.wp-block-image > figure.aligncenter > a > img.wp-image-5571 `div.wp-block-image > figure.aligncenter > a > img.wp-image-5571`	www.oasis-open.org/wp-content/uploads/2020/11/collaborative@2x-150x150-1.png	11.9 KiB	8.2 KiB

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.4 s

URL	Time Spent
oasis-open.org/	1.4 s
www.oasis-open.org/	0.0 ms

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 840 ms 131.9 KiB

URL	Transfer Size	Est Savings
www.oasis-open.org/wp-includes/css/dashicons.min.css?ver=6.9.4	34.4 KiB	34.1 KiB
/wp-content/plugins/gutentor/dist/blocks.style.build.css?...	26.6 KiB	26.6 KiB
/wp-content/themes/oasis-2020/build/style-8842b748cf3b4c1...	21.4 KiB	17.7 KiB
www.oasis-open.org/wp-includes/css/dist/block-editor/style.min.css?ver=6.9.4	16.6 KiB	16.6 KiB
www.oasis-open.org/wp-includes/css/dist/components/style.min.css?ver=6.9.4	14.6 KiB	14.6 KiB
/wp-content/plugins/gutentor/assets/library/fontawesome/c...	12.2 KiB	12.2 KiB
www.oasis-open.org/wp-includes/css/dist/editor/style.min.css?ver=6.9.4	10.2 KiB	10.1 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 19.4 KiB

URL	Transfer Size	Est Savings
platform-api.sharethis.com/js/sharethis.js?ver=2.3.8	46.4 KiB	13.9 KiB
www.oasis-open.org/wp-content/plugins/gutentor/assets/js/gutentor.js?ver=3.5.1	12.8 KiB	5.6 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 171.3 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=GT-W62J3VD	155.4 KiB	65.7 KiB
www.googletagmanager.com/gtag/js?id=UA-35180637-1&ver=6.9.4	115.5 KiB	64.7 KiB
/wp-content/themes/oasis-2020/build/frontend-96934effb79b...	29.9 KiB	20.9 KiB
platform-api.sharethis.com/js/sharethis.js?ver=2.3.8	46.3 KiB	20.1 KiB

More information about the performance of your application. These numbers don't directly affect the Performance score.

●Max Potential First Input Delay 130 ms

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Avoids enormous network payloads Total size was 1,143 KiB

●User Timing marks and measures 5 user timings

●JavaScript execution time 0.9 s

●Minimizes main-thread work 1.9 s

●Avoid long main-thread tasks 6 long tasks found

●Image elements have explicit `width` and `height`

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 30 ms

●Server Backend Latencies 610 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 30 ms

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

○LCP request discovery

○Avoid non-composited animations

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

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Search `div#page > header#masthead > div.site-header__wrap > button.search-toggle`

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.

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
A community for everyone. `div.content__body > div.wp-block-columns > div.wp-block-column > h4#h-a-community-for-everyone`
Useful links `footer#colophon > div.site-footer__wrap > nav#useful-links > h6`

These are opportunities to improve keyboard navigation in your application.

Names and labels

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.wp-block-column > div.wp-block-image > figure.aligncenter > a `div.wp-block-column > div.wp-block-image > figure.aligncenter > a`
div.wp-block-column > div.wp-block-image > figure.aligncenter > a `div.wp-block-column > div.wp-block-image > figure.aligncenter > a`
div.wp-block-column > div.wp-block-image > figure.aligncenter > a `div.wp-block-column > div.wp-block-image > figure.aligncenter > a`
div.wp-block-columns > div.wp-block-column > figure.wp-block-image > a `div.wp-block-columns > div.wp-block-column > figure.wp-block-image > a`
div.wp-block-columns > div.wp-block-column > figure.wp-block-image > a `div.wp-block-columns > div.wp-block-column > figure.wp-block-image > a`
div.wp-block-columns > div.wp-block-column > figure.wp-block-image > a `div.wp-block-columns > div.wp-block-column > figure.wp-block-image > a`
div.wp-block-columns > div.wp-block-column > figure.wp-block-image > a `div.wp-block-columns > div.wp-block-column > figure.wp-block-image > a`
nav.sponsors > ul.sponsors__list > li.sponsors__list-item > a.sponsor__link `nav.sponsors > ul.sponsors__list > li.sponsors__list-item > a.sponsor__link`
nav.sponsors > ul.sponsors__list > li.sponsors__list-item > a.sponsor__link `nav.sponsors > ul.sponsors__list > li.sponsors__list-item > a.sponsor__link`
nav.sponsors > ul.sponsors__list > li.sponsors__list-item > a.sponsor__link `nav.sponsors > ul.sponsors__list > li.sponsors__list-item > a.sponsor__link`
nav.sponsors > ul.sponsors__list > li.sponsors__list-item > a.sponsor__link `nav.sponsors > ul.sponsors__list > li.sponsors__list-item > a.sponsor__link`
nav.sponsors > ul.sponsors__list > li.sponsors__list-item > a.sponsor__link `nav.sponsors > ul.sponsors__list > li.sponsors__list-item > a.sponsor__link`
nav.sponsors > ul.sponsors__list > li.sponsors__list-item > a.sponsor__link `nav.sponsors > ul.sponsors__list > li.sponsors__list-item > a.sponsor__link`

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.

Best practices

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
< `div#carousel > div.btn-bar > div#buttons > a#prev`
> `div#carousel > div.btn-bar > div#buttons > a#next`
Partner Event `div.wp-block-column > section.wp-block-posts-list > article.wp-block-posts-list__post > a.primary-category`

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-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●ARIA attributes are used as specified for the element's role

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●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

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○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

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<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

○Form elements have associated labels

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○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.

○Elements with visible text labels have matching accessible names.

○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.

Best Practices

General

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / Warning	Source
SharedStorage	www.oasis-open.org/cdn-cgi/challenge-platform/scripts/jsd/main.js
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.	www.oasis-open.org/cdn-cgi/challenge-platform/scripts/jsd/main.js
Fledge	www.oasis-open.org/cdn-cgi/challenge-platform/scripts/jsd/main.js

●Uses HTTPS

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

100

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

○Structured data is valid

●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

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`