Skip to content
Audit Complete

Results for https://aweber.com

Visit site
Spain Spain · Madrid Completed: Apr 22, 2026 20:30 UTC
Download JSON Download Markdown Report

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
C72

Site Health

Score: 72 / 100

Based on 8 categories, 0 sections

Room to improve — your 31.6s load time is above Google's 2.5s 'Good' threshold.

Several missing protections leave your users and data exposed.

Several issues make your site difficult for assistive technology users.

Well-optimized for search — your content is discoverable.

Solid infrastructure — fast server responses across the board.

Mostly compliant — a few items need attention.

Rich content metadata — your pages look great everywhere.

Heavier than average — reducing page weight saves energy and bandwidth.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

Apple · 1113 peers
You 72
·
Avg 73
At average
0 50 100
Better than 32% of Apple sites See full Apple benchmark →
Cloudflare Bot Management · 412 peers
You 72
·
Avg 74
At average
0 50 100
Better than 23% of Cloudflare Bot Management sites See full Cloudflare Bot Management benchmark →

Top Priorities (5)

1

Content-Security-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
2

HSTS header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
3

No Content-Security-Policy header found

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy
4

Page weighs 32.5 MB (14.9 MB transferred)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Budget
5

1 control(s) without accessible label

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Form Accessibility
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

3

High impact, low effort — start here.

Strategic

2

High impact, requires investment.

Easy Improvements

0

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

