Skip to content
https://lylaslegacy.org

Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

59

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.

RequestCache TTLTransfer Size
/wp-content/cache/wpo-minify/1789001004/assets/wpo-minify...0.0 ms243.8 KiB
lylaslegacy.org/wp-content/uploads/2026/08/home-page-hero-graphic-2-1024x564.png0.0 ms222.1 KiB
/wp-content/cache/wpo-minify/1789001004/assets/wpo-minify...0.0 ms147.8 KiB
/wp-content/cache/wpo-minify/1789001004/assets/wpo-minify...0.0 ms133.0 KiB
/wp-content/cache/wpo-minify/1789001004/assets/wpo-minify...0.0 ms99.0 KiB
/wp-content/uploads/2026/07/672446677_10240960292454386_4...0.0 ms81.7 KiB
/wp-content/cache/wpo-minify/1789001004/assets/wpo-minify...0.0 ms67.0 KiB
/wp-content/uploads/elementor/google-fonts/fonts/roboto-f...0.0 ms39.4 KiB
/wp-content/uploads/elementor/google-fonts/fonts/cormoran...0.0 ms37.0 KiB
/wp-content/uploads/elementor/google-fonts/fonts/petitfor...0.0 ms27.7 KiB
/wp-content/uploads/elementor/google-fonts/fonts/lato-f09...0.0 ms24.1 KiB
/wp-content/uploads/elementor/google-fonts/fonts/lato-cc8...0.0 ms24.1 KiB
/wp-content/uploads/elementor/google-fonts/fonts/lato-702...0.0 ms23.3 KiB
/wp-content/uploads/elementor/google-fonts/fonts/lato-b0c...0.0 ms22.7 KiB
lylaslegacy.org/wp-content/uploads/2025/08/Transparent-LL-Logo.png.webp0.0 ms19.7 KiB
/wp-content/cache/wpo-minify/1789001004/assets/wpo-minify...0.0 ms18.5 KiB
/wp-content/cache/wpo-minify/1789001004/assets/wpo-minify...0.0 ms17.9 KiB
/wp-content/plugins/elementor/assets/js/shared-frontend-h...0.0 ms8.5 KiB
/wp-content/cache/wpo-minify/1789001004/assets/wpo-minify...0.0 ms1.8 KiB
/wp-content/plugins/elementor/assets/js/text-editor.45609...0.0 ms1.6 KiB
/wp-content/cache/wpo-minify/1789001004/assets/wpo-minify...0.0 ms1.1 KiB

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.

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.

