Skip to content
Audit Complete

Results for https://linktr.ee

Visit site
EE · EUR (€) · Estimated Applicable regulations: GDPR · ePrivacy Directive · EAA Dev cost: €45/hr How jurisdiction is detected
SaaS / Software · estimated Tracking: signups
Spain Spain · Madrid Completed: Apr 16, 2026 17:17 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)
C76

Site Health

Score: 76 / 100

Based on 8 categories, 0 sections

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

Good foundation, but a few gaps could be exploited.

Several issues make your site difficult for assistive technology users.

Well-optimized for search — your content is discoverable.

Solid infrastructure — fast server responses across the board.

Strong compliance posture across regulations.

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

Webflow sites average 74
At average
Better than 72% of Webflow sites See full Webflow benchmark →
Alpine.js sites average 81
At average
Better than 33% of Alpine.js sites See full Alpine.js benchmark →

Top Priorities (5)

1

Page weighs 29.2 MB (8.7 MB transferred)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Budget
2

15 link(s) with no accessible text

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

Accessibility › Link & Button Quality
3

2 control(s) without accessible label

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

Accessibility › Form Accessibility
4

32 image-only link(s) without alt text

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

Accessibility › Link & Button Quality
5

No <main> landmark found

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

Accessibility › Landmark Structure
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

0

High impact, low effort — start here.

Nothing in this quadrant — good news.

Strategic

5

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%2Flinktr.ee)](https://beavercheck.com/results/5bdd3434-1f9d-4a38-be22-c5ff7d077413)
<a href="https://beavercheck.com/results/5bdd3434-1f9d-4a38-be22-c5ff7d077413"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Flinktr.ee" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Flinktr.ee

This badge auto-updates with your latest scan result.

What fixing these means

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

Your LCP is 41.2s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.
4 accessibility issues exclude users who rely on assistive technology.

Conversion Barriers

3 critical 5 warning

8 barrier(s) likely increasing bounce by ~32%.

Speed (2)

Page takes 41.2s to load

+12% bounce

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

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

Page feels frozen for 26.1s

+5% bounce

Clicks on the primary CTA are ignored while JavaScript runs

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

Trust (2)

No HSTS header

+1% bounce

Returning visitors are briefly exposed to downgrade attacks on first request

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

No Content-Security-Policy header

+1% bounce

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

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

Usability (1)

2 form field(s) without a label

+4% bounce

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

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

Navigation (3)

15 link(s) with generic text ("click here", "read more")

+1% bounce

Screen-reader users navigating by link list see no context — and search engines can't infer relevance

Fix: Rewrite with descriptive phrases that identify the destination

No skip-to-content link

+1% bounce

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

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

5 broken link(s) on the page

+5% bounce

Clicks land on 404s — trust drops and the session often ends

Fix: Fix or remove the broken destinations surfaced on the Content tab

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

Return on Investment

€360 investment → €2.03/month returns + EUR 20,500,000 risk avoided

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

Investment

€360

8h · 5 findings

Monthly returns

€2.03 /mo

~€24 / year

  • Bandwidth savings €2.03

Regulatory risk avoided

EUR 20,500,000

if kept compliant

  • GDPR EUR 20,000,000
  • EAA EUR 500,000

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

€360

8.0 developer hours at €45/hr

Based on Estonia rates (€45/hr)

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

€1,708,335 / month at risk

~€20,500,024 / year if left unfixed

Compliance Risk

€20,500,000

GDPREAA
  • Privacy Policy not detected
    GDPR: EUR 10,000 – EUR 20,000,000
  • No <main> landmark found
    EAA: EUR 1,000 – EUR 500,000
  • 1 of 3 <nav> elements are unlabeled
    EAA: EUR 1,000 – EUR 500,000

+4 more

Bandwidth Waste

€2.03 /mo

27419.9 MB/mo × 0.074 EUR/GB

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

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

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

41.23 s

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

26.08 s

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

0.013

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

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

42.91 s

Detailed Report

Audit breakdown by category with detailed findings.

26

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.

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
div.container > div._w-img_large > div.img-100 > video#customize-your-linktree div.container > div._w-img_large > div.img-100 > video#customize-your-linktree
/666255f7f2126f4e8cec6f8f/692eb9b488731835c528bb18_captur...63.7 KiB56.2 KiB
div#swiper-wrapper-ffe7f11097426f171 > a.swiper-slide > div._w-slide-img > img.slider-img div#swiper-wrapper-ffe7f11097426f171 > a.swiper-slide > div._w-slide-img > img.slider-img
/666255f7f2126f4e8cec6f8f/66634cb2449d48431e9377da_tonyha...36.3 KiB28.2 KiB
div#swiper-wrapper-ffe7f11097426f171 > a.swiper-slide > div._w-slide-img > img.slider-img div#swiper-wrapper-ffe7f11097426f171 > a.swiper-slide > div._w-slide-img > img.slider-img
/666255f7f2126f4e8cec6f8f/66634cb2449d48431e937786_funkyn...30.5 KiB23.7 KiB
div#swiper-wrapper-ffe7f11097426f171 > a.swiper-slide > div._w-slide-img > img.slider-img div#swiper-wrapper-ffe7f11097426f171 > a.swiper-slide > div._w-slide-img > img.slider-img
/666255f7f2126f4e8cec6f8f/66634cb1449d48431e9376d8_pharre...28.1 KiB21.8 KiB
div#swiper-wrapper-ffe7f11097426f171 > a.swiper-slide > div._w-slide-img > img.slider-img div#swiper-wrapper-ffe7f11097426f171 > a.swiper-slide > div._w-slide-img > img.slider-img
/666255f7f2126f4e8cec6f8f/66634cb2449d48431e9377ba_selena...24.7 KiB17.3 KiB

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:31.119 label:Time to first byte subpart:timeToFirstByte] map[duration:12050.235 label:Element render delay subpart:elementRenderDelay]]
lhId: page-5-image
nodeLabel: svg > g > g#602 > image
path: 2,HTML,1,BODY,2,DIV,0,SECTION,0,DIV,1,DIV,0,DIV,0,DIV,7,DIV,0,DIV,0,DIV,0,svg,1,g,3,g,0,image
selector: svg > g > g#602 > image
snippet: <image width="800px" height="800px" preserveAspectRatio="xMidYMid slice" xlink:href="data:image/webp;base64,UklGRvpqAQBXRUJQVlA4IO5qAQAQXgWdASogAyADPm0wk0ekIqQ…">

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.2 s 123.7 KiB
URLTransfer SizeEst Savings
/666255f7f2126f4e8cec6f8f/css/marketing-sub-pages-s.share...133.9 KiB123.7 KiB

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

