C — https://babbel.com | BeaverCheck Audit

Site Health

Score: 76 / 100

Based on 8 categories, 0 sections

Decent speed, but optimizing further could improve engagement.

Several missing protections leave your users and data exposed.

Mostly accessible, but some users still face barriers.

Well-optimized for search — your content is discoverable.

Solid infrastructure — fast server responses across the board.

Mostly compliant — a few items need attention.

Good content signals with minor gaps.

Reasonable footprint with room for optimization.

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

Contentful sites average 73

At average

Better than 68% of Contentful sites See full Contentful benchmark →

Amazon Route 53 sites average 72

At average

Better than 80% of Amazon Route 53 sites See full Amazon Route 53 benchmark →

Top Priorities (5)

Content-Security-Policy header is missing

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

Security › Security Headers

HSTS header is missing

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

Security › Security Headers

No Content-Security-Policy header found

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

Security › Content Security Policy

56 third-party resources (100% of weight)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Inventory

Cross-Origin-Embedder-Policy header is missing

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

Security › Security Headers

View fix priority matrix

Fix Priority Matrix

5 findings

Impact

Quick Wins

High impact, low effort — start here.

Strategic

High impact, requires investment.

Easy Improvements

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fbabbel.com)](https://beavercheck.com/results/7c743242-f06f-4be7-90c1-2cc96c2420a1)

HTML

<a href="https://beavercheck.com/results/7c743242-f06f-4be7-90c1-2cc96c2420a1"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fbabbel.com" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fbabbel.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. The 1 performance issue below shapes how fast users perceive your page. Addressing the critical issues below would have the most immediate impact on your user trust.

4 security gaps detected — browsers may warn visitors about your site.

1 performance issue — Akamai's research found 53% of mobile users abandon pages over 3s.

Return on Investment

€340 investment → €0.52/month returns + EUR 120,500,000 risk avoided

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

Investment

€340

4h · 5 findings

Monthly returns

€0.52 /mo

~€6.22 / year

Bandwidth savings €0.52

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

€170 — 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

€340

4.0 developer hours at €85/hr

Based on European Union rates (€85/hr)

Quick wins

€170 4 fixes in ~120 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions

Custom rate

€ /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,006 / 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

+4 more

Bandwidth Waste

€0.52 /mo

6995.3 MB/mo × 0.074 EUR/GB

Optimize transfer: save ~700 KB per page load
Saves €0.52/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

Was this report useful?

Thanks for your feedback!

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

Checking for existing audit...

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

100

Best Practices

SEO

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.04 s

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

0 ms

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

0 ms

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

0.005

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

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

0 ms

Detailed Report

Audit breakdown by category with detailed findings.

—

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

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.

Request	Cache TTL	Transfer Size
/fonts/feature-text-lc-regular-italic-f09b8140b1bac8faf4e...	0.0 ms	86.1 KiB
/fonts/feature-text-lc-regular-0dde0d520ae12ba873bf5f4b59...	0.0 ms	82.8 KiB
/fonts/graphik-babbel-lcg-semibold-77c8d3f48eb4a9b0d89e78...	0.0 ms	54.7 KiB
/fonts/graphik-babbel-lcg-regular-4c04ca457245d20e7c0ccf6...	0.0 ms	51.1 KiB
cdn.cookielaw.org/scripttemplates/202501.2.0/otBannerSdk.js	86400.0 s	114.5 KiB
cdn.speedcurve.com/js/lux.es2020.js?id=295968638	3600.0 s	10.8 KiB
/logos/1564af4b-0fa8-4702-befe-a6eb2a868167/4654ed09-02d6...	86400.0 s	9.5 KiB
cdn.cookielaw.org/scripttemplates/otSDKStub.js	86400.0 s	9.1 KiB
cdn.cookielaw.org/logos/static/powered_by_logo.svg	86400.0 s	2.6 KiB
wt.babbel.com/ec/ec.js	86400.0 s	2.0 KiB
wt.babbel.com/wt/web-tools.cjs	86400.0 s	1.9 KiB
wt.babbel.com/mt/mt.cjs	86400.0 s	1.8 KiB
wt.babbel.com/gtm/gtm.js	86400.0 s	1.8 KiB
wt.babbel.com/cm/cm.js	86400.0 s	1.3 KiB

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
Two girls having breakfast while sitting at a table in the street of a European… `div > article > div.sc-9ce78922-0 > img.sc-a2f4c4bd-0`	/_next/image?url=https%3A%2F%2Fimages.ctfassets.net%2Fzuz...	262.1 KiB	223.0 KiB
A diverse group of people engaged in a relaxed conversation while sitting aroun… `header.sc-22a02f37-0 > div#3R2gHlyyn5YhCDqpM1oFqs > div.sc-9ce78922-0 > img.sc-a2f4c4bd-0`	/_next/image?url=https%3A%2F%2Fimages.ctfassets.net%2Fzuz...	172.9 KiB	152.2 KiB
A girl sitting comfortably on the couch while engaging with her device. `div > article > div.sc-9ce78922-0 > img.sc-a2f4c4bd-0`	/_next/image?url=https%3A%2F%2Fimages.ctfassets.net%2Fzuz...	129.1 KiB	109.9 KiB
body > div#onetrust-consent-sdk > div#onetrust-banner-sdk > ::before `body > div#onetrust-consent-sdk > div#onetrust-banner-sdk > ::before`	/api/v1/image/assets/5e04d7f833e7490c8aeee8378a31a44c/299...	132.0 KiB	85.9 KiB
An individual checking the Babbel app on their device. `div > article > div.sc-9ce78922-0 > img.sc-a2f4c4bd-0`	/_next/image?url=https%3A%2F%2Fimages.ctfassets.net%2Fzuz...	97.2 KiB	82.7 KiB

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
wt.babbel.com/wt/web-tools.cjs	1.9 KiB

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.

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

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

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

Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasks

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reason	Failure type
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
Unattributable	487 ms	182 ms	0.0 ms
www.babbel.com/edge/?id=GTM-MDD3PT	374 ms	309 ms	60 ms
/ebb938fae15463c06bab6135f2cf31c4e979b032/_next/static/ch...	351 ms	302 ms	25 ms
www.babbel.com/	307 ms	7.6 ms	1.7 ms
cdn.cookielaw.org/scripttemplates/202501.2.0/otBannerSdk.js	247 ms	148 ms	41 ms
/ebb938fae15463c06bab6135f2cf31c4e979b032/_next/static/ch...	124 ms	82 ms	41 ms
/ebb938fae15463c06bab6135f2cf31c4e979b032/_next/static/ch...	98 ms	88 ms	0.8 ms
/ebb938fae15463c06bab6135f2cf31c4e979b032/_next/static/ch...	79 ms	65 ms	12 ms
wt.babbel.com/wt/web-tools.cjs	65 ms	61 ms	1.9 ms

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Script Evaluation	1.3 s
Other	364 ms
Style & Layout	278 ms
Script Parsing & Compilation	231 ms
Parse HTML & CSS	46 ms
Rendering	35 ms
Garbage Collection	16 ms

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

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●Modern HTTP

●Network dependency tree

●Optimize viewport for mobile

●Avoids enormous network payloads Total size was 2,277 KiB

●User Timing marks and measures 4 user timings

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

●Network Requests

●Network Round Trip Times 40 ms

●Server Backend Latencies 370 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP breakdown

○LCP request discovery

○Avoid non-composited animations

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Over 25 million subscriptions sold! `div.sc-9ce78922-0 > div.sc-9ce78922-0 > div.sc-fa6f4619-0 > span.sc-e1b36bdc-0`

These are opportunities to improve the legibility of your content.

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
Privacy Statement `div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link`

○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

●`[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 with `role="dialog"` or `role="alertdialog"` have accessible names.

●`[aria-hidden="true"]` elements do not contain focusable descendents

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

100

Best Practices

General

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

●Uses HTTPS

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Mitigate clickjacking with XFO or CSP

SEO

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

Content Best Practices

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destination	Link Text
my.babbel.com/en/onboarding/default	More
support.babbel.com/hc/en-us/articles/205600528-Benefits-of-learning-with-Babbel	here
my.babbel.com/en/onboarding/default	More
cookiepedia.co.uk/giving-consent-to-cookies	More information

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

Performance

Accessibility

100

Best Practices

SEO

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.

806 ms

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

0 ms

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

0 ms

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

0.046

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

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

0 ms

Detailed Report

Audit breakdown by category with detailed findings.

—

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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 ▾

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.

Request	Cache TTL	Transfer Size
/fonts/feature-text-lc-regular-italic-f09b8140b1bac8faf4e...	0.0 ms	86.1 KiB
/fonts/feature-text-lc-regular-0dde0d520ae12ba873bf5f4b59...	0.0 ms	82.8 KiB
/fonts/graphik-babbel-lcg-semibold-77c8d3f48eb4a9b0d89e78...	0.0 ms	54.7 KiB
/fonts/graphik-babbel-lcg-regular-4c04ca457245d20e7c0ccf6...	0.0 ms	51.1 KiB
cdn.cookielaw.org/scripttemplates/202501.2.0/otBannerSdk.js	86400.0 s	114.5 KiB
cdn.speedcurve.com/js/lux.es2020.js?id=295968638	3600.0 s	10.8 KiB
/logos/1564af4b-0fa8-4702-befe-a6eb2a868167/4654ed09-02d6...	86400.0 s	9.5 KiB
cdn.cookielaw.org/scripttemplates/otSDKStub.js	86400.0 s	9.1 KiB
cdn.cookielaw.org/logos/static/powered_by_logo.svg	86400.0 s	2.6 KiB
wt.babbel.com/ec/ec.js	86400.0 s	2.0 KiB
wt.babbel.com/wt/web-tools.cjs	86400.0 s	1.9 KiB
wt.babbel.com/mt/mt.cjs	86400.0 s	1.8 KiB
wt.babbel.com/gtm/gtm.js	86400.0 s	1.8 KiB
wt.babbel.com/cm/cm.js	86400.0 s	1.3 KiB

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
Two girls having breakfast while sitting at a table in the street of a European… `div > article > div.sc-9ce78922-0 > img.sc-a2f4c4bd-0`	/_next/image?url=https%3A%2F%2Fimages.ctfassets.net%2Fzuz...	262.1 KiB	247.7 KiB
A diverse group of people engaged in a relaxed conversation while sitting aroun… `header.sc-22a02f37-0 > div#3R2gHlyyn5YhCDqpM1oFqs > div.sc-9ce78922-0 > img.sc-a2f4c4bd-0`	/_next/image?url=https%3A%2F%2Fimages.ctfassets.net%2Fzuz...	172.9 KiB	154.5 KiB
A girl sitting comfortably on the couch while engaging with her device. `div > article > div.sc-9ce78922-0 > img.sc-a2f4c4bd-0`	/_next/image?url=https%3A%2F%2Fimages.ctfassets.net%2Fzuz...	129.1 KiB	122.0 KiB
An individual checking the Babbel app on their device. `div > article > div.sc-9ce78922-0 > img.sc-a2f4c4bd-0`	/_next/image?url=https%3A%2F%2Fimages.ctfassets.net%2Fzuz...	97.2 KiB	91.8 KiB
body > div#onetrust-consent-sdk > div#onetrust-banner-sdk > ::before `body > div#onetrust-consent-sdk > div#onetrust-banner-sdk > ::before`	/api/v1/image/assets/5e04d7f833e7490c8aeee8378a31a44c/299...	132.0 KiB	85.9 KiB
div.sc-9ce78922-0 > ul.sc-9ce78922-0 > li.sc-9ce78922-0 > img.sc-a2f4c4bd-0 `div.sc-9ce78922-0 > ul.sc-9ce78922-0 > li.sc-9ce78922-0 > img.sc-a2f4c4bd-0`	/_next/image?url=https%3A%2F%2Fimages.ctfassets.net%2Fzuz...	79.7 KiB	66.8 KiB
div.sc-9ce78922-0 > ul.sc-9ce78922-0 > li.sc-9ce78922-0 > img.sc-a2f4c4bd-0 `div.sc-9ce78922-0 > ul.sc-9ce78922-0 > li.sc-9ce78922-0 > img.sc-a2f4c4bd-0`	/_next/image?url=https%3A%2F%2Fimages.ctfassets.net%2Fzuz...	36.4 KiB	33.1 KiB

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
wt.babbel.com/wt/web-tools.cjs	1.9 KiB

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.

Diagnostics

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

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

Learn more ▾

Source: Google web.dev / Lighthouse

Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasks

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reason	Failure type
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable

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

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●Modern HTTP

●Network dependency tree

●Optimize viewport for mobile

●Max Potential First Input Delay 50 ms

●Avoids enormous network payloads Total size was 2,410 KiB

●User Timing marks and measures 4 user timings

●JavaScript execution time 0.3 s

●Minimizes main-thread work 0.7 s

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

●Network Requests

●Network Round Trip Times 40 ms

●Server Backend Latencies 100 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

○LCP breakdown

○LCP request discovery

○Avoid non-composited animations

Accessibility

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
Sign up `ul.sc-9ce78922-0 > li.sc-92b30a8e-0 > a.sc-272f9ffd-0 > span.sc-e1b36bdc-0`
Over 25 million subscriptions sold! `div.sc-9ce78922-0 > div.sc-9ce78922-0 > div.sc-fa6f4619-0 > span.sc-e1b36bdc-0`

These are opportunities to improve the legibility of your content.

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
Privacy Statement `div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link`

○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

●`[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 with `role="dialog"` or `role="alertdialog"` have accessible names.

●`[aria-hidden="true"]` elements do not contain focusable descendents

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

100

Best Practices

General

Why this matters

Performance issues directly impact user engagement and conversion rates.

●Uses HTTPS

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Mitigate clickjacking with XFO or CSP

SEO

Content Best Practices

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destination	Link Text
my.babbel.com/en/onboarding/default	More
support.babbel.com/hc/en-us/articles/205600528-Benefits-of-learning-with-Babbel	here
my.babbel.com/en/onboarding/default	More
cookiepedia.co.uk/giving-consent-to-cookies	More information

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

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Results for https://babbel.com

Site Health

How you compare

Top Priorities (5)

Fix Priority Matrix

Quick Wins

Strategic

Easy Improvements

Deprioritize

What fixing these means

Return on Investment

Investment

Monthly returns

Regulatory risk avoided

Estimated Remediation Cost

Cost by category

Cost by effort level

What Inaction Is Costing You

Compliance Risk

Bandwidth Waste

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Contrast

Best Practices

General

SEO

Content Best Practices

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Contrast

Best Practices

General

SEO

Content Best Practices

Keyboard Shortcuts