Skip to content
Audit Complete

Results for https://www.allbirds.eu

Visit site
Spain Spain · Madrid Completed: Apr 6, 2026 15:09 UTC

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

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

Site Health

Score: 74 / 100

Based on 8 categories, 0 sections

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.

Top Priorities (5)

1

Page weighs 13.3 MB (5.6 MB transferred)

Performance › Page Weight Budget
2

10 image-in-link without alt text

Accessibility › Alt Text Quality
3

16 image(s) missing alt attribute

Accessibility › Alt Text Quality
4

16 link(s) with no accessible text

Accessibility › Link & Button Quality
5

5 image-only link(s) without alt text

Accessibility › Link & Button Quality
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.allbirds.eu)](https://beavercheck.com/results/2b7e29ab-bab9-4753-9c60-f992f517a51c)
<a href="https://beavercheck.com/results/2b7e29ab-bab9-4753-9c60-f992f517a51c"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.allbirds.eu" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fwww.allbirds.eu

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

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

Core Web Vitals

Key metrics that affect user experience.

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

5.69 s

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

20.06 s

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

1.36 s

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

0.000

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

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

20.39 s

Detailed Report

Audit breakdown by category with detailed findings.

33

Performance

Insights

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

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

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

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

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.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:10.365 source:map[column:150 line:2591 type:source-location url:https://allbirds.de/ urlProvider:network]] map[reflowTime:57.025 source:map[column:2632 line:164 type:source-location url:https://allbirds.de/cdn/shop/t/5/assets/theme.js?v=86044763260100624921774876360 urlProvider:network]] map[reflowTime:10.025 source:map[column:4766 line:12 type:source-location url:https://cdn.jsdelivr.net/npm/swiper@11/swiper-bundle.min.js urlProvider:network]] map[reflowTime:19.229 source:map[column:56906 line:12 type:source-location url:https://cdn.jsdelivr.net/npm/swiper@11/swiper-bundle.min.js urlProvider:network]] map[reflowTime:8.058 source:map[column:10640 line:12 type:source-location url:https://cdn.jsdelivr.net/npm/swiper@11/swiper-bundle.min.js urlProvider:network]]]

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

URLResource SizeEst Savings
div#media-grid-image_VCLLwh > a.content-over-media > picture > img.content-over-media__media div#media-grid-image_VCLLwh > a.content-over-media > picture > img.content-over-media__media
allbirds.de/cdn/shop/files/AB_Waterproof_Teaser.png?v=1774436644&width=800373.3 KiB269.8 KiB
div#media-grid-image_mPMcbf > a.content-over-media > picture > img.content-over-media__media div#media-grid-image_mPMcbf > a.content-over-media > picture > img.content-over-media__media
allbirds.de/cdn/shop/files/AB_Terralux.png?v=1772545691&width=800222.9 KiB119.4 KiB
div#media-grid-image_TK6AYM > a.content-over-media > picture > img.content-over-media__media div#media-grid-image_TK6AYM > a.content-over-media > picture > img.content-over-media__media
/cdn/shop/files/AB_Dasher_NZ_43fdeafd-5987-4510-a5a1-de16...202.8 KiB99.3 KiB
div#block-image_rCP7ha > div#slide-template--19445889171702__slideshow_zep4yQ-image_rCP7ha > picture > img div#block-image_rCP7ha > div#slide-template--19445889171702__slideshow_zep4yQ-image_rCP7ha > picture > img
allbirds.de/cdn/shop/files/AB_Hero_Varsity_Mobile.jpg?v=1772541563&width=800183.9 KiB99.3 KiB
div.relative > button.text-with-icon > div.h-stack > span.country-flags div.relative > button.text-with-icon > div.h-stack > span.country-flags
/cdn/shop/t/5/assets/country-flags-2x.png?v=1193884466821...173.4 KiB95.3 KiB
div#media-grid-image_hY6eEt > a.content-over-media > picture > img.content-over-media__media div#media-grid-image_hY6eEt > a.content-over-media > picture > img.content-over-media__media
/cdn/shop/files/AB_Teaser_Breezer_62b6d828-6a31-4c3d-a729...127.6 KiB43.1 KiB
div#block-image_anFW6Q > div#slide-template--19445889171702__slideshow_CLzrkk-image_anFW6Q > picture > img div#block-image_anFW6Q > div#slide-template--19445889171702__slideshow_CLzrkk-image_anFW6Q > picture > img
/cdn/shop/files/24Q3_September_Core_Segmentation_Testing_...51.2 KiB37.9 KiB

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

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.

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

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Estimated savings: 871 ms
URLTime Spent
www.allbirds.eu/871 ms
allbirds.de/0.0 ms

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

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.

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.

Estimated savings: 4.3 s 986.5 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.

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

CategoryTime Spent
Script Evaluation3.4 s
Style & Layout1.5 s
Other1.3 s
Script Parsing & Compilation258 ms
Parse HTML & CSS164 ms
Rendering53 ms
Garbage Collection17 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
LCP breakdown
LCP request discovery
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 6 user timings
Avoid long main-thread tasks 18 long tasks found
Image elements have explicit `width` and `height`
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 100 ms
Server Backend Latencies 850 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 30 ms
INP breakdown
Avoid non-composited animations
Avoid large layout shifts
87

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.

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.

Failing Elements
Der beste Erfinder der Welt ist die Natur. Daher holen wir uns hier Inspiration… div#slide-template--19445889171702__slideshow_CLzrkk-image_anFW6Q > div.content-over-media_content > div.prose > h6

These are opportunities to improve keyboard navigation in your application.

Names and labels

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

Failing Elements
div.content-over-media > video-media.sm:hidden > video.object-cover > img div.content-over-media > video-media.sm:hidden > video.object-cover > img
div.footer__block-content > div.footer__country-icons > a > img.image div.footer__block-content > div.footer__country-icons > a > img.image
div.footer__block-content > div.footer__country-icons > a > img.image div.footer__block-content > div.footer__country-icons > a > img.image
div.footer__block-content > div.footer__country-icons > a > img.image div.footer__block-content > div.footer__country-icons > a > img.image
div.footer__block-content > div.footer__country-icons > a > img.image div.footer__block-content > div.footer__country-icons > a > img.image
div.footer__block-content > div.footer__country-icons > a > img.image div.footer__block-content > div.footer__country-icons > a > img.image
div.footer__block-content > div.footer__country-icons > a > img.image div.footer__block-content > div.footer__country-icons > a > img.image
div.footer__block-content > div.footer__country-icons > a > img.image div.footer__block-content > div.footer__country-icons > a > img.image
div.footer__block-content > div.footer__country-icons > a > img.image div.footer__block-content > div.footer__country-icons > a > img.image
div.footer__block-content > div.footer__country-icons > a > img.image div.footer__block-content > div.footer__country-icons > a > img.image
div.footer__block-content > div.footer__country-icons > a > img.image div.footer__block-content > div.footer__country-icons > a > img.image

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.

Failing Elements
div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a
div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a
div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a
div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a
div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a
div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a
div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a
div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a
div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a
div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a

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

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Failing Elements
4.41 / 5 div#block-socials_dhcdGf > div.footer__block-content > div.jdgm-widget > button.jdgm-footer-stars-link
(864 Bewertungen) div#block-socials_dhcdGf > div.footer__block-content > div.jdgm-widget > button.jdgm-footer-count-link

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.

Failing Elements
4.41 / 5 div#block-socials_dhcdGf > div.footer__block-content > div.jdgm-widget > button.jdgm-footer-stars-link
(864 Bewertungen) div#block-socials_dhcdGf > div.footer__block-content > div.jdgm-widget > button.jdgm-footer-count-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
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
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
`[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
Background and foreground colors have a sufficient contrast ratio
Document has a `<title>` element
`<frame>` or `<iframe>` elements have a title
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links are distinguishable without relying on color.
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
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 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
`<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
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
No element has a `[tabindex]` value greater than 0
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.
96

Best Practices

General

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

SourceDescription
Failed to load resource: the server responded with a status of 404 ()
Failed to load resource: the server responded with a status of 404 ()
Failed to load resource: the server responded with a status of 404 ()
Failed to load resource: the server responded with a status of 404 ()
Refused to execute script from 'https://allbirds.de/cdn/shop/t/5/assets/swatch-image-switch.js?v=2965' because its MIME type ('text/html') is not executable, and strict MIME type checking is enabled.
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 issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
Mitigate clickjacking with XFO or CSP
92

SEO

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

Content Best Practices

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

Failing Elements
div.content-over-media > video-media.sm:hidden > video.object-cover > img div.content-over-media > video-media.sm:hidden > video.object-cover > img
div.footer__block-content > div.footer__country-icons > a > img.image div.footer__block-content > div.footer__country-icons > a > img.image
div.footer__block-content > div.footer__country-icons > a > img.image div.footer__block-content > div.footer__country-icons > a > img.image
div.footer__block-content > div.footer__country-icons > a > img.image div.footer__block-content > div.footer__country-icons > a > img.image
div.footer__block-content > div.footer__country-icons > a > img.image div.footer__block-content > div.footer__country-icons > a > img.image
div.footer__block-content > div.footer__country-icons > a > img.image div.footer__block-content > div.footer__country-icons > a > img.image
div.footer__block-content > div.footer__country-icons > a > img.image div.footer__block-content > div.footer__country-icons > a > img.image
div.footer__block-content > div.footer__country-icons > a > img.image div.footer__block-content > div.footer__country-icons > a > img.image
div.footer__block-content > div.footer__country-icons > a > img.image div.footer__block-content > div.footer__country-icons > a > img.image
div.footer__block-content > div.footer__country-icons > a > img.image div.footer__block-content > div.footer__country-icons > a > img.image
div.footer__block-content > div.footer__country-icons > a > img.image div.footer__block-content > div.footer__country-icons > a > img.image

Format your HTML in a way that enables crawlers to better understand your app’s content.

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

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

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

Core Web Vitals

Key metrics that affect user experience. — Desktop

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

935 ms

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

2.37 s

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

34 ms

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

0.000

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

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

3.15 s

Detailed Report

Audit breakdown by category with detailed findings.

84

Performance

Insights

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

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

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

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

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.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:26.666 source:map[column:9114 line:4 type:source-location url: urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:54.474 source:map[type:text value:[unattributed]]] map[reflowTime:13.585 source:map[column:172 line:1401 type:source-location url:https://allbirds.de/ urlProvider:network]] map[reflowTime:21.285 source:map[column:150 line:2591 type:source-location url:https://allbirds.de/ urlProvider:network]] map[reflowTime:15.16 source:map[column:2657 line:164 type:source-location url:https://allbirds.de/cdn/shop/t/5/assets/theme.js?v=86044763260100624921774876360 urlProvider:network]] map[reflowTime:14.821 source:map[column:26698 line:5 type:source-location url: urlProvider:network]] map[reflowTime:5.798 source:map[column:25754 line:3 type:source-location url: urlProvider:network]] map[reflowTime:0.161 source:map[column:25812 line:3 type:source-location url: urlProvider:network]] map[reflowTime:0.133 source:map[column:25876 line:3 type:source-location url: urlProvider:network]] map[reflowTime:5.753 source:map[column:6535 line:2 type:source-location url: urlProvider:network]] map[reflowTime:1.406 source:map[column:174716 line:1 type:source-location url:https://static.zdassets.com/web_widget/messenger/latest/web-widget-main-cf0e543.js urlProvider:network]]]

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

URLResource SizeEst Savings
div#block-image_rCP7ha > div#slide-template--19445889171702__slideshow_zep4yQ-image_rCP7ha > picture > img div#block-image_rCP7ha > div#slide-template--19445889171702__slideshow_zep4yQ-image_rCP7ha > picture > img
/cdn/shop/files/AB_Hero_Varsity_Desktop_a4e8c71e-709a-487...204.9 KiB93.6 KiB
div#media-grid-image_VCLLwh > a.content-over-media > picture > img.content-over-media__media div#media-grid-image_VCLLwh > a.content-over-media > picture > img.content-over-media__media
allbirds.de/cdn/shop/files/AB_Waterproof_Teaser.png?v=1774436644&width=400107.9 KiB86.5 KiB
div#block-image_anFW6Q > div#slide-template--19445889171702__slideshow_CLzrkk-image_anFW6Q > picture > img div#block-image_anFW6Q > div#slide-template--19445889171702__slideshow_CLzrkk-image_anFW6Q > picture > img
/cdn/shop/files/24Q3_September_Core_Segmentation_Testing_...133.6 KiB53.8 KiB
div.relative > button.text-with-icon > div.h-stack > span.country-flags div.relative > button.text-with-icon > div.h-stack > span.country-flags
/cdn/shop/t/5/assets/country-flags.png?v=3723003682655626...72.0 KiB52.4 KiB
div#media-grid-image_TK6AYM > a.content-over-media > picture > img.content-over-media__media div#media-grid-image_TK6AYM > a.content-over-media > picture > img.content-over-media__media
/cdn/shop/files/AB_Dasher_NZ_43fdeafd-5987-4510-a5a1-de16...72.2 KiB50.9 KiB
div#media-grid-image_mPMcbf > a.content-over-media > picture > img.content-over-media__media div#media-grid-image_mPMcbf > a.content-over-media > picture > img.content-over-media__media
allbirds.de/cdn/shop/files/AB_Terralux.png?v=1772545691&width=40068.4 KiB47.1 KiB
div#media-grid-image_hY6eEt > a.content-over-media > picture > img.content-over-media__media div#media-grid-image_hY6eEt > a.content-over-media > picture > img.content-over-media__media
/cdn/shop/files/AB_Teaser_Breezer_62b6d828-6a31-4c3d-a729...43.8 KiB22.5 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.

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.

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

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Estimated savings: 352 ms
URLTime Spent
www.allbirds.eu/352 ms
allbirds.de/0.0 ms

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

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.

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

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

Max Potential First Input Delay 90 ms
Layout shift culprits
Optimize DOM size
Font display
LCP breakdown
LCP request discovery
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 6 user timings
JavaScript execution time 0.7 s
Minimizes main-thread work 1.9 s
Avoid long main-thread tasks 3 long tasks found
Avoid non-composited animations 1 animated element found
Image elements have explicit `width` and `height`
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 30 ms
Server Backend Latencies 270 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 40 ms
INP breakdown
Avoid large layout shifts
87

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.

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.

Failing Elements
Der beste Erfinder der Welt ist die Natur. Daher holen wir uns hier Inspiration… div#slide-template--19445889171702__slideshow_CLzrkk-image_anFW6Q > div.content-over-media_content > div.prose > h6

These are opportunities to improve keyboard navigation in your application.

Names and labels

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

Failing Elements
div.content-over-media > video-media.hidden > video > img div.content-over-media > video-media.hidden > video > img
div.accordion__content > div.footer__block-content > div.footer__payment-icons > img.image div.accordion__content > div.footer__block-content > div.footer__payment-icons > img.image
div.accordion__content > div.footer__block-content > div.footer__payment-icons > img.image div.accordion__content > div.footer__block-content > div.footer__payment-icons > img.image
div.accordion__content > div.footer__block-content > div.footer__payment-icons > img.image div.accordion__content > div.footer__block-content > div.footer__payment-icons > img.image
div.accordion__content > div.footer__block-content > div.footer__payment-icons > img.image div.accordion__content > div.footer__block-content > div.footer__payment-icons > img.image
div.footer__block-content > div.footer__country-icons > a > img.image div.footer__block-content > div.footer__country-icons > a > img.image
div.footer__block-content > div.footer__country-icons > a > img.image div.footer__block-content > div.footer__country-icons > a > img.image
div.footer__block-content > div.footer__country-icons > a > img.image div.footer__block-content > div.footer__country-icons > a > img.image
div.footer__block-content > div.footer__country-icons > a > img.image div.footer__block-content > div.footer__country-icons > a > img.image
div.footer__block-content > div.footer__country-icons > a > img.image div.footer__block-content > div.footer__country-icons > a > img.image
div.footer__block-content > div.footer__country-icons > a > img.image div.footer__block-content > div.footer__country-icons > a > img.image
div.footer__block-content > div.footer__country-icons > a > img.image div.footer__block-content > div.footer__country-icons > a > img.image
div.footer__block-content > div.footer__country-icons > a > img.image div.footer__block-content > div.footer__country-icons > a > img.image
div.footer__block-content > div.footer__country-icons > a > img.image div.footer__block-content > div.footer__country-icons > a > img.image
div.footer__block-content > div.footer__country-icons > a > img.image div.footer__block-content > div.footer__country-icons > a > img.image

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.

Failing Elements
div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a
div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a
div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a
div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a
div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a
div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a
div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a
div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a
div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a
div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a

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

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Failing Elements
4.41 / 5 div#block-socials_dhcdGf > div.footer__block-content > div.jdgm-widget > button.jdgm-footer-stars-link
(864 Bewertungen) div#block-socials_dhcdGf > div.footer__block-content > div.jdgm-widget > button.jdgm-footer-count-link

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.

Failing Elements
4.41 / 5 div#block-socials_dhcdGf > div.footer__block-content > div.jdgm-widget > button.jdgm-footer-stars-link
(864 Bewertungen) div#block-socials_dhcdGf > div.footer__block-content > div.jdgm-widget > button.jdgm-footer-count-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
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
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
`[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
Background and foreground colors have a sufficient contrast ratio
Document has a `<title>` element
`<frame>` or `<iframe>` elements have a title
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links are distinguishable without relying on color.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
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 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
`<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.
No element has a `[tabindex]` value greater than 0
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.
96

Best Practices

General

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

SourceDescription
Failed to load resource: the server responded with a status of 404 ()
Failed to load resource: the server responded with a status of 404 ()
Failed to load resource: the server responded with a status of 404 ()
Failed to load resource: the server responded with a status of 404 ()
allbirds.de/ line 3934, col 0
Refused to execute script from 'https://allbirds.de/cdn/shop/t/5/assets/swatch-image-switch.js?v=2965' because its MIME type ('text/html') is not executable, and strict MIME type checking is enabled.
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 issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
Mitigate clickjacking with XFO or CSP
92

SEO

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

Content Best Practices

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

Failing Elements
div.content-over-media > video-media.hidden > video > img div.content-over-media > video-media.hidden > video > img
div.accordion__content > div.footer__block-content > div.footer__payment-icons > img.image div.accordion__content > div.footer__block-content > div.footer__payment-icons > img.image
div.accordion__content > div.footer__block-content > div.footer__payment-icons > img.image div.accordion__content > div.footer__block-content > div.footer__payment-icons > img.image
div.accordion__content > div.footer__block-content > div.footer__payment-icons > img.image div.accordion__content > div.footer__block-content > div.footer__payment-icons > img.image
div.accordion__content > div.footer__block-content > div.footer__payment-icons > img.image div.accordion__content > div.footer__block-content > div.footer__payment-icons > img.image
div.footer__block-content > div.footer__country-icons > a > img.image div.footer__block-content > div.footer__country-icons > a > img.image
div.footer__block-content > div.footer__country-icons > a > img.image div.footer__block-content > div.footer__country-icons > a > img.image
div.footer__block-content > div.footer__country-icons > a > img.image div.footer__block-content > div.footer__country-icons > a > img.image
div.footer__block-content > div.footer__country-icons > a > img.image div.footer__block-content > div.footer__country-icons > a > img.image
div.footer__block-content > div.footer__country-icons > a > img.image div.footer__block-content > div.footer__country-icons > a > img.image
div.footer__block-content > div.footer__country-icons > a > img.image div.footer__block-content > div.footer__country-icons > a > img.image
div.footer__block-content > div.footer__country-icons > a > img.image div.footer__block-content > div.footer__country-icons > a > img.image
div.footer__block-content > div.footer__country-icons > a > img.image div.footer__block-content > div.footer__country-icons > a > img.image
div.footer__block-content > div.footer__country-icons > a > img.image div.footer__block-content > div.footer__country-icons > a > img.image
div.footer__block-content > div.footer__country-icons > a > img.image div.footer__block-content > div.footer__country-icons > a > img.image

Format your HTML in a way that enables crawlers to better understand your app’s content.

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

Send Feedback