Why this matters

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

Learn more

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

Source: Google web.dev / Lighthouse

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 Evaluation22.3 s
Other14.4 s
Style & Layout811 ms
Rendering638 ms
Script Parsing & Compilation619 ms
Garbage Collection495 ms
Parse HTML & CSS109 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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 26.6 KiB
URLTransfer SizeEst Savings
unpkg.com/@rive-app/canvas@latest64.6 KiB26.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
Analyze your audience and keep them engaged div._w-img_large > div.img-100 > picture > img
/666255f7f2126f4e8cec6f8f/68b806bb5feb04097bb7d791_home-s...
div.navbar > div.nav-container > a.nav-logo > img.nav-tablet-mobile-logo div.navbar > div.nav-container > a.nav-logo > img.nav-tablet-mobile-logo
/666255f7f2126f4e8cec6f8f/666b48ad59add9f2777bb76f_downlo...
a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon
/666255f7f2126f4e8cec6f8f/66634cb2449d48431e937810_SVG.svg
a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon
/666255f7f2126f4e8cec6f8f/66634cb2449d48431e937810_SVG.svg
a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon
/666255f7f2126f4e8cec6f8f/66634cb2449d48431e937810_SVG.svg
a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon
/666255f7f2126f4e8cec6f8f/66634cb2449d48431e937810_SVG.svg
a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon
/666255f7f2126f4e8cec6f8f/66634cb2449d48431e937810_SVG.svg
a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon
/666255f7f2126f4e8cec6f8f/66634cb2449d48431e937810_SVG.svg
a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon
/666255f7f2126f4e8cec6f8f/66634cb2449d48431e937810_SVG.svg

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

