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.

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.

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]

items: [map[duration:1749.072998046875 label:Time to first byte subpart:timeToFirstByte] map[duration:167.158001953125 label:Resource load delay subpart:resourceLoadDelay] map[duration:405.172998046875 label:Resource load duration subpart:resourceLoadDuration] map[duration:189.107001953125 label:Element render delay subpart:elementRenderDelay]]

lhId: page-0-IMG

nodeLabel: Warrior Martial Arts

path: 1,HTML,1,BODY,0,HEADER,0,DIV,0,DIV,0,DIV,2,DIV,1,A,0,IMG

selector: div.d-flex > div.live-shortcode > a.custom-logo-link > img.custom-logo

snippet: <img width="200" height="56" src="https://warriorsuccesssystems.com/wp-content/uploads/2026/08/Warrior-Succe…" class="custom-logo" alt="Warrior Martial Arts" decoding="async">

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG

nodeLabel: Warrior Martial Arts

path: 1,HTML,1,BODY,0,HEADER,0,DIV,0,DIV,0,DIV,2,DIV,1,A,0,IMG

selector: div.d-flex > div.live-shortcode > a.custom-logo-link > img.custom-logo

snippet: <img width="200" height="56" src="https://warriorsuccesssystems.com/wp-content/uploads/2026/08/Warrior-Succe…" class="custom-logo" alt="Warrior Martial Arts" decoding="async">

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

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
warriorsuccesssystems.com/wp-includes/js/jquery/jquery.min.js?ver=3.7.1	29.9 KiB	629 ms
/wp-content/plugins/cleantalk-spam-protect/js/apbct-publi...	24.1 KiB	629 ms
warriorsuccesssystems.com/wp-includes/js/jquery/jquery-migrate.min.js?ver=3.4.1	5.0 KiB
/wp-content/plugins/livecanvas/modules/optin-extra-assets...	2.6 KiB
/wp-content/plugins/cleantalk-spam-protect/css/cleantalk-...	772 B
/wp-content/plugins/wp-store-locator/css/styles.min.css?v...	3.8 KiB
/wp-content/plugins/cleantalk-spam-protect/css/cleantalk-...	1.2 KiB
/wp-content/plugins/cleantalk-spam-protect/css/cleantalk-...	886 B
/css2?family=Bebas+Neue&family=Cinzel:wght@400;700;900&fa...	1.4 KiB	819 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.portrait-frame > div.portrait-placeholder > div.mt-3 > img.img-fluid `div.portrait-frame > div.portrait-placeholder > div.mt-3 > img.img-fluid`	/wp-content/uploads/2026/07/master-clark-one-finger-768x7...	49.0 KiB	42.4 KiB
Warrior Martial Arts `div.d-flex > div.live-shortcode > a.custom-logo-link > img.custom-logo`	/wp-content/uploads/2026/08/Warrior-Success-Systems-logo-...	9.2 KiB	7.4 KiB

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

Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 967 ms

URL	Time Spent
warriorsuccesssystems.com/	1.1 s

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: 0.0 ms 61.2 KiB

URL	Transfer Size	Est Savings
/wp-content/themes/picostrap5-child-base/css-output/bundl...	63.2 KiB	61.2 KiB

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

●Use efficient cache lifetimes

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●Modern HTTP

●Optimize viewport for mobile

●Max Potential First Input Delay 50 ms

●Minify CSS

●Minify JavaScript

●Reduce unused JavaScript

●Avoids enormous network payloads Total size was 594 KiB

●JavaScript execution time 0.2 s

●Minimizes main-thread work 1.6 s

●Avoid long main-thread tasks 4 long tasks found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 160 ms

●Server Backend Latencies 280 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

○INP breakdown

○User Timing marks and measures

○Avoid non-composited animations

○Avoid large layout shifts

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.

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
SUMMIT `body.home > main#theme-main > section#events > div.events-bg-text`

These are opportunities to improve the legibility of your content.

Names and labels

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.portrait-frame > div.portrait-placeholder > div.mt-3 > img.img-fluid `div.portrait-frame > div.portrait-placeholder > div.mt-3 > img.img-fluid`
div.row > div.col-lg-10 > div.lc-block > img.img-fluid `div.row > div.col-lg-10 > div.lc-block > img.img-fluid`

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.fixed-top > div.container-fluid > div.d-flex > a.navbar-brand `div.fixed-top > div.container-fluid > div.d-flex > a.navbar-brand`
div.container-fluid > div.d-flex > div.live-shortcode > a.navbar-brand `div.container-fluid > div.d-flex > div.live-shortcode > a.navbar-brand`
div.container-fluid > div.d-flex > div.live-shortcode > a.btn `div.container-fluid > div.d-flex > div.live-shortcode > a.btn`

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.

○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 have valid values

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

●Buttons have an accessible name

●Form elements have associated labels

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

●Select elements have associated label elements.

●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

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

●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 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

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

○Links are distinguishable without relying on color.

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

○`<object>` elements have alternate text

○Skip links are focusable.

○No element has a `[tabindex]` value greater than 0

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

100

Best Practices

●Uses HTTPS

●Avoids deprecated APIs

●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 clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

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.

Content Best Practices

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destination	Link Text
cp.mystudio.io/e/?=9047242100/3207/838615//1784744491	LEARN MORE
warriorsuccesssystems.com/warrior-leadership-framework/	LEARN MORE
warriorsuccesssystems.com/school-growth-playbook/	LEARN MORE
warriorsuccesssystems.com/videos/	LEARN MORE
warriorsuccesssystems.com/gallery/	LEARN MORE
warriorsuccesssystems.com/warrior-fitness-programming-guide/	LEARN MORE
warriorsuccesssystems.com/warrior-insights-blog/	LEARN MORE
warriorsuccesssystems.com/inner-circle-previews/	LEARN MORE

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.portrait-frame > div.portrait-placeholder > div.mt-3 > img.img-fluid `div.portrait-frame > div.portrait-placeholder > div.mt-3 > img.img-fluid`
div.row > div.col-lg-10 > div.lc-block > img.img-fluid `div.row > div.col-lg-10 > div.lc-block > img.img-fluid`

Format your HTML in a way that enables crawlers to better understand your app’s content.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Page has successful HTTP status code

●Links are crawlable

●robots.txt is valid

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`