URLResource SizeEst Savings
Building Belonging Changing Lives Providing life-saving safety equipment and m… main#content > div.page-content > div.elementor > div.elementor-element
lylaslegacy.org/wp-content/uploads/2026/08/home-page-hero-graphic-2-1024x564.png221.9 KiB127.9 KiB
div.e-con-inner > div.elementor-element > div.elementor-element > img.attachment-1536x1536 div.e-con-inner > div.elementor-element > div.elementor-element > img.attachment-1536x1536
/wp-content/uploads/2026/07/672446677_10240960292454386_4...81.5 KiB69.1 KiB
div.elementor > div.elementor-element > div.elementor-element > img#1178 div.elementor > div.elementor-element > div.elementor-element > img#1178
lylaslegacy.org/wp-content/uploads/2025/08/Transparent-LL-Logo.png.webp19.4 KiB18.3 KiB

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:12092.682 label:Time to first byte subpart:timeToFirstByte] map[duration:805.516 label:Resource load delay subpart:resourceLoadDelay] map[duration:377.509 label:Resource load duration subpart:resourceLoadDuration] map[duration:34.131 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-DIV
nodeLabel: Building Belonging Changing Lives Providing life-saving safety equipment and m…
path: 1,HTML,1,BODY,3,MAIN,0,DIV,0,DIV,0,DIV
selector: main#content > div.page-content > div.elementor > div.elementor-element
snippet: <div class="elementor-element elementor-element-19973f2d e-con e-atomic-element e-flex…" data-id="19973f2d" data-element_type="e-flexbox" data-e-type="e-flexbox" data-interaction-id="19973f2d">

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-DIV
nodeLabel: Building Belonging Changing Lives Providing life-saving safety equipment and m…
path: 1,HTML,1,BODY,3,MAIN,0,DIV,0,DIV,0,DIV
selector: main#content > div.page-content > div.elementor > div.elementor-element
snippet: <div class="elementor-element elementor-element-19973f2d e-con e-atomic-element e-flex…" data-id="19973f2d" data-element_type="e-flexbox" data-e-type="e-flexbox" data-interaction-id="19973f2d">

HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLProtocol
lylaslegacy.org/http/1.1
/wp-content/cache/wpo-minify/1789001004/assets/wpo-minify...http/1.1
/wp-content/cache/wpo-minify/1789001004/assets/wpo-minify...http/1.1
/wp-content/cache/wpo-minify/1789001004/assets/wpo-minify...http/1.1
/wp-content/cache/wpo-minify/1789001004/assets/wpo-minify...http/1.1
/wp-content/cache/wpo-minify/1789001004/assets/wpo-minify...http/1.1
lylaslegacy.org/wp-content/uploads/2025/08/Transparent-LL-Logo.png.webphttp/1.1
/wp-content/uploads/2026/07/672446677_10240960292454386_4...http/1.1
/wp-content/cache/wpo-minify/1789001004/assets/wpo-minify...http/1.1
/wp-content/cache/wpo-minify/1789001004/assets/wpo-minify...http/1.1
/wp-content/cache/wpo-minify/1789001004/assets/wpo-minify...http/1.1
/wp-content/cache/wpo-minify/1789001004/assets/wpo-minify...http/1.1
lylaslegacy.org/wp-content/uploads/2026/08/home-page-hero-graphic-2-1024x564.pnghttp/1.1
/wp-content/uploads/elementor/google-fonts/fonts/cormoran...http/1.1
/wp-content/uploads/elementor/google-fonts/fonts/petitfor...http/1.1
/wp-content/uploads/elementor/google-fonts/fonts/lato-702...http/1.1
/wp-content/uploads/elementor/google-fonts/fonts/lato-b0c...http/1.1
/wp-content/uploads/elementor/google-fonts/fonts/lato-f09...http/1.1
/wp-content/uploads/elementor/google-fonts/fonts/lato-cc8...http/1.1
/wp-content/uploads/elementor/google-fonts/fonts/roboto-f...http/1.1
lylaslegacy.org/wp-json/wp-statistics/v2/hithttp/1.1
/wp-content/plugins/elementor/assets/js/shared-frontend-h...http/1.1
/wp-content/plugins/elementor/assets/js/text-editor.45609...http/1.1
lylaslegacy.org/wp-content/uploads/2026/08/cropped-Favicon-1-32x32.pnghttp/1.1

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.

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: 11.7 s
URLTime Spent
lylaslegacy.org/11.8 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.

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.

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

●Max Potential First Input Delay 70 ms
●Layout shift culprits
●Optimize DOM size
●Font display
●Forced reflow
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Avoids enormous network payloads Total size was 1,286 KiB
●JavaScript execution time 0.3 s
●Minimizes main-thread work 1.2 s
●Avoid long main-thread tasks 5 long tasks found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 120 ms
●Server Backend Latencies 10 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Avoid multiple page redirects
●Avoid large layout shifts 2 layout shifts found
○INP breakdown
○User Timing marks and measures
○Avoid non-composited animations
90

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.

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
Every Number Represents Someone We Love div.elementor > div.elementor-element > div.elementor-element > h5.e-785e782-9686cb7
Your Gift Creates Lasting Change div.elementor-element > div.elementor-element > div.e-con-inner > h4.e-67f5879-673003c
Any div.e-con-inner > div.elementor-element > div.elementor-element > h4.e-490f84c-1ce8941

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.elementor-element > div.elementor-element > div.elementor-icon-wrapper > a.elementor-icon div.elementor-element > div.elementor-element > div.elementor-icon-wrapper > a.elementor-icon
div.elementor-element > div.elementor-element > div.elementor-icon-wrapper > a.elementor-icon div.elementor-element > div.elementor-element > div.elementor-icon-wrapper > a.elementor-icon

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-hidden="true"]` is not present on the document `<body>`
●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-hidden="true"]` elements do not contain focusable descendents
●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
●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.
●Document has a main landmark.
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○Deprecated ARIA roles were not used
○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 use only permitted ARIA attributes
○`[role]`s have all required `[aria-*]` attributes
○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
○`[role]` values are valid
○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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○Buttons have an accessible name
○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
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○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.
○Identical links have the same purpose.
○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
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`

Send Feedback