Layout shift culprits
Document request latency
Optimize DOM size
Modern HTTP
Optimize viewport for mobile
Minify CSS
User Timing marks and measures 5 user timings
Avoid long main-thread tasks 20 long tasks found
Network Requests
Network Round Trip Times 180 ms
Server Backend Latencies 710 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Avoid multiple page redirects
Initial server response time was short Root document took 20 ms
Avoid large layout shifts 1 layout shift found
INP breakdown
LCP request discovery
Avoid non-composited animations
89

Accessibility

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

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
creators influencers small businesses athletes models monetizers health educato… section.trusted-by > div._w-scrolling-heading > div.swiper > div#swiper-wrapper-9219c5bde34181ae

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Why should podcasters use Linktree? div.faq-item > div.faq-head > div.q-wrapper > h4.faq-question

These are opportunities to improve keyboard navigation in your application.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div._w-footer-bottom > div._w-footer-right-col-links > div._w-app-links > a.button div._w-footer-bottom > div._w-footer-right-col-links > div._w-app-links > a.button
div._w-footer-bottom > div._w-footer-right-col-links > div._w-app-links > a.button div._w-footer-bottom > div._w-footer-right-col-links > div._w-app-links > a.button
div._w-footer-right-col-links > div._w-social-icons > div._w-social-links > a.footer-app-social-link div._w-footer-right-col-links > div._w-social-icons > div._w-social-links > a.footer-app-social-link
div._w-footer-right-col-links > div._w-social-icons > div._w-social-links > a.footer-app-social-link div._w-footer-right-col-links > div._w-social-icons > div._w-social-links > a.footer-app-social-link
div._w-footer-right-col-links > div._w-social-icons > div._w-social-links > a.footer-app-social-link div._w-footer-right-col-links > div._w-social-icons > div._w-social-links > a.footer-app-social-link
div._w-footer-right-col-links > div._w-social-icons > div._w-social-links > a.footer-app-social-link div._w-footer-right-col-links > div._w-social-icons > div._w-social-links > a.footer-app-social-link

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Best practices

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.w-mod-js html.w-mod-js

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
English div.dg-app > div > div.dg-main-language-dropdown > button.language-dropdown-trigger
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
Input buttons have discernible text.
Form elements have associated labels
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Background and foreground colors have a sufficient contrast ratio
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
Deprecated ARIA roles were not used
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Uses ARIA roles only on compatible elements
`[accesskey]` values are unique
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
`[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 type="image">` elements have `[alt]` text
Links are distinguishable without relying on color.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
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
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
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
Access to fetch at 'https://api-sr.amplitude.com/sessions/v2/track?device_id=cc0e4eea-0e6d-5f28-88c3-66b4e7d40fb6&session_id=1776359743336&type=replay' from origin 'https://linktr.ee' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Access to fetch at 'https://api-sr.amplitude.com/sessions/v2/track?device_id=cc0e4eea-0e6d-5f28-88c3-66b4e7d40fb6&session_id=1776359743336&type=replay' from origin 'https://linktr.ee' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
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

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

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

1.08 s

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

6.21 s

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

2.97 s

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

0.012

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

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

7.88 s

Detailed Report

Audit breakdown by category with detailed findings.

39

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.

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.

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.container > div._w-img_large > div.img-100 > video#customize-your-linktree div.container > div._w-img_large > div.img-100 > video#customize-your-linktree
/666255f7f2126f4e8cec6f8f/692eb9b488731835c528bb18_captur...63.7 KiB54.9 KiB
div#swiper-wrapper-d56418a62e05d242 > a.swiper-slide > div._w-slide-img > img.slider-img div#swiper-wrapper-d56418a62e05d242 > a.swiper-slide > div._w-slide-img > img.slider-img
/666255f7f2126f4e8cec6f8f/66634cb2449d48431e9377da_tonyha...54.4 KiB40.4 KiB
div#swiper-wrapper-d56418a62e05d242 > a.swiper-slide > div._w-slide-img > img.slider-img div#swiper-wrapper-d56418a62e05d242 > a.swiper-slide > div._w-slide-img > img.slider-img
/666255f7f2126f4e8cec6f8f/66634cb2449d48431e937786_funkyn...45.5 KiB37.9 KiB
div#swiper-wrapper-d56418a62e05d242 > a.swiper-slide > div._w-slide-img > img.slider-img div#swiper-wrapper-d56418a62e05d242 > a.swiper-slide > div._w-slide-img > img.slider-img
/666255f7f2126f4e8cec6f8f/66634cb1449d48431e9376d8_pharre...39.9 KiB33.2 KiB
div#swiper-wrapper-d56418a62e05d242 > a.swiper-slide > div._w-slide-img > img.slider-img div#swiper-wrapper-d56418a62e05d242 > a.swiper-slide > div._w-slide-img > img.slider-img
/666255f7f2126f4e8cec6f8f/66634cb2449d48431e9377ba_selena...37.9 KiB31.5 KiB
Analyze your audience and keep them engaged div._w-img_large > div.img-100 > picture > img
/666255f7f2126f4e8cec6f8f/68b80693934ab0ccd4bf7482_home-s...33.9 KiB28.3 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

