Skip to content
Audit Complete

Results for https://duolingo.com

Visit site
Corporate / Enterprise · estimated Tracking: leads
Spain Spain · Madrid Completed: Apr 15, 2026 23:28 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 14.1s 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.

Solid SEO basics — a few optimizations could boost rankings.

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

Amazon Route 53 sites average 72
At average
Better than 29% of Amazon Route 53 sites See full Amazon Route 53 benchmark →
Apple sites average 73
At average
Better than 27% of Apple sites See full Apple 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

1 control(s) without accessible label

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

Accessibility › Form Accessibility
5

41 image(s) missing alt attribute

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

Accessibility › Alt Text Quality
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%2Fduolingo.com)](https://beavercheck.com/results/d1a0c3d7-2a24-4fad-b9ad-c2e7d0e2c0b2)
<a href="https://beavercheck.com/results/d1a0c3d7-2a24-4fad-b9ad-c2e7d0e2c0b2"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fduolingo.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fduolingo.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. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. 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.
2 accessibility issues exclude users who rely on assistive technology.

Return on Investment

€383 investment → €680/month returns + EUR 120,500,000 risk avoided

Payback period: < 1 month First-year ROI: +2032%

Investment

€383

4h · 5 findings

Monthly returns

€680 /mo

~€8,157 / year

  • Conversions recovered €679
  • Bandwidth savings €0.83

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

Payback period

0 12mo 24mo

€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

€383

4.5 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,667 / month at risk

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

Compliance Risk

€120,500,000

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

+9 more

Bandwidth Waste

€0.83 /mo

11146.5 MB/mo × 0.074 EUR/GB

  • Optimize transfer: save ~1.1 MB per page load
    Saves €0.83/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.

33
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
86
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.
100
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.

5.47 s

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

14.15 s

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

1.78 s

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

0.000

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

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

22.04 s

Detailed Report

Audit breakdown by category with detailed findings.

33

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.

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.

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.

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: div._15kfC > div._1ybpv > picture._1Bvko > img
path: 1,HTML,1,BODY,1,DIV,0,DIV,1,HEADER,1,DIV,0,DIV,0,PICTURE,2,IMG
selector: div._15kfC > div._1ybpv > picture._1Bvko > img
snippet: <img alt="" src="https://d35aaqx5ub95lt.cloudfront.net/images/splash/lottie/ded26f174e26ad1…">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
value: no origins were preconnected
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates

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.

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
div._15kfC > div._1ybpv > picture._1Bvko > img div._15kfC > div._1ybpv > picture._1Bvko > img
/images/splash/lottie/ded26f174e26ad19d0a35cad7747c28c.png89.9 KiB52.4 KiB

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

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.

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.0 s
URLTime Spent
duolingo.com/1.0 s
www.duolingo.com/0.0 ms

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

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

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.

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 Evaluation4.9 s
Other2.4 s
Style & Layout700 ms
Script Parsing & Compilation403 ms
Garbage Collection340 ms
Rendering118 ms
Parse HTML & CSS37 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
The page has an unload handler in the main frame.Actionable
Pages with cache-control:no-store header cannot enter back/forward cache.Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.Not actionable

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 13.6 KiB
URLTransfer SizeEst Savings
d35aaqx5ub95lt.cloudfront.net/css/app-12b7bcea.css16.0 KiB13.6 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
div._15kfC > div._1ybpv > picture._1Bvko > img div._15kfC > div._1ybpv > picture._1Bvko > img
/images/splash/lottie/ded26f174e26ad19d0a35cad7747c28c.png

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

Layout shift culprits
Optimize DOM size
Forced reflow
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
Avoid long main-thread tasks 20 long tasks found
Network Requests
Network Round Trip Times 100 ms
Server Backend Latencies 110 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 140 ms
INP breakdown
User Timing marks and measures
Avoid non-composited animations
Avoid large layout shifts
86

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.qO_UG > div._3CwWq > div.zKVv4 > button._38iBE div.qO_UG > div._3CwWq > div.zKVv4 > button._38iBE

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.

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
free. fun. effective. section.uU0-M > section._3k9io > div._2Yq-n > h2._3X-2C
Learning with Duolingo is fun, and research shows that it works! With quick, bi… section._3k9io > div._2Yq-n > p.KsAV5 > span
research shows that it works div._2Yq-n > p.KsAV5 > span > a._1F7oE
backed by science section.uU0-M > section._36L7f > div._2Yq-n > h2._3X-2C
We use a combination of research-backed teaching methods and delightful content… section.uU0-M > section._36L7f > div._2Yq-n > p.KsAV5
stay motivated section.uU0-M > section._3k9io > div._2Yq-n > h2._3X-2C
We make it easy to form a habit of language learning with game-like features, f… section.uU0-M > section._3k9io > div._2Yq-n > p.KsAV5
personalized learning section.uU0-M > section._36L7f > div._2Yq-n > h2._3X-2C
Combining the best of AI and language science, lessons are tailored to help you… section.uU0-M > section._36L7f > div._2Yq-n > p.KsAV5
duolingo english test div._2Yq-n > h2._3X-2C > span > span
Our convenient, fast, and affordable English test integrates the latest assessm… section._3dG3I > section._3k9io > div._2Yq-n > p.KsAV5
duolingo for schools section._3dG3I > section._36L7f > div._2Yq-n > h2._3X-2C
Teachers, we’re here to help you! Our free tools support your students as they … section._3dG3I > section._36L7f > div._2Yq-n > p.KsAV5
duolingo abc section._3dG3I > section._3k9io > div._2Yq-n > h2._3X-2C
From language to literacy! With fun phonics lessons and delightful stories, Duo… section._3dG3I > section._3k9io > div._2Yq-n > p.KsAV5
learn a language with duolingo section.F71XF > div._1fSpL > div._3qFL2 > h1._1FmL9
About us div.kWIKU > div._2zjY4 > div > div._30Vi6
Courses div > ul > li > a
Mission div > ul > li > a
Approach div > ul > li > a
Efficacy div > ul > li > a
Duolingo Handbook div > ul > li > a
Research div > ul > li > a
Careers div > ul > li > a
Brand guidelines div > ul > li > a
Store div > ul > li > a
Press div > ul > li > a
Investors div > ul > li > a
Contact us div > ul > li > a
Products div.kWIKU > div._2zjY4 > div > div._30Vi6
Duolingo div > ul > li > a
Duolingo for Schools div > ul > li > a
Duolingo English Test div > ul > li > a
Podcast div > ul > li > a
Duolingo for Business div > ul > li > a
Super Duolingo div > ul > li > a
Gift Super Duolingo div > ul > li > a
Duolingo Max div > ul > li > a
Apps div.kWIKU > div._2zjY4 > div > div._30Vi6
Duolingo for Android div > ul > li > a
Duolingo for iOS div > ul > li > a
Help and support div.kWIKU > div._2zjY4 > div > div._30Vi6
Duolingo FAQs div > ul > li > a
Schools FAQs div > ul > li > a
Duolingo English Test FAQs div > ul > li > a
Status div > ul > li > a
Privacy and terms div.kWIKU > div._2zjY4 > div > div._30Vi6
Community guidelines div > ul > li > a
Terms div > ul > li > a
Privacy div > ul > li > a
Do Not Sell or Share My Personal Information div > ul > li > a
Social div.kWIKU > div._2zjY4 > div > div._30Vi6
Blog div > ul > li > a
Instagram div > ul > li > a
TikTok div > ul > li > a
Twitter div > ul > li > a
YouTube div > ul > li > a
LinkedIn div > ul > li > a
Site language: div.qO_UG > footer._1nNuk > div.-Dahb > div._1LLyK
العربية div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
বাংলা div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
Čeština div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
Deutsch div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
Ελληνικά div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
English div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
Español div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
Français div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
हिंदी div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
Magyar div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
Bahasa Indonesia div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
Italiano div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
日本語 div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
한국어 div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
Nederlands div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
Polski div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
Português div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
Română div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
Русский div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
svenska div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
தமிழ் div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
తెలుగు div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
ภาษาไทย div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
Tagalog div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
Türkçe div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
Українською div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
Tiếng Việt div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
中文 div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
4.5 div._3CwWq > div.zKVv4 > div > span._2PsOB
Cookie Policy div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a
REJECT ALL div.ot-sdk-row > div#onetrust-button-group-parent > div#onetrust-button-group > button#onetrust-reject-all-handler
ACCEPT COOKIES div.ot-sdk-row > div#onetrust-button-group-parent > div#onetrust-button-group > button#onetrust-accept-btn-handler

These are opportunities to improve the legibility of your content.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
head > meta head > meta

These items highlight common accessibility best practices.

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
Cookie Policy div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a
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
Image elements have `[alt]` attributes
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
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links are distinguishable without relying on color.
Links have a discernible name
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.
Heading elements appear in a sequentially-descending order
Document has a main landmark.
Deprecated ARIA roles were not used
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements 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
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Form elements have associated labels
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.
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
Unload event listeners are deprecated and will be removed.

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
Failed to load resource: the server responded with a status of 404 ()
Failed to load resource: the server responded with a status of 404 ()
Failed to load resource: the server responded with a status of 404 ()
Failed to load resource: the server responded with a status of 404 ()
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
100

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Document has a meta description
Page has successful HTTP status code
Links have descriptive text
Links are crawlable
robots.txt is valid
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

54
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
86
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. — Desktop

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

1.62 s

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

4.52 s

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

264 ms

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

0.000

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

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

4.76 s

Detailed Report

Audit breakdown by category with detailed findings.

54

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.

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.

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.

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:3.891 source:map[column:34909 line:7 type:source-location url:https://cdn.cookielaw.org/scripttemplates/202404.1.0/otBannerSdk.js 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:57.302 source:map[type:text value:[unattributed]]] map[reflowTime:3.294 source:map[column:258333 line:6 type:source-location url:https://cdn.cookielaw.org/scripttemplates/202404.1.0/otBannerSdk.js urlProvider:network]] map[reflowTime:0.117 source:map[column:258677 line:6 type:source-location url:https://cdn.cookielaw.org/scripttemplates/202404.1.0/otBannerSdk.js urlProvider:network]] map[reflowTime:0.48 source:map[column:146929 line:6 type:source-location url:https://cdn.cookielaw.org/scripttemplates/202404.1.0/otBannerSdk.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:680.143 label:Time to first byte subpart:timeToFirstByte] map[duration:1874.218 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-DIV
nodeLabel: We and third parties, such as our advertising partners and service providers, u…
path: 1,HTML,1,BODY,5,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV,1,DIV
selector: div.ot-sdk-row > div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text
snippet: <div id="onetrust-policy-text">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
value: no origins were preconnected
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates

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.

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.

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: 491 ms
URLTime Spent
duolingo.com/491 ms
www.duolingo.com/0.0 ms

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

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

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.

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 Evaluation5.4 s
Style & Layout3.3 s
Other3.1 s
Rendering1.3 s
Garbage Collection122 ms
Script Parsing & Compilation121 ms
Parse HTML & CSS10.0 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
The page has an unload handler in the main frame.Actionable
Pages with cache-control:no-store header cannot enter back/forward cache.Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.Not actionable

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 13.1 KiB
URLTransfer SizeEst Savings
d35aaqx5ub95lt.cloudfront.net/css/app-12b7bcea.css16.0 KiB13.1 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
Minify JavaScript
Avoid long main-thread tasks 4 long tasks found
Image elements have explicit `width` and `height`
Network Requests
Network Round Trip Times 100 ms
Server Backend Latencies 110 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 140 ms
INP breakdown
LCP request discovery
User Timing marks and measures
Avoid non-composited animations
Avoid large layout shifts
86

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
SITE LANGUAGE: ENGLISH nav.lZqWH > div.tFegI > button._1gEmM > span._9lHjd
ENGLISH ul._399s9 > li > a._1nZQi > span._2qfTm
SPANISH ul._399s9 > li > a._1nZQi > span._2qfTm
FRENCH ul._399s9 > li > a._1nZQi > span._2qfTm
GERMAN ul._399s9 > li > a._1nZQi > span._2qfTm
ITALIAN ul._399s9 > li > a._1nZQi > span._2qfTm
PORTUGUESE ul._399s9 > li > a._1nZQi > span._2qfTm
MATH ul._399s9 > li > a._1nZQi > span._2qfTm
CHESS ul._399s9 > li > a._1nZQi > span._2qfTm
free. fun. effective. section.uU0-M > section._3k9io > div._2Yq-n > h2._3X-2C
Learning with Duolingo is fun, and research shows that it works! With quick, bi… section._3k9io > div._2Yq-n > p.KsAV5 > span
research shows that it works div._2Yq-n > p.KsAV5 > span > a._1F7oE
backed by science section.uU0-M > section._36L7f > div._2Yq-n > h2._3X-2C
We use a combination of research-backed teaching methods and delightful content… section.uU0-M > section._36L7f > div._2Yq-n > p.KsAV5
stay motivated section.uU0-M > section._3k9io > div._2Yq-n > h2._3X-2C
We make it easy to form a habit of language learning with game-like features, f… section.uU0-M > section._3k9io > div._2Yq-n > p.KsAV5
personalized learning section.uU0-M > section._36L7f > div._2Yq-n > h2._3X-2C
Combining the best of AI and language science, lessons are tailored to help you… section.uU0-M > section._36L7f > div._2Yq-n > p.KsAV5
duolingo english test div._2Yq-n > h2._3X-2C > span > span
Our convenient, fast, and affordable English test integrates the latest assessm… section._3dG3I > section._3k9io > div._2Yq-n > p.KsAV5
duolingo for schools section._3dG3I > section._36L7f > div._2Yq-n > h2._3X-2C
Teachers, we’re here to help you! Our free tools support your students as they … section._3dG3I > section._36L7f > div._2Yq-n > p.KsAV5
duolingo abc section._3dG3I > section._3k9io > div._2Yq-n > h2._3X-2C
From language to literacy! With fun phonics lessons and delightful stories, Duo… section._3dG3I > section._3k9io > div._2Yq-n > p.KsAV5
About us div.kWIKU > div._2zjY4 > div > div._30Vi6
Courses div > ul > li > a
Mission div > ul > li > a
Approach div > ul > li > a
Efficacy div > ul > li > a
Duolingo Handbook div > ul > li > a
Research div > ul > li > a
Careers div > ul > li > a
Brand guidelines div > ul > li > a
Store div > ul > li > a
Press div > ul > li > a
Investors div > ul > li > a
Contact us div > ul > li > a
Products div.kWIKU > div._2zjY4 > div > div._30Vi6
Duolingo div > ul > li > a
Duolingo for Schools div > ul > li > a
Duolingo English Test div > ul > li > a
Podcast div > ul > li > a
Duolingo for Business div > ul > li > a
Super Duolingo div > ul > li > a
Gift Super Duolingo div > ul > li > a
Duolingo Max div > ul > li > a
Apps div.kWIKU > div._2zjY4 > div > div._30Vi6
Duolingo for Android div > ul > li > a
Duolingo for iOS div > ul > li > a
Help and support div.kWIKU > div._2zjY4 > div > div._30Vi6
Duolingo FAQs div > ul > li > a
Schools FAQs div > ul > li > a
Duolingo English Test FAQs div > ul > li > a
Status div > ul > li > a
Privacy and terms div.kWIKU > div._2zjY4 > div > div._30Vi6
Community guidelines div > ul > li > a
Terms div > ul > li > a
Privacy div > ul > li > a
Do Not Sell or Share My Personal Information div > ul > li > a
Social div.kWIKU > div._2zjY4 > div > div._30Vi6
Blog div > ul > li > a
Instagram div > ul > li > a
TikTok div > ul > li > a
Twitter div > ul > li > a
YouTube div > ul > li > a
LinkedIn div > ul > li > a
Site language: div.qO_UG > footer._1nNuk > div.-Dahb > div._1LLyK
العربية div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
বাংলা div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
Čeština div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
Deutsch div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
Ελληνικά div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
English div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
Español div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
Français div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
हिंदी div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
Magyar div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
Bahasa Indonesia div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
Italiano div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
日本語 div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
한국어 div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
Nederlands div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
Polski div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
Português div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
Română div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
Русский div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
svenska div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
தமிழ் div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
తెలుగు div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
ภาษาไทย div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
Tagalog div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
Türkçe div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
Українською div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
Tiếng Việt div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
中文 div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm
Cookie Policy div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a
REJECT ALL div.ot-sdk-row > div#onetrust-button-group-parent > div#onetrust-button-group > button#onetrust-reject-all-handler
ACCEPT COOKIES div.ot-sdk-row > div#onetrust-button-group-parent > div#onetrust-button-group > button#onetrust-accept-btn-handler

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI

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

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
head > meta head > meta

These items highlight common accessibility best practices.

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
Cookie Policy div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a
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
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
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links are distinguishable without relying on color.
Links have a discernible name
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.
Heading elements appear in a sequentially-descending order
Document has a main landmark.
Deprecated ARIA roles were not used
Identical links have the same purpose.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements 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
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Form elements have associated labels
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.
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.
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
Unload event listeners are deprecated and will be removed.

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
Failed to load resource: the server responded with a status of 404 ()
Failed to load resource: the server responded with a status of 404 ()
Failed to load resource: the server responded with a status of 404 ()
Failed to load resource: the server responded with a status of 404 ()
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

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
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI
ul._399s9 > li > a._1nZQi > img._1RsYI ul._399s9 > li > a._1nZQi > img._1RsYI

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
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback