C — https://www.flixbus.com | BeaverCheck Audit

Site Health

Score: 73 / 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)

Content-Security-Policy header is missing

Security › Security Headers

Cookie 'redirectInfoMessage' is missing the Secure flag

Security › Cookie Security

HSTS header is missing

Security › Security Headers

No Content-Security-Policy header found

Security › Content Security Policy

1 button(s) with no accessible text

Accessibility › Link & Button Quality

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.flixbus.com)](https://beavercheck.com/results/830f3ea5-d8f5-f67b-f929-2b15938bb441)

HTML

<a href="https://beavercheck.com/results/830f3ea5-d8f5-f67b-f929-2b15938bb441"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.flixbus.com" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fwww.flixbus.com

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

Best Practices

SEO

Core Web Vitals

Key metrics that affect user experience.

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

3.41 s

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

12.29 s

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

1.54 s

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

0.291

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

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

15.52 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

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

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.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Request	Cache TTL	Transfer Size
www.datadoghq-browser-agent.com/eu1/v5/datadog-rum.js	14400.0 s	51.9 KiB
honeycomb.flixbus.com/dist/15.3.3/font/roboto-latin-700-normal.woff2	0.0 ms	21.0 KiB
honeycomb.flixbus.com/dist/15.3.3/font/roboto-latin-500-normal.woff2	0.0 ms	21.0 KiB
honeycomb.flixbus.com/dist/15.3.3/font/roboto-latin-400-normal.woff2	0.0 ms	20.7 KiB
pulse.cro.flixbus.com/static/hybridge.js	600.0 s	12.9 KiB
app.usercentrics.eu/browser-ui/latest/loader.js	3600.0 s	10.8 KiB
pulse.cro.flixbus.com/static/fxp.js	120.0 s	5.1 KiB
honeycomb-icons.hive.flixbus.com/9.0.0/flix-icons/p-d146a345.js	0.0 ms	4.8 KiB
pulse.cro.flixbus.com/static/pulse.js	600.0 s	2.5 KiB
cdn.adtriba.com/v2/adtriba.js	7200.0 s	3.0 KiB
honeycomb-icons.hive.flixbus.com/9.0.0/flix-icons/p-d3d1f320.entry.js	0.0 ms	1.9 KiB
honeycomb.flixbus.com/dist/15.3.3/js/popup.js	0.0 ms	1.8 KiB
honeycomb.flixbus.com/dist/15.3.3/js/dropdown.js	0.0 ms	1.7 KiB
honeycomb.flixbus.com/dist/15.3.3/js/tabs.js	0.0 ms	1.4 KiB
account-widget.booking.flixbus.com/current/assets/entry.js	0.0 ms	1.1 KiB
honeycomb.flixbus.com/dist/15.3.3/js/classToggler.js	0.0 ms	1.1 KiB
honeycomb.flixbus.com/dist/15.3.3/css/honeycomb-fonts.css	0.0 ms	906 B
honeycomb-icons.hive.flixbus.com/9.0.0/flix-icons/flix-icons.esm.js	0.0 ms	834 B
app.usercentrics.eu/session/1px.png?settingsId=Cw0rbv9tt	1800.0 s	822 B
o.adtriba.com/px.gif	86400.0 s	227 B

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]

items: [map[node:map[type:text value:Total] score:0.29108399999999995] map[node:map[boundingRect:map[bottom:3290 height:3110 left:0 right:412 top:180 width:412] lhId:page-3-MAIN nodeLabel:Bus Travel in the US One Way Round Trip From To Today, Apr 7 Departure 1 Adul… path:1,HTML,1,BODY,6,MAIN selector:body.flix-main-wrapper > main#main-content snippet:<main id="main-content"> type:node] score:0.257594] map[node:map[boundingRect:map[bottom:733 height:308 left:12 right:400 top:425 width:388] lhId:page-6-DIV nodeLabel:div.hero-content > div.hero-search-mask-wrapper > div#search-mask-placeholder > div.flix-col-12 path:1,HTML,1,BODY,6,MAIN,0,DIV,1,DIV,1,DIV,0,DIV,1,DIV selector:div.hero-content > div.hero-search-mask-wrapper > div#search-mask-placeholder > div.flix-col-12 snippet:<div class="flix-col-12 flix-grid sm-placeholder-padding-0"> type:node] score:0.032589 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:1521 height:16 left:92 right:182 top:1505 width:90] lhId:page-13-IMG nodeLabel:div.social-proof > div.social-proof__container > div.social-proof__logos > img.social-proof__logo path:1,HTML,1,BODY,6,MAIN,6,DIV,1,DIV,1,DIV,0,IMG selector:div.social-proof > div.social-proof__container > div.social-proof__logos > img.social-proof__logo snippet:<img src="https://cdn-cf.cms.flixbus.com/drupal-assets/social-proof-logos/flixbus-gr…" alt="" class="social-proof__logo" data-id="flixbus"> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:980 height:211 left:0 right:412 top:769 width:412] lhId:page-7-DIV nodeLabel:Get the app and travel with ease of mind Digital ticket & Live tracking Trust… path:1,HTML,1,BODY,6,MAIN,3,DIV selector:body.flix-main-wrapper > main#main-content > div.card-banner-mobile snippet:<div class="card-banner-mobile"> type:node] score:0.000901]]

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

	URL	Resource Size	Est Savings
div.hero-container > div#default-hero-image-container > picture > img.hero-image `div.hero-container > div#default-hero-image-container > picture > img.hero-image`	/drupal-assets/2021-08/US_Cali_FlixBus_New-Design_mobile.jpg	98.1 KiB	84.3 KiB
Vehicle passing through a city `div.page-content-wrapper > div.exploration-map-banner-image > picture > img`	/drupal-assets/exploration-map-banner/flixbus-mobile-larg...	106.9 KiB	77.2 KiB
FlixBus app on phone `div.card-banner__right-content > div.card-banner__phone > picture > img.card-banner__phone-img`	cdn-cf.cms.flixbus.com/drupal-assets/card-banner/card-banner-phone-mobile.avif	56.2 KiB	46.7 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.

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.

URL	Transfer Size	Duration
cdn-cf.cms.flixbus.com/drupal-assets/flix-home-assets/cms_honeycomb.f4a64e.css	13.0 KiB	971 ms
cdn-cf.cms.flixbus.com/drupal-assets/flix-home-assets/styles.ca8b6e.css	8.0 KiB	154 ms
www.flixbus.com/assets/uc/cc.js	1.1 KiB

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

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Element	Layout shift score
Bus Travel in the US One Way Round Trip From To Today, Apr 7 Departure 1 Adul… `body.flix-main-wrapper > main#main-content`	0.258
div.hero-content > div.hero-search-mask-wrapper > div#search-mask-placeholder > div.flix-col-12 `div.hero-content > div.hero-search-mask-wrapper > div#search-mask-placeholder > div.flix-col-12`	0.033
Get the app and travel with ease of mind Digital ticket & Live tracking Trust… `body.flix-main-wrapper > main#main-content > div.card-banner-mobile`	0.001

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 JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Estimated savings: 2.9 s 735.4 KiB

URL	Transfer Size	Est Savings
d3k6pebee3cv6.cloudfront.net/search-mask/current/main.920e98fd.js	219.5 KiB	78.2 KiB
www.googletagmanager.com/gtm.js?id=GTM-QFH9M	183.5 KiB	72.7 KiB
www.googletagmanager.com/gtag/js?id=AW-993552604&cx=c&gtm=4e6460	145.9 KiB	65.9 KiB
www.googletagmanager.com/gtag/js?id=DC-13389221&cx=c&gtm=4e6460	129.7 KiB	63.3 KiB
www.googletagmanager.com/gtag/js?id=DC-13397442&cx=c&gtm=4e6460	129.7 KiB	63.3 KiB
www.googletagmanager.com/gtag/js?id=DC-13513570&cx=c&gtm=4e6460	129.7 KiB	63.3 KiB
www.googletagmanager.com/gtag/js?id=DC-13118234&cx=c&gtm=4e6460	129.7 KiB	63.2 KiB
www.googletagmanager.com/gtag/js?id=DC-14468760&cx=c&gtm=4e6460	129.7 KiB	63.0 KiB
www.googletagmanager.com/gtag/js?id=DC-13147834&cx=c&gtm=4e6460	130.2 KiB	62.7 KiB
app.usercentrics.eu/browser-ui/3.96.0/index.module.js	119.8 KiB	53.3 KiB
account-widget.booking.flixbus.com/current/assets/main.CgKgh9lJ.js	54.5 KiB	31.4 KiB
www.datadoghq-browser-agent.com/eu1/v5/datadog-rum.js	51.5 KiB	29.0 KiB
app.usercentrics.eu/browser-ui/3.96.0/VirtualServiceItem-c9f2ea00.js	48.7 KiB	26.3 KiB

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

URL	Total CPU Time	Script Evaluation	Script Parse
Unattributable	1.8 s	257 ms	0.0 ms
www.googletagmanager.com/gtm.js?id=GTM-QFH9M	951 ms	819 ms	70 ms
d3k6pebee3cv6.cloudfront.net/search-mask/current/main.920e98fd.js	913 ms	619 ms	171 ms
app.usercentrics.eu/browser-ui/3.96.0/index.module.js	615 ms	410 ms	3.0 ms
www.flixbus.com/	597 ms	67 ms	9.4 ms
www.googletagmanager.com/gtag/js?id=DC-13118234&cx=c&gtm=4e6460	380 ms	343 ms	34 ms
www.datadoghq-browser-agent.com/eu1/v5/datadog-rum.js	307 ms	250 ms	17 ms
www.googletagmanager.com/gtag/js?id=DC-13147834&cx=c&gtm=4e6460	216 ms	169 ms	45 ms
www.googletagmanager.com/gtag/js?id=AW-993552604&cx=c&gtm=4e6460	191 ms	151 ms	36 ms
cdn-cf.cms.flixbus.com/drupal-assets/flix-home-assets/main.52f17b.js	177 ms	88 ms	7.4 ms
www.googletagmanager.com/gtag/js?id=DC-13389221&cx=c&gtm=4e6460	150 ms	109 ms	38 ms
www.googletagmanager.com/gtag/js?id=DC-14468760&cx=c&gtm=4e6460	138 ms	100 ms	36 ms
www.googletagmanager.com/gtag/js?id=DC-13397442&cx=c&gtm=4e6460	131 ms	100 ms	29 ms
www.googletagmanager.com/gtag/js?id=DC-13513570&cx=c&gtm=4e6460	131 ms	103 ms	27 ms
account-widget.booking.flixbus.com/current/assets/main.CgKgh9lJ.js	130 ms	104 ms	1.0 ms
honeycomb-icons.hive.flixbus.com/9.0.0/flix-icons/p-d146a345.js	120 ms	71 ms	0.1 ms
d2kfg2dwwf7b20.cloudfront.net/broccoli.js	113 ms	99 ms	7.9 ms
app.usercentrics.eu/browser-ui/latest/loader.js	50 ms	44 ms	4.1 ms

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

Category	Time Spent
Script Evaluation	4.1 s
Other	1.9 s
Style & Layout	613 ms
Script Parsing & Compilation	561 ms
Parse HTML & CSS	153 ms
Rendering	94 ms
Garbage Collection	24 ms

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: 0.0 ms 10.9 KiB

URL	Transfer Size	Est Savings
cdn-cf.cms.flixbus.com/drupal-assets/flix-home-assets/cms_honeycomb.f4a64e.css	12.6 KiB	10.9 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

	URL
FlixBus app on phone `div.card-banner__right-content > div.card-banner__phone > picture > img.card-banner__phone-img`	cdn-cf.cms.flixbus.com/drupal-assets/card-banner/card-banner-phone-mobile.avif
flixbus logo `div.flix-header__inner > div.flix-header-brand > a.flix-header-brand__link > img.flix-header-brand__img`	cdn-cf.cms.flixbus.com/drupal-assets/logos/flixbus.png
div.social-proof > div.social-proof__container > div.social-proof__logos > img.social-proof__logo `div.social-proof > div.social-proof__container > div.social-proof__logos > img.social-proof__logo`	/drupal-assets/social-proof-logos/greyhound-greyscale-70.svg
div.social-proof > div.social-proof__container > div.social-proof__logos > img.social-proof__logo `div.social-proof > div.social-proof__container > div.social-proof__logos > img.social-proof__logo`	/drupal-assets/social-proof-logos/flixtrain-greyscale-70.svg
div.social-proof > div.social-proof__container > div.social-proof__logos > img.social-proof__logo `div.social-proof > div.social-proof__container > div.social-proof__logos > img.social-proof__logo`	cdn-cf.cms.flixbus.com/drupal-assets/social-proof-logos/flixbus-greyscale-70.svg
div.social-proof > div.social-proof__container > div.social-proof__logos > img.social-proof__logo `div.social-proof > div.social-proof__container > div.social-proof__logos > img.social-proof__logo`	cdn-cf.cms.flixbus.com/drupal-assets/social-proof-logos/kamil-greyscale-70.svg

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

●Document request latency

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●LCP request discovery

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

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

●Avoid long main-thread tasks 20 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 30 ms

●Server Backend Latencies 80 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 30 ms

○INP breakdown

○User Timing marks and measures

○Avoid non-composited animations

Accessibility

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

Names and labels

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

Failing Elements
div.iBR9R > div.wFRu3 > span.hcr-tooltip-target-13-6-1 > button.hcr-btn-13-6-1 `div.iBR9R > div.wFRu3 > span.hcr-tooltip-target-13-6-1 > button.hcr-btn-13-6-1`

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.footer-social-right-container > ul.footer-social-icons > li > a `div.footer-social-right-container > ul.footer-social-icons > li > a`
div.footer-social-right-container > ul.footer-social-icons > li > a `div.footer-social-right-container > ul.footer-social-icons > li > a`
div.footer-social-right-container > ul.footer-social-icons > li > a `div.footer-social-right-container > ul.footer-social-icons > li > a`
div.footer-social-right-container > ul.footer-social-icons > li > a `div.footer-social-right-container > ul.footer-social-icons > li > a`
div.footer-social-right-container > ul.footer-social-icons > li > a `div.footer-social-right-container > ul.footer-social-icons > li > a`
div.footer-social-right-container > ul.footer-social-icons > li > a `div.footer-social-right-container > ul.footer-social-icons > li > 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.

○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

●Image elements have `[alt]` attributes

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●`button`, `link`, and `menuitem` elements have accessible names

●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

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○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

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

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

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

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

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

Best Practices

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

	URL	Aspect Ratio (Displayed)	Aspect Ratio (Actual)
Vehicle passing through a city `div.page-content-wrapper > div.exploration-map-banner-image > picture > img`	/drupal-assets/exploration-map-banner/flixbus-mobile-larg...	412 x 443 (0.93)	767 x 798 (0.96)

●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

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

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

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

SEO

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

Content Best Practices

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

Link destination	Link Text
corporate.flix.com/flix-sustainable-travel/flix-innovation-catalyst-pioneer/	here

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

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

Accessibility

Best Practices

SEO

Core Web Vitals

Key metrics that affect user experience. — Desktop

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

792 ms

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

1.14 s

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

209 ms

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

0.165

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

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

3.62 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

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

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

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

items: [map[node:map[type:text value:Total] score:0.16459300000000002] map[node:map[boundingRect:map[bottom:2546 height:2402 left:0 right:1350 top:144 width:1350] lhId:page-8-MAIN nodeLabel:Bus Travel in the US One Way Round Trip From To Today, Apr 7 Departure 1 Adul… path:1,HTML,1,BODY,6,MAIN selector:body.flix-main-wrapper > main#main-content snippet:<main id="main-content"> type:node] score:0.077361] map[node:map[boundingRect:map[bottom:632 height:263 left:90 right:1260 top:369 width:1170] lhId:page-11-DIV nodeLabel:Bus Travel in the US One Way Round Trip From To Today, Apr 7 Departure 1 Adul… path:1,HTML,1,BODY,6,MAIN,0,DIV,1,DIV selector:body.flix-main-wrapper > main#main-content > div.hero-container > div.hero-content snippet:<div class="hero-content"> type:node] score:0.034563] map[node:map[boundingRect:map[bottom:632 height:263 left:90 right:1260 top:369 width:1170] lhId:page-11-DIV nodeLabel:Bus Travel in the US One Way Round Trip From To Today, Apr 7 Departure 1 Adul… path:1,HTML,1,BODY,6,MAIN,0,DIV,1,DIV selector:body.flix-main-wrapper > main#main-content > div.hero-container > div.hero-content snippet:<div class="hero-content"> type:node] score:0.033529] map[node:map[boundingRect:map[bottom:632 height:263 left:90 right:1260 top:369 width:1170] lhId:page-11-DIV nodeLabel:Bus Travel in the US One Way Round Trip From To Today, Apr 7 Departure 1 Adul… path:1,HTML,1,BODY,6,MAIN,0,DIV,1,DIV selector:body.flix-main-wrapper > main#main-content > div.hero-container > div.hero-content snippet:<div class="hero-content"> type:node] score:0.010457] map[node:map[boundingRect:map[bottom:1023 height:30 left:364 right:986 top:993 width:622] lhId:page-3-DIV nodeLabel:main#main-content > div.social-proof > div.social-proof__container > div.social-proof__logos path:1,HTML,1,BODY,6,MAIN,6,DIV,1,DIV,1,DIV selector:main#main-content > div.social-proof > div.social-proof__container > div.social-proof__logos snippet:<div class="social-proof__logos"> type:node] score:0.008136]]

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

	URL	Resource Size	Est Savings
div.hero-container > div#default-hero-image-container > picture > img.hero-image `div.hero-container > div#default-hero-image-container > picture > img.hero-image`	/drupal-assets/2021-08/US_Cali_FlixBus_New-Design_desktop...	342.2 KiB	249.7 KiB
FlixBus app on phone `div.card-banner__right-content > div.card-banner__phone > picture > img.card-banner__phone-img`	cdn-cf.cms.flixbus.com/drupal-assets/card-banner/card-banner-phone-desktop.avif	139.8 KiB	125.3 KiB
Vehicle passing through a city `div.page-content-wrapper > div.exploration-map-banner-image > picture > img`	/drupal-assets/exploration-map-banner/flixbus-desktop-lar...	140.8 KiB	109.2 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.

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

value: No additional origins are good candidates for preconnecting

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.

URL	Transfer Size	Duration
cdn-cf.cms.flixbus.com/drupal-assets/flix-home-assets/cms_honeycomb.f4a64e.css	13.0 KiB	330 ms
cdn-cf.cms.flixbus.com/drupal-assets/flix-home-assets/styles.ca8b6e.css	8.0 KiB
www.flixbus.com/assets/uc/cc.js	1.1 KiB

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Request	Cache TTL	Transfer Size
www.datadoghq-browser-agent.com/eu1/v5/datadog-rum.js	14400.0 s	51.9 KiB
honeycomb.flixbus.com/dist/15.3.3/font/roboto-latin-700-normal.woff2	0.0 ms	21.0 KiB
honeycomb.flixbus.com/dist/15.3.3/font/roboto-latin-500-normal.woff2	0.0 ms	21.0 KiB
honeycomb.flixbus.com/dist/15.3.3/font/roboto-latin-400-normal.woff2	0.0 ms	20.7 KiB
pulse.cro.flixbus.com/static/hybridge.js	600.0 s	12.9 KiB
app.usercentrics.eu/browser-ui/latest/loader.js	3600.0 s	10.8 KiB
pulse.cro.flixbus.com/static/fxp.js	120.0 s	5.1 KiB
honeycomb-icons.hive.flixbus.com/9.0.0/flix-icons/p-d146a345.js	0.0 ms	4.8 KiB
pulse.cro.flixbus.com/static/pulse.js	600.0 s	2.5 KiB
cdn.adtriba.com/v2/adtriba.js	7200.0 s	3.0 KiB
honeycomb-icons.hive.flixbus.com/9.0.0/flix-icons/p-d3d1f320.entry.js	0.0 ms	1.9 KiB
honeycomb.flixbus.com/dist/15.3.3/js/popup.js	0.0 ms	1.8 KiB
honeycomb.flixbus.com/dist/15.3.3/js/dropdown.js	0.0 ms	1.7 KiB
honeycomb.flixbus.com/dist/15.3.3/js/tabs.js	0.0 ms	1.4 KiB
account-widget.booking.flixbus.com/current/assets/entry.js	0.0 ms	1.1 KiB
honeycomb.flixbus.com/dist/15.3.3/js/classToggler.js	0.0 ms	1.1 KiB
honeycomb.flixbus.com/dist/15.3.3/css/honeycomb-fonts.css	0.0 ms	907 B
honeycomb-icons.hive.flixbus.com/9.0.0/flix-icons/flix-icons.esm.js	0.0 ms	833 B
app.usercentrics.eu/session/1px.png?settingsId=Cw0rbv9tt	1800.0 s	822 B
o.adtriba.com/px.gif	86400.0 s	227 B

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

Element	Layout shift score
Bus Travel in the US One Way Round Trip From To Today, Apr 7 Departure 1 Adul… `body.flix-main-wrapper > main#main-content`	0.077
Bus Travel in the US One Way Round Trip From To Today, Apr 7 Departure 1 Adul… `body.flix-main-wrapper > main#main-content > div.hero-container > div.hero-content`	0.035
Bus Travel in the US One Way Round Trip From To Today, Apr 7 Departure 1 Adul… `body.flix-main-wrapper > main#main-content > div.hero-container > div.hero-content`	0.034
Bus Travel in the US One Way Round Trip From To Today, Apr 7 Departure 1 Adul… `body.flix-main-wrapper > main#main-content > div.hero-container > div.hero-content`	0.010
main#main-content > div.social-proof > div.social-proof__container > div.social-proof__logos `main#main-content > div.social-proof > div.social-proof__container > div.social-proof__logos`	0.008
English Open language selection `body.flix-main-wrapper > header.flix-header > div.flix-header__inner > div#header-widgets-container`	0.001

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.

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

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

Category	Time Spent
Script Evaluation	1.3 s
Other	555 ms
Style & Layout	170 ms
Script Parsing & Compilation	148 ms
Rendering	43 ms
Parse HTML & CSS	36 ms
Garbage Collection	34 ms

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: 0.0 ms 10.2 KiB

URL	Transfer Size	Est Savings
cdn-cf.cms.flixbus.com/drupal-assets/flix-home-assets/cms_honeycomb.f4a64e.css	12.6 KiB	10.2 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.

Estimated savings: 0.0 ms 718.0 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtm.js?id=GTM-QFH9M	183.5 KiB	72.7 KiB
www.googletagmanager.com/gtag/js?id=AW-993552604&cx=c&gtm=4e6460	145.9 KiB	65.9 KiB
www.googletagmanager.com/gtag/js?id=DC-13389221&cx=c&gtm=4e6460	129.7 KiB	63.3 KiB
www.googletagmanager.com/gtag/js?id=DC-13397442&cx=c&gtm=4e6460	129.7 KiB	63.3 KiB
www.googletagmanager.com/gtag/js?id=DC-13118234&cx=c&gtm=4e6460	129.7 KiB	63.3 KiB
www.googletagmanager.com/gtag/js?id=DC-13513570&cx=c&gtm=4e6460	129.7 KiB	63.2 KiB
www.googletagmanager.com/gtag/js?id=DC-14468760&cx=c&gtm=4e6460	129.7 KiB	63.0 KiB
www.googletagmanager.com/gtag/js?id=DC-13147834&cx=c&gtm=4e6460	130.2 KiB	62.7 KiB
d3k6pebee3cv6.cloudfront.net/search-mask/current/main.920e98fd.js	219.5 KiB	60.8 KiB
app.usercentrics.eu/browser-ui/3.96.0/index.module.js	119.8 KiB	53.3 KiB
account-widget.booking.flixbus.com/current/assets/main.CgKgh9lJ.js	54.5 KiB	31.4 KiB
www.datadoghq-browser-agent.com/eu1/v5/datadog-rum.js	51.5 KiB	29.0 KiB
app.usercentrics.eu/browser-ui/3.96.0/VirtualServiceItem-c9f2ea00.js	48.7 KiB	26.3 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

	URL
FlixBus app on phone `div.card-banner__right-content > div.card-banner__phone > picture > img.card-banner__phone-img`	cdn-cf.cms.flixbus.com/drupal-assets/card-banner/card-banner-phone-desktop.avif
flixbus logo `div.flix-header__inner > div.flix-header-brand > a.flix-header-brand__link > img.flix-header-brand__img`	cdn-cf.cms.flixbus.com/drupal-assets/logos/flixbus.png
div.social-proof > div.social-proof__container > div.social-proof__logos > img.social-proof__logo `div.social-proof > div.social-proof__container > div.social-proof__logos > img.social-proof__logo`	/drupal-assets/social-proof-logos/greyhound-greyscale-70.svg
div.social-proof > div.social-proof__container > div.social-proof__logos > img.social-proof__logo `div.social-proof > div.social-proof__container > div.social-proof__logos > img.social-proof__logo`	/drupal-assets/social-proof-logos/flixtrain-greyscale-70.svg
div.social-proof > div.social-proof__container > div.social-proof__logos > img.social-proof__logo `div.social-proof > div.social-proof__container > div.social-proof__logos > img.social-proof__logo`	cdn-cf.cms.flixbus.com/drupal-assets/social-proof-logos/flixbus-greyscale-70.svg
div.social-proof > div.social-proof__container > div.social-proof__logos > img.social-proof__logo `div.social-proof > div.social-proof__container > div.social-proof__logos > img.social-proof__logo`	cdn-cf.cms.flixbus.com/drupal-assets/social-proof-logos/kamil-greyscale-70.svg
Get it on Google Play `div.card-banner__content > div.card-banner__buttons > a.card-banner__store-link > img`
Download on the App Store `div.card-banner__content > div.card-banner__buttons > a.card-banner__store-link > img`

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

●Document request latency

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●LCP request discovery

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

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

●JavaScript execution time 1.1 s

●Avoid long main-thread tasks 4 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 50 ms

●Server Backend Latencies 100 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 30 ms

○INP breakdown

○User Timing marks and measures

○Avoid non-composited animations

Accessibility

Names and labels

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

Failing Elements
div.iBR9R > div.wFRu3 > span.hcr-tooltip-target-13-6-1 > button.hcr-btn-13-6-1 `div.iBR9R > div.wFRu3 > span.hcr-tooltip-target-13-6-1 > button.hcr-btn-13-6-1`

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.card-banner__right-content > div.card-banner__phone > div.card-banner__qr-code > img `div.card-banner__right-content > div.card-banner__phone > div.card-banner__qr-code > img`

Failing Elements
div.footer-social-right-container > ul.footer-social-icons > li > a `div.footer-social-right-container > ul.footer-social-icons > li > a`
div.footer-social-right-container > ul.footer-social-icons > li > a `div.footer-social-right-container > ul.footer-social-icons > li > a`
div.footer-social-right-container > ul.footer-social-icons > li > a `div.footer-social-right-container > ul.footer-social-icons > li > a`
div.footer-social-right-container > ul.footer-social-icons > li > a `div.footer-social-right-container > ul.footer-social-icons > li > a`
div.footer-social-right-container > ul.footer-social-icons > li > a `div.footer-social-right-container > ul.footer-social-icons > li > a`
div.footer-social-right-container > ul.footer-social-icons > li > a `div.footer-social-right-container > ul.footer-social-icons > li > 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.

○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

●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

●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

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○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

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

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

○`<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.

Best Practices

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

	URL	Aspect Ratio (Displayed)	Aspect Ratio (Actual)
div.card-banner__right-content > div.card-banner__phone > div.card-banner__qr-code > img `div.card-banner__right-content > div.card-banner__phone > div.card-banner__qr-code > img`		150 x 145 (1.03)	154 x 154 (1.00)

●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

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

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

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

SEO

Content Best Practices

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

Link destination	Link Text
corporate.flix.com/flix-sustainable-travel/flix-innovation-catalyst-pioneer/	here

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.card-banner__right-content > div.card-banner__phone > div.card-banner__qr-code > img `div.card-banner__right-content > div.card-banner__phone > div.card-banner__qr-code > img`

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

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links are crawlable

●robots.txt is valid

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Browse & Analyze

Learn

Results for https://www.flixbus.com

Site Health

Top Priorities (5)

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Names and labels

Best Practices

User Experience

SEO

Content Best Practices

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Names and labels

Best Practices

User Experience

SEO

Content Best Practices

Keyboard Shortcuts