0

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Faweber.com)](https://beavercheck.com/results/07063d4d-0068-4da3-ac7b-b914e20a40b6)
<a href="https://beavercheck.com/results/07063d4d-0068-4da3-ac7b-b914e20a40b6"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Faweber.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Faweber.com

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 31.6s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. Addressing the critical issues below would have the most immediate impact on your user trust.

3 security gaps detected — browsers may warn visitors about your site.
Your LCP is 31.6s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.
1 accessibility issue excludes users who rely on assistive technology.

Conversion Barriers

2 critical 5 warning

7 barrier(s) likely increasing bounce by ~28%.

Speed (2)

Page takes 31.6s to load

+12% bounce

Users abandon at ~3s — you're 29.1s over the 2.5s threshold

Fix: Optimize render-blocking resources, preload the hero image, and compress images

Page feels frozen for 2.3s

+5% bounce

Clicks on the primary CTA are ignored while JavaScript runs

Fix: Break up long tasks; defer non-critical JavaScript to post-hydration

Trust (2)

No HSTS header

+1% bounce

Returning visitors are briefly exposed to downgrade attacks on first request

Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Usability (2)

Layout shifts during page load

+3% bounce

Content movement causes mis-clicks on CTAs and form fields

Fix: Add width/height to images; reserve space for late-loading embeds

1 form field(s) without a label

+2% bounce

Screen readers skip unlabeled fields; autofill can't identify them; checkout abandonment spikes

Fix: Associate every input with a visible <label for="…">; add autocomplete attributes

Navigation (1)

No skip-to-content link

+1% bounce

Keyboard and screen-reader users must tab through the entire header on every page

Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

€425 investment → €3.48/month returns + EUR 120,500,000 risk avoided

Payback period: > 2 years First-year ROI: -90%

Investment

€425

5h · 5 findings

Monthly returns

€3.48 /mo

~€42 / year

  • Bandwidth savings €3.48

Regulatory risk avoided

EUR 120,500,000

if kept compliant

  • ePrivacy Directive EUR 100,000,000
  • GDPR EUR 20,000,000
  • EAA EUR 500,000

€128 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

€425

5.0 developer hours at €85/hr

Based on European Union rates (€85/hr)

Quick wins
€128 3 fixes in ~90 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions
/hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

€10,041,670 / month at risk

~€120,500,042 / year if left unfixed

Compliance Risk

€120,500,000

ePrivacy DirectiveGDPREAA
  • No privacy policy link detected
    GDPR: EUR 10,000 – EUR 20,000,000
  • 1 advertising/retargeting trackers detected
    GDPR: EUR 10,000 – EUR 20,000,000
  • Trackers detected but no cookie policy found
    GDPR: EUR 5,000 – EUR 10,000,000

+7 more

Bandwidth Waste

€3.48 /mo

46955.6 MB/mo × 0.074 EUR/GB

  • Optimize transfer: save ~4.7 MB per page load
    Saves €3.48/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Unique monthly visitors from your analytics

Purchases, signups, or key actions

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue
Current bounce (est.)
After fixes (est.)
Estimated bounce reduction

Fix 5 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

27
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
92
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
77
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
92
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

4.60 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

31.57 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

2.33 s

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.110

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

7.68 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

50.19 s

Detailed Report

Audit breakdown by category with detailed findings.

27

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

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

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.

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.

URLResource SizeEst 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.png278.1 KiB235.8 KiB
d3tnn7lar6ozas.cloudfront.net/324c02db-6b9b-4059-81fa-61006f2a2e9c.png10.7 KiB10.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 KiB7.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 KiB5.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 KiB5.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.png5.4 KiB5.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.png5.4 KiB4.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.

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

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

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

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Estimated savings: 5.8 s 1.3 MiB
URLTransfer SizeEst Savings
assets.aweber-static.com/www/assets/bundles/vendor.1d4983cd.js91.9 KiB91.4 KiB
assets.aweber-static.com/www/assets/bundles/vendor.1d4983cd.js91.9 KiB76.2 KiB
fast.wistia.net/assets/external/E-v1.js97.4 KiB72.5 KiB
www.googletagmanager.com/gtag/destination?id=AW-1071267547&cx=c&gtm=4e64k0133.9 KiB67.1 KiB
www.googletagmanager.com/gtag/js?id=G-05FEES4HX1&cx=c&gtm=4e64k0178.9 KiB66.3 KiB
www.googletagmanager.com/gtag/js?id=G-05FEES4HX1&cx=c&gtm=4e64k0178.9 KiB66.0 KiB
www.googletagmanager.com/gtag/js?id=AW-849838713&cx=c&gtm=4e64k0144.3 KiB63.0 KiB
www.googletagmanager.com/gtag/js?id=AW-849838713&cx=c&gtm=4e64k0144.3 KiB63.0 KiB
www.googletagmanager.com/gtag/js?id=G-FTJYCR0QMZ&cx=c&gtm=4e64k0146.3 KiB62.6 KiB
www.googletagmanager.com/gtag/js?id=G-FTJYCR0QMZ&cx=c&gtm=4e64k0146.3 KiB62.1 KiB
www.googletagmanager.com/gtag/js?id=AW-849867947&cx=c&gtm=4e64k0144.0 KiB62.0 KiB
www.googletagmanager.com/gtag/js?id=AW-849867947&cx=c&gtm=4e64k0144.0 KiB61.9 KiB
/gtm.js?id=GTM-5J4XPK&gtm_auth=UYNjOPXi40kADX0ZYRcuvw&gtm...177.0 KiB60.7 KiB
/gtm.js?id=GTM-5J4XPK&gtm_auth=UYNjOPXi40kADX0ZYRcuvw&gtm...177.0 KiB60.4 KiB
edge.fullstory.com/s/fs.js79.2 KiB51.2 KiB
connect.facebook.net/en_US/fbevents.js96.5 KiB44.8 KiB
edge.fullstory.com/s/fs.js79.2 KiB42.2 KiB
solve-widget.forethought.ai/embed.js68.6 KiB39.7 KiB
ph.aweber.com/static/array.js60.8 KiB33.9 KiB
connect.facebook.net/en_US/fbevents.js96.5 KiB31.9 KiB
ph.aweber.com/static/array.js60.8 KiB31.5 KiB
edge.fullstory.com/s/fs.js79.2 KiB29.2 KiB
cdn.livechatinc.com/tracking.js32.5 KiB27.3 KiB
assets.aweber-static.com/www/assets/bundles/jquery.3d7b1213.js38.3 KiB26.1 KiB
assets.aweber-static.com/www/assets/bundles/jquery.3d7b1213.js38.3 KiB25.3 KiB
ph.aweber.com/static/surveys.js?v=1.370.130.2 KiB24.2 KiB
ph.aweber.com/static/surveys.js?v=1.370.130.2 KiB24.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.

URLTotal CPU TimeScript EvaluationScript Parse
www.aweber.com/index-t2.htm5.3 s2.8 s164 ms
Unattributable2.0 s110 ms0.0 ms
edge.fullstory.com/s/fs.js1.1 s850 ms98 ms
www.googletagmanager.com/gtag/js?id=G-05FEES4HX1&cx=c&gtm=4e64k01.0 s725 ms205 ms
assets.aweber-static.com/www/assets/bundles/vendor.1d4983cd.js836 ms544 ms145 ms
/gtm.js?id=GTM-5J4XPK&gtm_auth=UYNjOPXi40kADX0ZYRcuvw&gtm...692 ms532 ms141 ms
fast.wistia.net/assets/external/E-v1.js631 ms485 ms91 ms
www.googletagmanager.com/gtag/js?id=AW-849867947&cx=c&gtm=4e64k0595 ms468 ms123 ms
www.googletagmanager.com/gtag/js?id=AW-849838713&cx=c&gtm=4e64k0569 ms425 ms140 ms
www.googletagmanager.com/gtag/js?id=G-FTJYCR0QMZ&cx=c&gtm=4e64k0566 ms421 ms138 ms
ph.aweber.com/static/array.js438 ms366 ms62 ms
www.aweber.com/393 ms141 ms158 ms
connect.facebook.net/en_US/fbevents.js355 ms223 ms89 ms
assets.aweber-static.com/www/assets/bundles/globals.0ee29b05.js293 ms49 ms0.9 ms
scripts.clarity.ms/0.8.59/clarity.js259 ms223 ms9.5 ms
assets.aweber-static.com/www/assets/bundles/jquery.3d7b1213.js242 ms179 ms42 ms
/signals/config/137848689911278?v=2.9.303&r=stable&domain...198 ms174 ms22 ms
solve-widget.forethought.ai/embed.js174 ms140 ms21 ms
www.googletagmanager.com/gtag/destination?id=AW-1071267547&cx=c&gtm=4e64k0162 ms126 ms35 ms
cdn.livechatinc.com/tracking.js157 ms113 ms34 ms
www.google-analytics.com/analytics.js137 ms112 ms19 ms
/assets/external/iframeApi.js@51432a28fdfed55ac3775a38563...102 ms84 ms0.6 ms
/dcdn/settings.js?a=1330&settings_type=4&ts=1776871296&dt...89 ms31 ms58 ms
/v3.6/customer/action/get_configuration?organization_id=6...82 ms76 ms0.8 ms
/cdn/7.0/track-8854bbf636dc51133b2fa5048349131fbr.js62 ms58 ms3.8 ms
bat.bing.com/bat.js56 ms43 ms12 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.

CategoryTime Spent
Script Evaluation9.8 s
Other3.2 s
Script Parsing & Compilation1.9 s
Style & Layout1.4 s
Garbage Collection261 ms
Rendering259 ms
Parse HTML & CSS152 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 reasonFailure type
Pages with WebSocket cannot enter back/forward cache.Pending browser support

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
92

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

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 / WarningSource
AttributionReporting

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.

SourceDescription
[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
92

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

Performance issues directly impact user engagement and conversion rates.

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`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

65
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
90
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
81
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
92
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

1.70 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

5.82 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

143 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.008

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

1.84 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

8.36 s

Detailed Report

Audit breakdown by category with detailed findings.

65

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

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

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 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:0.296 source:map[column:377712 line:20 type:source-location url: 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:13.185 source:map[type:text value:[unattributed]]] map[reflowTime:4.868 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:0.395 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.199 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.268 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.121 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.318 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:0.296 source:map[column:379595 line:19 type:source-location url: urlProvider:network]]]

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
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.png278.1 KiB148.0 KiB
Fine Dining div.template-column > div.template-card > div.email-template > img
images.unsplash.com/photo-1504674900247-0877df9cc836?w=600&h=400&fit=crop89.4 KiB84.9 KiB
Travel div.template-column > div.template-card > div.email-template > img
images.unsplash.com/photo-1469854523086-cc02fe5d8800?w=600&h=400&fit=crop78.7 KiB74.2 KiB
Luxury Store div.template-column > div.template-card > div.email-template > img
images.unsplash.com/photo-1441986300917-64674bd600d8?w=600&h=400&fit=crop66.5 KiB62.0 KiB
Team Meeting div.template-column > div.template-card > div.email-template > img
images.unsplash.com/photo-1600880292203-757bb62b4baf?w=600&h=450&fit=crop63.9 KiB58.8 KiB
Creative Team div.template-column > div.template-card > div.email-template > img
images.unsplash.com/photo-1522071820081-009f0129c71c?w=600&h=400&fit=crop55.6 KiB51.1 KiB
Dashboard Analytics div.template-card > div.email-template > div > img
images.unsplash.com/photo-1551288049-bebda4e38f71?w=600&h=400&fit=crop48.5 KiB45.6 KiB
Conference div.template-column > div.template-card > div.email-template > img
images.unsplash.com/photo-1517245386807-bb43f82c33c4?w=600&h=500&fit=crop51.0 KiB45.4 KiB
Success Story div.email-template > div > div > img
images.unsplash.com/photo-1552664730-d307ca884978?w=400&h=300&fit=crop26.4 KiB23.1 KiB
d3tnn7lar6ozas.cloudfront.net/324c02db-6b9b-4059-81fa-61006f2a2e9c.png10.7 KiB10.5 KiB
Smart Watch div.email-template > div > div > img
images.unsplash.com/photo-1523275335684-37898b6baf30?w=400&h=300&fit=crop10.5 KiB8.1 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 KiB7.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/email-marketing.2246e...6.0 KiB5.9 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 KiB5.8 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.png5.4 KiB5.3 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.png5.4 KiB4.9 KiB

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.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.
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

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.

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.

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.2 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: 40 ms 12.7 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

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Estimated savings: 590 ms 1.2 MiB
URLTransfer SizeEst Savings
fast.wistia.net/assets/external/E-v1.js129.5 KiB96.3 KiB
assets.aweber-static.com/www/assets/bundles/vendor.1d4983cd.js91.9 KiB91.4 KiB
assets.aweber-static.com/www/assets/bundles/vendor.1d4983cd.js91.9 KiB76.2 KiB
www.googletagmanager.com/gtag/destination?id=AW-1071267547&cx=c&gtm=4e64k0h1133.9 KiB67.1 KiB
www.googletagmanager.com/gtag/js?id=G-05FEES4HX1&cx=c&gtm=4e64k0h1178.8 KiB65.5 KiB
www.googletagmanager.com/gtag/js?id=AW-849838713&cx=c&gtm=4e64k0144.3 KiB63.0 KiB
www.googletagmanager.com/gtag/js?id=AW-849838713&cx=c&gtm=4e64k0h1144.3 KiB63.0 KiB
www.googletagmanager.com/gtag/js?id=G-FTJYCR0QMZ&cx=c&gtm=4e64k0h1146.2 KiB62.1 KiB
www.googletagmanager.com/gtag/js?id=AW-849867947&cx=c&gtm=4e64k0144.0 KiB61.6 KiB
www.googletagmanager.com/gtag/js?id=AW-849867947&cx=c&gtm=4e64k0h1143.9 KiB61.3 KiB
/gtm.js?id=GTM-5J4XPK&gtm_auth=UYNjOPXi40kADX0ZYRcuvw&gtm...177.0 KiB61.0 KiB
/gtm.js?id=GTM-5J4XPK&gtm_auth=UYNjOPXi40kADX0ZYRcuvw&gtm...177.0 KiB60.9 KiB
edge.fullstory.com/s/fs.js79.2 KiB42.2 KiB
solve-widget.forethought.ai/embed.js68.6 KiB39.7 KiB
ph.aweber.com/static/array.js61.7 KiB34.4 KiB
connect.facebook.net/en_US/fbevents.js96.5 KiB32.3 KiB
ph.aweber.com/static/array.js61.7 KiB31.7 KiB
edge.fullstory.com/s/fs.js79.2 KiB29.0 KiB
assets.aweber-static.com/www/assets/bundles/jquery.3d7b1213.js38.2 KiB26.0 KiB
assets.aweber-static.com/www/assets/bundles/jquery.3d7b1213.js38.2 KiB26.0 KiB
/signals/config/137848689911278?v=2.9.303&r=stable&domain...86.1 KiB24.0 KiB
ph.aweber.com/static/surveys.js?v=1.370.129.9 KiB23.9 KiB
ph.aweber.com/static/surveys.js?v=1.370.129.9 KiB23.9 KiB
browser.sentry-cdn.com/9.6.1/bundle.min.js24.6 KiB21.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 minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation2.1 s
Other630 ms
Style & Layout390 ms
Script Parsing & Compilation358 ms
Garbage Collection51 ms
Rendering49 ms
Parse HTML & CSS33 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 reasonFailure type
Pages with WebSocket cannot enter back/forward cache.Pending browser support

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.

Max Potential First Input Delay 100 ms
Layout shift culprits
Document request latency
Optimize DOM size
Font display
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 14 user timings
Avoid long main-thread tasks 11 long tasks found
Network Requests
Network Round Trip Times 100 ms
Server Backend Latencies 400 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 150 ms
Avoid large layout shifts 3 layout shifts found
INP breakdown
LCP request discovery
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.

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
Start Free Trial div.template-card > div.email-template > div > div
NEW BLOG POST div.template-card > div.email-template > div > div
AWARD-WINNING AGENCY div.template-card > div.email-template > div > div
$199 div > div > div > div
PRE-ORDER NOW div > div > div > div
Start Free Trial div.template-card > div.email-template > div > div
MICHELIN RATED div.template-card > div.email-template > div > div
SUCCESS STORY div > div > div > div
Read Full Story → div > div > div > div
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.

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
Workflow automation that actually works div.template-card > div.email-template > div > h3

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

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 / WarningSource
AttributionReporting
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
92

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

Performance issues directly impact user engagement and conversion rates.

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`

Send Feedback