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
app.termly.io/resource-blocker/216cf329-ca04-4739-97e0-83de0c63ae4c	14400.0 s	143.4 KiB
cdn.livechatinc.com/website/media/img/resources/logos/helpdesk-white-green.svg	172800.0 s	143.7 KiB
cdn.livechatinc.com/tracking.js	28800.0 s	32.9 KiB
app.termly.io/resource-blocker/support/894-6156b36a131577c56e7e.min.js	14400.0 s	8.4 KiB
/v3.6/customer/action/get_localization?organization_id=09...	600.0 s	4.7 KiB
app.termly.io/resource-blocker/support/808-26e9c6c7a3bd048ed656.min.js	14400.0 s	3.2 KiB
app.termly.io/resource-blocker/support/524-7d36cb122791702e3df2.min.js	14400.0 s	2.7 KiB
/v3.6/customer/action/get_configuration?organization_id=0...	600.0 s	1.8 KiB
/v3.6/customer/action/get_dynamic_configuration?x-region=...	0.0 ms	618 B
app.termly.io/resource-blocker/support/377-e518d8a5c599aa1c5977.min.js	14400.0 s	873 B
/global-mapper/lc_license_id/12212181/region?jsonp=__lc_r...	0.0 ms	200 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.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:119.369 source:map[column:156 line:13 type:source-location url:https://www.score.org/sites/default/files/js/js_YDBm4rPUvHWOm2jKNU25FOazMmkjHcDaZ8uaTS4q3zk.js?scope=footer&delta=0&language=en&theme=outline_frontend&include=eJxtjuEOgjAMhF8Is0dqynbA4uxIW4j49E5DoqD_evddc5fYufAGDT0mXnNV68C2kcLmKpZXUL7xCAvNyQ9oVxcvWUCDVnFICrHlIH7pWeQfT-1xlM5iVRALl81ztJDKShPK3F7OqLTaOLGfuBncgpUcrzSAfVEkiu8W3zP7lnBQH-YH9lKEu0NbM7XRV9ujo9ZlDl_37ruyWGHPVcKP8wSmoIXI urlProvider:network]]]

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:38.779 source:map[type:text value:[unattributed]]] map[reflowTime:2.19 source:map[column:712 line:14 type:source-location url:https://www.score.org/sites/default/files/js/js_YDBm4rPUvHWOm2jKNU25FOazMmkjHcDaZ8uaTS4q3zk.js?scope=footer&delta=0&language=en&theme=outline_frontend&include=eJxtjuEOgjAMhF8Is0dqynbA4uxIW4j49E5DoqD_evddc5fYufAGDT0mXnNV68C2kcLmKpZXUL7xCAvNyQ9oVxcvWUCDVnFICrHlIH7pWeQfT-1xlM5iVRALl81ztJDKShPK3F7OqLTaOLGfuBncgpUcrzSAfVEkiu8W3zP7lnBQH-YH9lKEu0NbM7XRV9ujo9ZlDl_37ruyWGHPVcKP8wSmoIXI urlProvider:network]] map[reflowTime:97.205 source:map[column:49615 line:2 type:source-location url:https://www.score.org/sites/default/files/js/js_YDBm4rPUvHWOm2jKNU25FOazMmkjHcDaZ8uaTS4q3zk.js?scope=footer&delta=0&language=en&theme=outline_frontend&include=eJxtjuEOgjAMhF8Is0dqynbA4uxIW4j49E5DoqD_evddc5fYufAGDT0mXnNV68C2kcLmKpZXUL7xCAvNyQ9oVxcvWUCDVnFICrHlIH7pWeQfT-1xlM5iVRALl81ztJDKShPK3F7OqLTaOLGfuBncgpUcrzSAfVEkiu8W3zP7lnBQH-YH9lKEu0NbM7XRV9ujo9ZlDl_37ruyWGHPVcKP8wSmoIXI urlProvider:network]] map[reflowTime:8.295 source:map[column:50335 line:2 type:source-location url:https://www.score.org/sites/default/files/js/js_YDBm4rPUvHWOm2jKNU25FOazMmkjHcDaZ8uaTS4q3zk.js?scope=footer&delta=0&language=en&theme=outline_frontend&include=eJxtjuEOgjAMhF8Is0dqynbA4uxIW4j49E5DoqD_evddc5fYufAGDT0mXnNV68C2kcLmKpZXUL7xCAvNyQ9oVxcvWUCDVnFICrHlIH7pWeQfT-1xlM5iVRALl81ztJDKShPK3F7OqLTaOLGfuBncgpUcrzSAfVEkiu8W3zP7lnBQH-YH9lKEu0NbM7XRV9ujo9ZlDl_37ruyWGHPVcKP8wSmoIXI urlProvider:network]] map[reflowTime:0.978 source:map[column:50393 line:2 type:source-location url:https://www.score.org/sites/default/files/js/js_YDBm4rPUvHWOm2jKNU25FOazMmkjHcDaZ8uaTS4q3zk.js?scope=footer&delta=0&language=en&theme=outline_frontend&include=eJxtjuEOgjAMhF8Is0dqynbA4uxIW4j49E5DoqD_evddc5fYufAGDT0mXnNV68C2kcLmKpZXUL7xCAvNyQ9oVxcvWUCDVnFICrHlIH7pWeQfT-1xlM5iVRALl81ztJDKShPK3F7OqLTaOLGfuBncgpUcrzSAfVEkiu8W3zP7lnBQH-YH9lKEu0NbM7XRV9ujo9ZlDl_37ruyWGHPVcKP8wSmoIXI urlProvider:network]] map[reflowTime:0.616 source:map[column:50457 line:2 type:source-location url:https://www.score.org/sites/default/files/js/js_YDBm4rPUvHWOm2jKNU25FOazMmkjHcDaZ8uaTS4q3zk.js?scope=footer&delta=0&language=en&theme=outline_frontend&include=eJxtjuEOgjAMhF8Is0dqynbA4uxIW4j49E5DoqD_evddc5fYufAGDT0mXnNV68C2kcLmKpZXUL7xCAvNyQ9oVxcvWUCDVnFICrHlIH7pWeQfT-1xlM5iVRALl81ztJDKShPK3F7OqLTaOLGfuBncgpUcrzSAfVEkiu8W3zP7lnBQH-YH9lKEu0NbM7XRV9ujo9ZlDl_37ruyWGHPVcKP8wSmoIXI urlProvider:network]] map[reflowTime:9.599 source:map[column:49637 line:2 type:source-location url:https://www.score.org/sites/default/files/js/js_YDBm4rPUvHWOm2jKNU25FOazMmkjHcDaZ8uaTS4q3zk.js?scope=footer&delta=0&language=en&theme=outline_frontend&include=eJxtjuEOgjAMhF8Is0dqynbA4uxIW4j49E5DoqD_evddc5fYufAGDT0mXnNV68C2kcLmKpZXUL7xCAvNyQ9oVxcvWUCDVnFICrHlIH7pWeQfT-1xlM5iVRALl81ztJDKShPK3F7OqLTaOLGfuBncgpUcrzSAfVEkiu8W3zP7lnBQH-YH9lKEu0NbM7XRV9ujo9ZlDl_37ruyWGHPVcKP8wSmoIXI urlProvider:network]] map[reflowTime:0.782 source:map[column:51395 line:2 type:source-location url:https://www.score.org/sites/default/files/js/js_YDBm4rPUvHWOm2jKNU25FOazMmkjHcDaZ8uaTS4q3zk.js?scope=footer&delta=0&language=en&theme=outline_frontend&include=eJxtjuEOgjAMhF8Is0dqynbA4uxIW4j49E5DoqD_evddc5fYufAGDT0mXnNV68C2kcLmKpZXUL7xCAvNyQ9oVxcvWUCDVnFICrHlIH7pWeQfT-1xlM5iVRALl81ztJDKShPK3F7OqLTaOLGfuBncgpUcrzSAfVEkiu8W3zP7lnBQH-YH9lKEu0NbM7XRV9ujo9ZlDl_37ruyWGHPVcKP8wSmoIXI urlProvider:network]] map[reflowTime:29.768 source:map[column:1826 line:0 type:source-location url:https://www.score.org/themes/custom/outline_frontend/dist/components/score/score-card-jumbo-cta-50/score-card-jumbo-50-1774983339.js urlProvider:network]] map[reflowTime:54.165 source:map[column:659 line:0 type:source-location url:https://www.score.org/themes/custom/outline_frontend/dist/components/score/score-image/score-image-1774983339.js urlProvider:network]]]

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:1630.214 label:Time to first byte subpart:timeToFirstByte] map[duration:455.092 label:Resource load delay subpart:resourceLoadDelay] map[duration:11.553 label:Resource load duration subpart:resourceLoadDuration] map[duration:978.714 label:Element render delay subpart:elementRenderDelay]]

