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
connect.facebook.net/en_US/fbevents.js	1200.0 s	96.6 KiB
/signals/config/137848689911278?v=2.9.303&r=stable&domain...	1200.0 s	86.3 KiB
/signals/config/137848689911278?v=2.9.303&r=stable&domain...	1200.0 s	86.3 KiB
ph.aweber.com/static/surveys.js?v=1.370.1	300.0 s	30.5 KiB
scripts.clarity.ms/0.8.59/clarity.js	86400.0 s	26.2 KiB
/v3.6/customer/action/get_localization?organization_id=67...	600.0 s	4.7 KiB
static.cloudflareinsights.com/beacon.min.js	86400.0 s	10.7 KiB
/v3.6/customer/action/get_configuration?organization_id=6...	600.0 s	1.6 KiB
/v3.6/customer/action/get_dynamic_configuration?x-region=...	0.0 ms	623 B
scripts.clarity.ms/0.8.59/clarity.livechat.js	86400.0 s	1.3 KiB
ph.aweber.com/array/phc_CrcHvwT29CjFQD1FpXXp3eLB6LrWANZtKrZu32L6RWi/config.js	14400.0 s	685 B
api.livechatinc.com/global-mapper/lc_license_id/8613054/region?jsonp=__lc_region	0.0 ms	199 B
/tr/?id=137848689911278&ev=PageView&dl=https%3A%2F%2Fwww....	0.0 ms	19 B
connect.facebook.net/en_US/fbevents.js	1200.0 s	0 B
edge.fullstory.com/s/fs.js	3600.0 s	0 B
edge.fullstory.com/s/fs.js	3600.0 s	0 B
ph.aweber.com/static/array.js	300.0 s	0 B
cdn.livechatinc.com/tracking.js	28800.0 s	0 B
ph.aweber.com/static/surveys.js?v=1.370.1	300.0 s	0 B
www.google-analytics.com/analytics.js	7200.0 s	0 B
s.yimg.com/wi/ytc.js	0.0 ms	0 B
analytics.aweber.com/js/awt_analytics.js?id=1w	0.0 ms	0 B
ph.aweber.com/array/phc_CrcHvwT29CjFQD1FpXXp3eLB6LrWANZtKrZu32L6RWi/config.js	14400.0 s	0 B
/v.gif?cd=0&a=1330&d=aweber.com&u=DD67098C773EA836A178F0D...	43200.0 s	0 B

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:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:0.585 source:map[column:7461 line:1 type:source-location url:https://assets.aweber-static.com/www/assets/bundles/jquery.3d7b1213.js urlProvider:network]] map[reflowTime:45.336 source:map[column:57840 line:1 type:source-location url:https://assets.aweber-static.com/www/assets/bundles/jquery.3d7b1213.js urlProvider:network]] map[reflowTime:0.28 source:map[column:57898 line:1 type:source-location url:https://assets.aweber-static.com/www/assets/bundles/jquery.3d7b1213.js urlProvider:network]] map[reflowTime:0.207 source:map[column:57962 line:1 type:source-location url:https://assets.aweber-static.com/www/assets/bundles/jquery.3d7b1213.js urlProvider:network]] map[reflowTime:0.119 source:map[column:7483 line:1 type:source-location url:https://assets.aweber-static.com/www/assets/bundles/jquery.3d7b1213.js urlProvider:network]] map[reflowTime:0.3 source:map[column:58883 line:1 type:source-location url:https://assets.aweber-static.com/www/assets/bundles/jquery.3d7b1213.js urlProvider:network]] map[reflowTime:11.383 source:map[type:text value:[unattributed]]]]

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
MCP chat `div.aw-row > div.aw-col-xs-12 > div.feature-card > img.feature-image`	assets.aweber-static.com/www/assets/img/homepage/mcp.772e72e7.png	278.1 KiB	235.8 KiB
	d3tnn7lar6ozas.cloudfront.net/324c02db-6b9b-4059-81fa-61006f2a2e9c.png	10.7 KiB	10.2 KiB
div.feature-card-new > div.feature-card-content > h3.feature-card-title > img.feature-icon `div.feature-card-new > div.feature-card-content > h3.feature-card-title > img.feature-icon`	/www/assets/img/homepage/icons/2025/web-push-notification...	7.3 KiB	7.0 KiB
div.feature-card-new > div.feature-card-content > h3.feature-card-title > img.feature-icon `div.feature-card-new > div.feature-card-content > h3.feature-card-title > img.feature-icon`	/www/assets/img/homepage/icons/2025/email-marketing.2246e...	6.0 KiB	5.7 KiB
div.feature-card-new > div.feature-card-content > h3.feature-card-title > img.feature-icon `div.feature-card-new > div.feature-card-content > h3.feature-card-title > img.feature-icon`	/www/assets/img/homepage/icons/2025/workflow-automations....	5.8 KiB	5.6 KiB
div.feature-card-new > div.feature-card-content > h3.feature-card-title > img.feature-icon `div.feature-card-new > div.feature-card-content > h3.feature-card-title > img.feature-icon`	assets.aweber-static.com/www/assets/img/homepage/icons/2025/ai.e0225de0.png	5.4 KiB	5.2 KiB
WordPress `div.aw-col-xs-12 > div.integrations-grid > div.integration-logo > img`	assets.aweber-static.com/www/assets/img/homepage/int-wordpress.4313f90c.png	5.4 KiB	4.4 KiB

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
/css2?family=Calistoga&family=Inter:ital,opsz,wght@0,14.....	874 B
assets.aweber-static.com/www/assets/css/index-t2-style.41191f38.css	17.4 KiB
fonts.googleapis.com/css2?family=Calistoga&display=swap	586 B
assets.aweber-static.com/www/assets/bundles/jquery.3d7b1213.js	0 B

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

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

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

URL	Time Spent
aweber.com/	1.2 s
www.aweber.com/	2.1 s
www.aweber.com/index-t2.htm	0.0 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Layout shift score
0.110

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.

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: 170 ms 12.4 KiB

URL	Transfer Size	Est Savings
assets.aweber-static.com/www/assets/css/index-t2-style.41191f38.css	17.1 KiB	12.4 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: 5.8 s 1.3 MiB

URL	Transfer Size	Est Savings
assets.aweber-static.com/www/assets/bundles/vendor.1d4983cd.js	91.9 KiB	91.4 KiB
assets.aweber-static.com/www/assets/bundles/vendor.1d4983cd.js	91.9 KiB	76.2 KiB
fast.wistia.net/assets/external/E-v1.js	97.4 KiB	72.5 KiB
www.googletagmanager.com/gtag/destination?id=AW-1071267547&cx=c&gtm=4e64k0	133.9 KiB	67.1 KiB
www.googletagmanager.com/gtag/js?id=G-05FEES4HX1&cx=c&gtm=4e64k0	178.9 KiB	66.3 KiB
www.googletagmanager.com/gtag/js?id=G-05FEES4HX1&cx=c&gtm=4e64k0	178.9 KiB	66.0 KiB
www.googletagmanager.com/gtag/js?id=AW-849838713&cx=c&gtm=4e64k0	144.3 KiB	63.0 KiB
www.googletagmanager.com/gtag/js?id=AW-849838713&cx=c&gtm=4e64k0	144.3 KiB	63.0 KiB
www.googletagmanager.com/gtag/js?id=G-FTJYCR0QMZ&cx=c&gtm=4e64k0	146.3 KiB	62.6 KiB
www.googletagmanager.com/gtag/js?id=G-FTJYCR0QMZ&cx=c&gtm=4e64k0	146.3 KiB	62.1 KiB
www.googletagmanager.com/gtag/js?id=AW-849867947&cx=c&gtm=4e64k0	144.0 KiB	62.0 KiB
www.googletagmanager.com/gtag/js?id=AW-849867947&cx=c&gtm=4e64k0	144.0 KiB	61.9 KiB
/gtm.js?id=GTM-5J4XPK&gtm_auth=UYNjOPXi40kADX0ZYRcuvw&gtm...	177.0 KiB	60.7 KiB
/gtm.js?id=GTM-5J4XPK&gtm_auth=UYNjOPXi40kADX0ZYRcuvw&gtm...	177.0 KiB	60.4 KiB
edge.fullstory.com/s/fs.js	79.2 KiB	51.2 KiB
connect.facebook.net/en_US/fbevents.js	96.5 KiB	44.8 KiB
edge.fullstory.com/s/fs.js	79.2 KiB	42.2 KiB
solve-widget.forethought.ai/embed.js	68.6 KiB	39.7 KiB
ph.aweber.com/static/array.js	60.8 KiB	33.9 KiB
connect.facebook.net/en_US/fbevents.js	96.5 KiB	31.9 KiB
ph.aweber.com/static/array.js	60.8 KiB	31.5 KiB
edge.fullstory.com/s/fs.js	79.2 KiB	29.2 KiB
cdn.livechatinc.com/tracking.js	32.5 KiB	27.3 KiB
assets.aweber-static.com/www/assets/bundles/jquery.3d7b1213.js	38.3 KiB	26.1 KiB
assets.aweber-static.com/www/assets/bundles/jquery.3d7b1213.js	38.3 KiB	25.3 KiB
ph.aweber.com/static/surveys.js?v=1.370.1	30.2 KiB	24.2 KiB
ph.aweber.com/static/surveys.js?v=1.370.1	30.2 KiB	24.1 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.aweber.com/index-t2.htm	5.3 s	2.8 s	164 ms
Unattributable	2.0 s	110 ms	0.0 ms
edge.fullstory.com/s/fs.js	1.1 s	850 ms	98 ms
www.googletagmanager.com/gtag/js?id=G-05FEES4HX1&cx=c&gtm=4e64k0	1.0 s	725 ms	205 ms
assets.aweber-static.com/www/assets/bundles/vendor.1d4983cd.js	836 ms	544 ms	145 ms
/gtm.js?id=GTM-5J4XPK&gtm_auth=UYNjOPXi40kADX0ZYRcuvw&gtm...	692 ms	532 ms	141 ms
fast.wistia.net/assets/external/E-v1.js	631 ms	485 ms	91 ms
www.googletagmanager.com/gtag/js?id=AW-849867947&cx=c&gtm=4e64k0	595 ms	468 ms	123 ms
www.googletagmanager.com/gtag/js?id=AW-849838713&cx=c&gtm=4e64k0	569 ms	425 ms	140 ms
www.googletagmanager.com/gtag/js?id=G-FTJYCR0QMZ&cx=c&gtm=4e64k0	566 ms	421 ms	138 ms
ph.aweber.com/static/array.js	438 ms	366 ms	62 ms
www.aweber.com/	393 ms	141 ms	158 ms
connect.facebook.net/en_US/fbevents.js	355 ms	223 ms	89 ms
assets.aweber-static.com/www/assets/bundles/globals.0ee29b05.js	293 ms	49 ms	0.9 ms
scripts.clarity.ms/0.8.59/clarity.js	259 ms	223 ms	9.5 ms
assets.aweber-static.com/www/assets/bundles/jquery.3d7b1213.js	242 ms	179 ms	42 ms
/signals/config/137848689911278?v=2.9.303&r=stable&domain...	198 ms	174 ms	22 ms
solve-widget.forethought.ai/embed.js	174 ms	140 ms	21 ms
www.googletagmanager.com/gtag/destination?id=AW-1071267547&cx=c&gtm=4e64k0	162 ms	126 ms	35 ms
cdn.livechatinc.com/tracking.js	157 ms	113 ms	34 ms
www.google-analytics.com/analytics.js	137 ms	112 ms	19 ms
/assets/external/iframeApi.js@51432a28fdfed55ac3775a38563...	102 ms	84 ms	0.6 ms
/dcdn/settings.js?a=1330&settings_type=4&ts=1776871296&dt...	89 ms	31 ms	58 ms
/v3.6/customer/action/get_configuration?organization_id=6...	82 ms	76 ms	0.8 ms
/cdn/7.0/track-8854bbf636dc51133b2fa5048349131fbr.js	62 ms	58 ms	3.8 ms
bat.bing.com/bat.js	56 ms	43 ms	12 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	9.8 s
Other	3.2 s
Script Parsing & Compilation	1.9 s
Style & Layout	1.4 s
Garbage Collection	261 ms
Rendering	259 ms
Parse HTML & CSS	152 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

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
solve-widget.forethought.ai/static/js/async/686.71a27cd8.js	734.5 KiB
/www/assets/img/homepage/create-customers-for-life.863c17...	496.3 KiB
assets.aweber-static.com/www/assets/img/awards/stevie2022-gold.f13261bb.png	462.6 KiB
assets.aweber-static.com/www/assets/img/homepage/make-money.d55b96c9.png	457.3 KiB
assets.aweber-static.com/www/assets/img/awards/stevie2022-bronze.a5dde858.png	432.3 KiB
/www/assets/img/homepage/get-more-eyes-on-your-content.f2...	418.3 KiB
assets.aweber-static.com/www/assets/img/homepage/split-hero-t2.05967eb7.png	398.4 KiB
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	362.4 KiB
/www/assets/img/homepage/grow-your-email-list.b47abfda.png	331.3 KiB
/www/assets/img/homepage/save-time-with-automation.14441e...	320.5 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL
2022 Gold Stevie Award `div.aw-row > div.aw-col-xs-12 > div.awards-top > img`	assets.aweber-static.com/www/assets/img/awards/stevie2022-gold.f13261bb.png
2022 Bronze Stevie Award `div.aw-row > div.aw-col-xs-12 > div.awards-top > img`	assets.aweber-static.com/www/assets/img/awards/stevie2022-bronze.a5dde858.png
2025 Gold Stevie Award `div.aw-row > div.aw-col-xs-12 > div.awards-top > img`	assets.aweber-static.com/www/assets/img/awards/stevie2025-gold.074681ec.png
2025 Bronze Stevie Award `div.aw-row > div.aw-col-xs-12 > div.awards-top > img`	assets.aweber-static.com/www/assets/img/awards/stevie2025-bronze.f22eb5b8.png
2024 Silver Stevie Award `div.aw-row > div.aw-col-xs-12 > div.awards-top > img`	assets.aweber-static.com/www/assets/img/awards/stevie2024-silver.14c94943.png
2021 Silver Stevie Award `div.aw-row > div.aw-col-xs-12 > div.awards-top > img`	assets.aweber-static.com/www/assets/img/awards/stevie2021-silver.90f8b6db.png
2021 Bronze Stevie Award `div.aw-row > div.aw-col-xs-12 > div.awards-top > img`	assets.aweber-static.com/www/assets/img/awards/stevie2021-bronze.915ad5fc.png
2020 Bronze Stevie Award `div.aw-row > div.aw-col-xs-12 > div.awards-top > img`	assets.aweber-static.com/www/assets/img/awards/stevie2020-bronze.21a2248e.jpg
2019 Silver Stevie Award `div.aw-row > div.aw-col-xs-12 > div.awards-top > img`	assets.aweber-static.com/www/assets/img/awards/stevie2019-silver.751870e7.jpg
2019 Bronze Stevie Award `div.aw-row > div.aw-col-xs-12 > div.awards-top > img`	assets.aweber-static.com/www/assets/img/awards/stevie2019-bronze.ebba53c8.jpg
2018 Silver Stevie Award `div.aw-row > div.aw-col-xs-12 > div.awards-top > img`	assets.aweber-static.com/www/assets/img/awards/stevie2018-silver.3e56b3d8.jpg
2018 Bronze Stevie Award `div.aw-row > div.aw-col-xs-12 > div.awards-top > img`	assets.aweber-static.com/www/assets/img/awards/stevie2018-bronze.d4976afd.jpg
graphic that says 27 year anniversary `div.aw-ribbon-inner > a.dfy-link > span.aw-ribbon-msg > img.p--xs-small-r`	assets.aweber-static.com/www/assets/img/launch/anni-27.2064556f.png

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

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●LCP breakdown

●Modern HTTP

●Network dependency tree

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●User Timing marks and measures 25 user timings

●Avoid long main-thread tasks 20 long tasks found

●Network Requests

●Network Round Trip Times 100 ms

●Server Backend Latencies 470 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

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

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
Get AWeber Free `div.aw-container > div.aw-row > div.nav > a#gtm-order-nav-00`
Start for free → `div.aw-row > div.aw-col-xs-12 > div.p--xs-small-t > a.btn`
LIMITED TIME OFFER `div.aw-row > div.aw-col-xs-12 > div.dfy-card > span.dfy-badge`
$79 `div.aw-col-xs-12 > div.dfy-card > div.dfy-pricing > span.dfy-price`
for a limited time (Reg. $599) `div.aw-col-xs-12 > div.dfy-card > div.dfy-pricing > span.dfy-price-note`
Start for $79 today → `div.aw-row > div.aw-col-xs-12 > div.dfy-card > a.btn`
$599 `div.card > div.card__header > p.h5 > strike.text--negative`
Advanced landing page features `div.card > div.card__footer > p > strike`
Sales tracking and low transaction fees `div.card > div.card__footer > p > strike`
Remove AWeber branding `div.card > div.card__footer > p.m--xs-xsmall-b > strike`
Start your free trial → `div.aw-row > div.aw-col-xs-12 > div.final-cta-box > a.btn`

These are opportunities to improve the legibility of your content.

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
body.body--hero-dark > a.dfy-link `body.body--hero-dark > a.dfy-link`
body.body--hero-dark > div.aw-sticky-ribbon > a.dfy-link `body.body--hero-dark > div.aw-sticky-ribbon > a.dfy-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

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

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

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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

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

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

●Elements use only permitted ARIA attributes

●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

●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

●Touch targets have sufficient size and spacing.

●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

●Heading elements appear in a sequentially-descending order

●Deprecated ARIA roles were not used

●ARIA IDs are unique

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

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

○No form fields have multiple labels

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

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

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
AttributionReporting	connect.facebook.net/en_US/fbevents.js line 279, col 769

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source	Description
assets.aweber-static.com/www/assets/bundles/vendor.1d4983cd.js line 1, col 130590	`[AW-WebPush]: Unable to initialize AWeber Web Push Notifications: error fetching prompts. TypeError: Failed to fetch`

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

Canonical links suggest which URL to show in search results. Learn more about canonical links.

Why this matters

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

Source: MDN Permissions-Policy

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

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