Reduce unused 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: 100 ms 126.9 KiB
URLTransfer SizeEst Savings
/666255f7f2126f4e8cec6f8f/css/marketing-sub-pages-s.share...133.9 KiB126.9 KiB

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

Why this matters

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

Learn more

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

Source: Google web.dev / Lighthouse

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 Evaluation3.9 s
Other2.1 s
Style & Layout227 ms
Script Parsing & Compilation154 ms
Rendering134 ms
Garbage Collection103 ms
Parse HTML & CSS30 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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 26.6 KiB
URLTransfer SizeEst Savings
unpkg.com/@rive-app/canvas@latest64.6 KiB26.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
Analyze your audience and keep them engaged div._w-img_large > div.img-100 > picture > img
/666255f7f2126f4e8cec6f8f/68b80693934ab0ccd4bf7482_home-s...
Photo of David Coleman, Founder div.swiper > div#swiper-wrapper-6e961610e7f332a58 > div.swiper-slide > img.testimonial-img
/666255f7f2126f4e8cec6f8f/66864533e85838c661396b01_Testim...
Photo of Riley Lemon, creator div.swiper > div#swiper-wrapper-6e961610e7f332a58 > div.swiper-slide > img.testimonial-img
/666255f7f2126f4e8cec6f8f/66864533566fcb42ef955aad_Testim...
Photo of David Coleman, Founder div.swiper > div#swiper-wrapper-6e961610e7f332a58 > div.swiper-slide > img.testimonial-img
/666255f7f2126f4e8cec6f8f/66864533e85838c661396b01_Testim...
Photo of Riley Lemon, creator div.swiper > div#swiper-wrapper-6e961610e7f332a58 > div.swiper-slide > img.testimonial-img
/666255f7f2126f4e8cec6f8f/66864533566fcb42ef955aad_Testim...
div.navbar > div.nav-container > a.nav-logo > img.nav-desktop-logo div.navbar > div.nav-container > a.nav-logo > img.nav-desktop-logo
/666255f7f2126f4e8cec6f8f/66634daccb34e6d65a41c76d_downlo...
a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon
/666255f7f2126f4e8cec6f8f/66634cb2449d48431e937810_SVG.svg
a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon
/666255f7f2126f4e8cec6f8f/66634cb2449d48431e937810_SVG.svg
a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon
/666255f7f2126f4e8cec6f8f/66634cb2449d48431e937810_SVG.svg
a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon
/666255f7f2126f4e8cec6f8f/66634cb2449d48431e937810_SVG.svg
a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon
/666255f7f2126f4e8cec6f8f/66634cb2449d48431e937810_SVG.svg
a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon
/666255f7f2126f4e8cec6f8f/66634cb2449d48431e937810_SVG.svg
a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon
/666255f7f2126f4e8cec6f8f/66634cb2449d48431e937810_SVG.svg
a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon
/666255f7f2126f4e8cec6f8f/66634cb2449d48431e937810_SVG.svg
a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon
/666255f7f2126f4e8cec6f8f/66634cb2449d48431e937810_SVG.svg
a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon
/666255f7f2126f4e8cec6f8f/66634cb2449d48431e937810_SVG.svg
a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon
/666255f7f2126f4e8cec6f8f/66634cb2449d48431e937810_SVG.svg
a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon
/666255f7f2126f4e8cec6f8f/66634cb2449d48431e937810_SVG.svg
a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon
/666255f7f2126f4e8cec6f8f/66634cb2449d48431e937810_SVG.svg
a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon
/666255f7f2126f4e8cec6f8f/66634cb2449d48431e937810_SVG.svg
a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon
/666255f7f2126f4e8cec6f8f/66634cb2449d48431e937810_SVG.svg
a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon
/666255f7f2126f4e8cec6f8f/66634cb2449d48431e937810_SVG.svg
a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon
/666255f7f2126f4e8cec6f8f/66634cb2449d48431e937810_SVG.svg
a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon
/666255f7f2126f4e8cec6f8f/66634cb2449d48431e937810_SVG.svg
a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon
/666255f7f2126f4e8cec6f8f/66634cb2449d48431e937810_SVG.svg
a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon
/666255f7f2126f4e8cec6f8f/66634cb2449d48431e937810_SVG.svg
a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon a.swiper-slide > div._w-slide-pill-link > div.slider-link-pill > img.card-pill-link-icon
/666255f7f2126f4e8cec6f8f/66634cb2449d48431e937810_SVG.svg
Photo of Patti Chimkire, Founder and Pastry Chef div.swiper > div#swiper-wrapper-6e961610e7f332a58 > div.swiper-slide > img.testimonial-img
Photo of Luke Kidgell, Comedian div.swiper > div#swiper-wrapper-6e961610e7f332a58 > div.swiper-slide > img.testimonial-img

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