lhId: page-0-IMG

nodeLabel: Owner of Zeal Aerial Fitness and SCORE Mentor

path: 1,HTML,1,BODY,3,DIV,2,MAIN,0,DIV,0,DIV,0,ARTICLE,0,DIV,0,SECTION,0,OUTLINE-GRID,0,OUTLINE-COLUMN,0,DIV,0,SCORE-CONTAINER,0,SCORE-INTERIOR-HERO-BANNER-LIGHT,0,DIV,0,SCORE-IMAGE,0,IMG

selector: score-interior-hero-banner-light > div > score-image > img

snippet: <img src="/sites/default/files/styles/responsive_16_9_500w/public/2026-01/Zeal-Aeria…" data-srcset="/sites/default/files/styles/responsive_16_9_250w/public/2026-01/Zeal-Aeria…" loading="eager" alt="Owner of Zeal Aerial Fitness and SCORE Mentor" width="412" height="232" data-multiplier="1x" data-ratio="16:9" data-observed="1" data-loaded="1">

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: Owner of Zeal Aerial Fitness and SCORE Mentor

path: 1,HTML,1,BODY,3,DIV,2,MAIN,0,DIV,0,DIV,0,ARTICLE,0,DIV,0,SECTION,0,OUTLINE-GRID,0,OUTLINE-COLUMN,0,DIV,0,SCORE-CONTAINER,0,SCORE-INTERIOR-HERO-BANNER-LIGHT,0,DIV,0,SCORE-IMAGE,0,IMG

selector: score-interior-hero-banner-light > div > score-image > img

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

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
/sites/default/files/css/css_UeUBFXFmqd1K-XLM7GEjb80FzueB...	3.1 KiB
/sites/default/files/css/css_i9IM56GfQPJmF5iVO4lf0PdIV8HR...	13.1 KiB	300 ms

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Est Savings
www.score.org/modules/custom/score_assets/slick/fonts/slick.woff	10 ms

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: 754 ms

URL	Time Spent
score.org/	754 ms
www.score.org/	0.0 ms

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: 1.2 s

URL	Time Spent
www.score.org/	1.3 s

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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 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: 570 ms 128.9 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtm.js?id=GTM-TB22VPP	174.2 KiB	74.5 KiB
app.termly.io/resource-blocker/216cf329-ca04-4739-97e0-83de0c63ae4c	143.2 KiB	54.5 KiB

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
www.score.org/	1.5 s	61 ms	6.8 ms
/sites/default/files/js/js_YDBm4rPUvHWOm2jKNU25FOazMmkjHc...	1.3 s	621 ms	20 ms
Unattributable	851 ms	39 ms	0.0 ms
www.googletagmanager.com/gtm.js?id=GTM-TB22VPP	821 ms	643 ms	133 ms
/themes/custom/outline_frontend/dist/node_modules/lit-ele...	729 ms	511 ms	0.2 ms
app.termly.io/resource-blocker/216cf329-ca04-4739-97e0-83de0c63ae4c	544 ms	430 ms	70 ms
/themes/custom/outline_frontend/dist/components/score/sco...	269 ms	11 ms	0.1 ms
/themes/custom/outline_frontend/dist/node_modules/lit-ele...	232 ms	210 ms	0.2 ms
cdn.livechatinc.com/tracking.js	195 ms	166 ms	21 ms
/themes/custom/outline_frontend/dist/components/base/outl...	165 ms	127 ms	0.1 ms
cdn.gtranslate.net/widgets/latest/dropdown.js	149 ms	134 ms	2.3 ms
/themes/custom/outline_frontend/dist/components/score/sco...	122 ms	0.0 ms	0.1 ms
/v3.6/customer/action/get_configuration?organization_id=0...	93 ms	86 ms	1.9 ms
/themes/custom/outline_frontend/dist/components/controlle...	83 ms	65 ms	0.1 ms
/themes/custom/outline_frontend/dist/node_modules/@vimeo/...	79 ms	45 ms	0.4 ms
/themes/custom/outline_frontend/dist/components/controlle...	64 ms	60 ms	0.2 ms
/themes/custom/outline_frontend/dist/components/base/outl...	61 ms	25 ms	0.3 ms
/themes/custom/outline_frontend/dist/components/score/sco...	60 ms	7.2 ms	0.1 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Script Evaluation	3.4 s
Other	1.7 s
Style & Layout	1.7 s
Rendering	499 ms
Script Parsing & Compilation	306 ms
Parse HTML & CSS	285 ms
Garbage Collection	24 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reason	Failure type
Pages with WebSocket cannot enter back/forward cache.	Pending browser support

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 2.2 KiB

URL	Transfer Size	Est Savings
/modules/custom/score_analytics/dlv_shadow_dom_helper_jqu...	3.9 KiB	2.2 KiB

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

●Layout shift culprits

●Optimize DOM size

●Improve image delivery

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Reduce unused CSS

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

●User Timing marks and measures 3 user timings

●Avoid long main-thread tasks 20 long tasks found

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

●Network Requests

●Network Round Trip Times 10 ms

●Server Backend Latencies 360 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

○INP breakdown

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

ARIA

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.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
Powered by Progressive Commercial. Mentor and client meeting pointing at laptop. `div.carousel-wrapper > div.slick-list > div.slick-track > div#slick-slide00`
c `div.carousel-wrapper > div.slick-list > div.slick-track > div#slick-slide10`

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
Prepare for Event Success: Plan for Peak Demand, Operations, and Execution `div.heading-container > h4.semibold`

These are opportunities to improve keyboard navigation in your application.

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.header-container > div > score-image > img `div.header-container > div > score-image > img`

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
score-header > div > div#block-outline-frontend-site-branding > a.logo `score-header > div > div#block-outline-frontend-site-branding > a.logo`

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.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
REGISTER FOR ONLINE LIVE EVENT REGISTER FOR ONLINE LIVE EVENT `a.btn`

○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

●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

●`[aria-*]` attributes have valid values

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

●Buttons have an accessible name

●Input buttons have discernible text.

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

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

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

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

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

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

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

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

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○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

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

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

○Select elements have associated label elements.

○Skip links are focusable.

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

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

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.

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.header-container > div > score-image > img `div.header-container > div > score-image > img`

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 have descriptive text

●Links are crawlable

●robots.txt is valid

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`