Layout shift culprits
Document request latency
Optimize DOM size
Forced reflow
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
User Timing marks and measures 5 user timings
Avoid long main-thread tasks 19 long tasks found
Network Requests
Network Round Trip Times 170 ms
Server Backend Latencies 380 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Avoid multiple page redirects
Initial server response time was short Root document took 20 ms
Avoid large layout shifts 3 layout shifts found
INP breakdown
LCP request discovery
Avoid non-composited animations
89

Accessibility

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

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
creators influencers small businesses athletes models monetizers health educato… section.trusted-by > div._w-scrolling-heading > div.swiper > div#swiper-wrapper-1016fe0b593e96ce0

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Why should podcasters use Linktree? div.faq-item > div.faq-head > div.q-wrapper > h4.faq-question

These are opportunities to improve keyboard navigation in your application.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div._w-footer-bottom > div._w-footer-right-col-links > div._w-app-links > a.button div._w-footer-bottom > div._w-footer-right-col-links > div._w-app-links > a.button
div._w-footer-bottom > div._w-footer-right-col-links > div._w-app-links > a.button div._w-footer-bottom > div._w-footer-right-col-links > div._w-app-links > a.button
div._w-footer-right-col-links > div._w-social-icons > div._w-social-links > a.footer-app-social-link div._w-footer-right-col-links > div._w-social-icons > div._w-social-links > a.footer-app-social-link
div._w-footer-right-col-links > div._w-social-icons > div._w-social-links > a.footer-app-social-link div._w-footer-right-col-links > div._w-social-icons > div._w-social-links > a.footer-app-social-link
div._w-footer-right-col-links > div._w-social-icons > div._w-social-links > a.footer-app-social-link div._w-footer-right-col-links > div._w-social-icons > div._w-social-links > a.footer-app-social-link
div._w-footer-right-col-links > div._w-social-icons > div._w-social-links > a.footer-app-social-link div._w-footer-right-col-links > div._w-social-icons > div._w-social-links > a.footer-app-social-link

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Best practices

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.w-mod-js html.w-mod-js

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
English div.dg-app > div > div.dg-main-language-dropdown > button.language-dropdown-trigger
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
Input buttons have discernible text.
Form elements have associated labels
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Background and foreground colors have a sufficient contrast ratio
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
Deprecated ARIA roles were not used
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Uses ARIA roles only on compatible elements
`[accesskey]` values are unique
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
`[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 type="image">` elements have `[alt]` text
Links are distinguishable without relying on color.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
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
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
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 413 ()
Failed to load resource: the server responded with a status of 413 ()
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`

Send Feedback