Skip to content
https://vueling.com

Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

25

Performance

Insights

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

RequestCache TTLTransfer Size
m.vueling.com/main.589b2ac66d647595.js224.0 s735.7 KiB
cdn.quantummetric.com/qscripts/quantum-vueling.js300.0 s154.8 KiB
m.vueling.com/scripts.5f11d3cd0711642e.js382.0 s154.7 KiB
m.vueling.com/VvV_CU/-cR/1WF/N2BGojSq/J1i3LDVuV9w9Xk/bBJnKQVZfQ/EHlz/bBFRMAUC21600.0 s182.6 KiB
m.vueling.com/assets/fonts/ds-vueling-icons.woff2?m8cpo5222.0 s109.2 KiB
/VvV_CU/-cR/1WF/N2BGojSq/SDi3LDVu/Uk9rKQVZfQ/JB4J/VWwANyU...21600.0 s153.4 KiB
m.vueling.com/assets/fonts/source-sans-pro/SourceSansPro-SemiBold.woff294.0 s75.0 KiB
m.vueling.com/assets/fonts/source-sans-pro/SourceSansPro-Regular.woff2399.0 s76.0 KiB
m.vueling.com/assets/img/home/complete-your-travel/parking.png484.0 s60.4 KiB
cdn.cookielaw.org/consent/eb440cb9-982b-4dfe-9764-a5f339ad9985/OtAutoBlock.js86400.0 s131.6 KiB
m.vueling.com/resources/5ca37ed9506e8073faf2465e595f1330830972a3a4ff7600.0 s56.6 KiB
se.monetate.net/js/2/a-02a953bb/p/m.vueling.com/custom.js3600.0 s63.8 KiB
m.vueling.com/styles.8e885a44ccb9c0d4.css357.0 s53.3 KiB
m.vueling.com/assets/img/home/complete-your-travel/hotels.webp83.0 s48.5 KiB
cdn.cookielaw.org/scripttemplates/6.38.0/otBannerSdk.js86400.0 s87.9 KiB
m.vueling.com/assets/img/home/complete-your-travel/cars.png11.0 s28.7 KiB
m.vueling.com/6258.afba6971f62b6f1d.js255.0 s23.4 KiB
m.vueling.com/231.353e5fa70266ac30.js335.0 s22.6 KiB
m.vueling.com/assets/fonts/pilcrow/vuelingpilcrow-semibold-webfont.woff2395.0 s22.4 KiB
m.vueling.com/assets/img/check-in/home-push/home-checkin2x.webp418.0 s20.7 KiB
m.vueling.com/common.899366586e059b1b.js482.0 s18.1 KiB
m.vueling.com/assets/img/myvueling/push-home-vy-club.png469.0 s17.9 KiB
www.google-analytics.com/analytics.js7200.0 s20.9 KiB
m.vueling.com/polyfills.dcdf2a094f8295e9.js420.0 s12.9 KiB
m.vueling.com/VvV_CU/-cR/1WF/N2BGojSq/SD/YGFXKQVZfQ/WkoG/Cm09AkYp86400.0 s28.8 KiB
static.vueling.com/corporative7/media/1187/roma-fco_091025ok.webp603013.0 s108.5 KiB
static.vueling.com/corporative7/media/1055/bc_mb_375x715_bg_140426w.webp603013.0 s85.2 KiB
static.vueling.com/corporative7/media/1108/edimburgo-edi.webp603013.0 s77.9 KiB
m.vueling.com/ajax-loader.94cdb3319868cfa7.gif110.0 s6.6 KiB
static.vueling.com/corporative7/media/1066/amsterdam-ams.webp603013.0 s63.0 KiB
static.vueling.com/corporative7/media/1153/malta-mla.webp603013.0 s56.6 KiB
s.go-mpulse.net/boomerang/PC6QT-A8FK6-WHT6M-VUAGT-35NQS604800.0 s56.1 KiB
m.vueling.com/8946.db870a66c8e5f2bc.js255.0 s5.1 KiB
m.vueling.com/runtime.8bee5dd196d2555b.js420.0 s4.6 KiB
m.vueling.com/assets/img/home/app-store/android.svg267.0 s3.4 KiB
cdn.cookielaw.org/consent/eb440cb9-982b-4dfe-9764-a5f339ad9985/otSDKStub.js86400.0 s7.5 KiB
static.vueling.com/corporative7/media/1017/urban_mobile_home.jpg2590214.0 s27.0 KiB
m.vueling.com/assets/img/home/logo-vueling.svg450.0 s2.6 KiB
static.vueling.com/corporative7/media/1016/playa_mobile.jpg2590214.0 s23.4 KiB
m.vueling.com/assets/img/home/fly-with-us/avios.svg155.0 s1.9 KiB
static.vueling.com/corporative7/media/1015/familia_mobile_home.jpg2590235.0 s17.5 KiB
m.vueling.com/assets/img/home/fly-with-us/hand-up.svg255.0 s1.6 KiB
m.vueling.com/assets/js/usabilla-dev.js451.0 s1.6 KiB
m.vueling.com/assets/img/home/fly-with-us/check-in.svg155.0 s1.3 KiB
cdn.cookielaw.org/logos/static/powered_by_logo.svg86400.0 s2.7 KiB
m.vueling.com/assets/img/home/social/instagram.svg11.0 s1.0 KiB
m.vueling.com/assets/img/home/social/youtube.svg291.0 s1.0 KiB
m.vueling.com/assets/img/loadingVueling2Airplanesv2.svg463.0 s1.0 KiB
m.vueling.com/assets/img/home/social/twitter.svg291.0 s1.0 KiB
m.vueling.com/assets/img/home/social/facebook.svg154.0 s862 B
m.vueling.com/VvV_CU/-cR/1WF/N2BGojSq/SD/YGFXKQVZfQ/Z1NX/EXYUJRlZ86400.0 s1.3 KiB
/eu-central-1.amazonaws/vueling-universal13.js?z=0.073516...0.0 ms365 B

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:7.329 source:map[column:32013 line:0 type:source-location url:https://m.vueling.com/6258.afba6971f62b6f1d.js urlProvider:network]] map[reflowTime:6.501 source:map[column:1.463006e+06 line:0 type:source-location url:https://m.vueling.com/main.589b2ac66d647595.js urlProvider:network]] map[reflowTime:9.29 source:map[column:1.485627e+06 line:0 type:source-location url:https://m.vueling.com/main.589b2ac66d647595.js urlProvider:network]] map[reflowTime:13.507 source:map[column:62730 line:0 type:source-location url:https://m.vueling.com/6258.afba6971f62b6f1d.js urlProvider:network]] map[reflowTime:1.126 source:map[column:707875 line:0 type:source-location url:https://m.vueling.com/main.589b2ac66d647595.js urlProvider:network]] map[reflowTime:8.094 source:map[column:705855 line:0 type:source-location url:https://m.vueling.com/main.589b2ac66d647595.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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
alt div.img-background-main > image-container.img-background-main__src > picture.ng-tns-c4244759221-3 > img.ng-tns-c4244759221-3
static.vueling.com/corporative7/media/1055/bc_mb_375x715_bg_140426w.webp84.9 KiB42.8 KiB
div.card-container > vy-card-link > div.card-container > div.card-container__header div.card-container > vy-card-link > div.card-container > div.card-container__header
m.vueling.com/assets/img/home/complete-your-travel/parking.png59.9 KiB25.7 KiB
URBAN AND CULTURAL div#your-destiny > cdk-virtual-scroll-viewport.cdk-virtual-scroll-viewport > div.cdk-virtual-scroll-content-wrapper > div.destiny-card
static.vueling.com/corporative7/media/1017/urban_mobile_home.jpg26.6 KiB20.8 KiB
div.card-container > vy-card-link > div.card-container > div.card-container__header div.card-container > vy-card-link > div.card-container > div.card-container__header
m.vueling.com/assets/img/home/complete-your-travel/cars.png28.2 KiB19.9 KiB
TO THE BEACH! div#your-destiny > cdk-virtual-scroll-viewport.cdk-virtual-scroll-viewport > div.cdk-virtual-scroll-content-wrapper > div.destiny-card
static.vueling.com/corporative7/media/1016/playa_mobile.jpg23.0 KiB17.3 KiB
div.card-container > vy-card-link > div.card-container > div.card-container__header div.card-container > vy-card-link > div.card-container > div.card-container__header
m.vueling.com/assets/img/home/complete-your-travel/hotels.webp48.0 KiB13.8 KiB
FAMILY div#your-destiny > cdk-virtual-scroll-viewport.cdk-virtual-scroll-viewport > div.cdk-virtual-scroll-content-wrapper > div.destiny-card
static.vueling.com/corporative7/media/1015/familia_mobile_home.jpg17.1 KiB11.3 KiB
vueling club home.ng-star-inserted > app-vy-club-push-home.ng-star-inserted > div.image > img
m.vueling.com/assets/img/myvueling/push-home-vy-club.png17.4 KiB10.0 KiB

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]
items: [map[duration:1266.258 label:Time to first byte subpart:timeToFirstByte] map[duration:4895.812 label:Resource load delay subpart:resourceLoadDelay] map[duration:160.829 label:Resource load duration subpart:resourceLoadDuration] map[duration:123.912 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-IMG
nodeLabel: alt
path: 1,HTML,2,BODY,1,DIV,1,VY-APP,2,MAIN,1,HOME,3,DIV,3,HOME-IMAGE-SLIDER,0,IMAGE-BACKGROUND,1,SWIPER-CONTAINER,0,SWIPER-SLIDE,0,DIV,0,IMAGE-CONTAINER,0,PICTURE,1,IMG
selector: div.img-background-main > image-container.img-background-main__src > picture.ng-tns-c4244759221-3 > img.ng-tns-c4244759221-3
snippet: <img _ngcontent-ng-c4244759221="" priority="true" width="100" height="100" class="ng-tns-c4244759221-3 picture-width ng-trigger ng-trigger-fadeIn" alt="alt" data-test-id="" loading="eager" fetchpriority="high" decoding="sync" ng-img="true" src="https://static.vueling.com/corporative7/media/1055/bc_mb_375x715_bg_140426…">

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG
nodeLabel: alt
path: 1,HTML,2,BODY,1,DIV,1,VY-APP,2,MAIN,1,HOME,3,DIV,3,HOME-IMAGE-SLIDER,0,IMAGE-BACKGROUND,1,SWIPER-CONTAINER,0,SWIPER-SLIDE,0,DIV,0,IMAGE-CONTAINER,0,PICTURE,1,IMG
selector: div.img-background-main > image-container.img-background-main__src > picture.ng-tns-c4244759221-3 > img.ng-tns-c4244759221-3
snippet: <img _ngcontent-ng-c4244759221="" priority="true" width="100" height="100" class="ng-tns-c4244759221-3 picture-width ng-trigger ng-trigger-fadeIn" alt="alt" data-test-id="" loading="eager" fetchpriority="high" decoding="sync" ng-img="true" src="https://static.vueling.com/corporative7/media/1055/bc_mb_375x715_bg_140426…">

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 3.3 s

Diagnostics

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTotal CPU TimeScript EvaluationScript Parse
m.vueling.com/5.6 s5.2 s2.9 ms
m.vueling.com/resources/5ca37ed9506e8073faf2465e595f1330830972a3a4ff75.4 s4.8 s43 ms
Unattributable2.0 s748 ms0.0 ms
m.vueling.com/main.589b2ac66d647595.js1.5 s1.2 s14 ms
/VvV_CU/-cR/1WF/N2BGojSq/SDi3LDVu/Uk9rKQVZfQ/JB4J/VWwANyU...1.1 s942 ms91 ms
www.googletagmanager.com/gtag/js?id=AW-807657239&cx=c&gtm=4e64f0h2900 ms805 ms36 ms
www.googletagmanager.com/gtm.js?id=GTM-NQHBFRM&gtm=4e64f0h2605 ms519 ms71 ms
m.vueling.com/VvV_CU/-cR/1WF/N2BGojSq/J1i3LDVuV9w9Xk/bBJnKQVZfQ/EHlz/bBFRMAUC555 ms454 ms85 ms
cdn.cookielaw.org/scripttemplates/6.38.0/otBannerSdk.js527 ms352 ms58 ms
www.googletagmanager.com/gtm.js?id=GTM-56RKXM6523 ms350 ms104 ms
www.googletagmanager.com/gtag/js?id=G-Y2R5C29F9Q&cx=c&gtm=4e64f0h2388 ms327 ms56 ms
m.vueling.com/scripts.5f11d3cd0711642e.js350 ms203 ms47 ms
/trk/4/s/a-02a953bb/p/m.vueling.com/933881050-0?mr=t16744...292 ms228 ms3.9 ms
cdn.cookielaw.org/consent/eb440cb9-982b-4dfe-9764-a5f339ad9985/OtAutoBlock.js208 ms25 ms167 ms
cdn.quantummetric.com/qscripts/quantum-vueling.js199 ms137 ms55 ms
www.googletagmanager.com/gtag/js?id=DC-9971265&cx=c&gtm=4e64f0h2198 ms153 ms42 ms
www.googletagmanager.com/gtag/js?id=AW-1070364677104 ms64 ms38 ms
se.monetate.net/js/2/a-02a953bb/p/m.vueling.com/custom.js103 ms71 ms32 ms
cdn.cookielaw.org/consent/eb440cb9-982b-4dfe-9764-a5f339ad9985/otSDKStub.js102 ms84 ms1.9 ms
s.go-mpulse.net/boomerang/PC6QT-A8FK6-WHT6M-VUAGT-35NQS94 ms63 ms25 ms
m.vueling.com/VvV_CU/-cR/1WF/N2BGojSq/SD/YGFXKQVZfQ/WkoG/Cm09AkYp84 ms76 ms7.4 ms
/trk/4/s/a-02a953bb/p/m.vueling.com/933881050-1?mr=t16744...80 ms66 ms3.2 ms
www.googletagmanager.com/gtag/js?id=AW-1070364677&cx=c&gtm=4e64f0h277 ms32 ms44 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation16.9 s
Other2.0 s
Script Parsing & Compilation1.0 s
Style & Layout530 ms
Garbage Collection375 ms
Parse HTML & CSS203 ms
Rendering94 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
The page has an unload handler in the main frame.Actionable
The page has an unload handler in a sub frame.Actionable

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 59.9 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
vueling club home.ng-star-inserted > app-vy-club-push-home.ng-star-inserted > div.image > img
m.vueling.com/assets/img/myvueling/push-home-vy-club.png
Collect Avios, fly for free app-fly-with-us.ng-star-inserted > div.fly-with-us-container > div.fly-with-us-container__content > img
m.vueling.com/assets/img/home/fly-with-us/avios.svg
No admin charges app-fly-with-us.ng-star-inserted > div.fly-with-us-container > div.fly-with-us-container__content > img
m.vueling.com/assets/img/home/fly-with-us/hand-up.svg
app-store button.mdc-button > span.mdc-button__label > span > img
m.vueling.com/assets/img/home/app-store/android.svg
Free online check-in app-fly-with-us.ng-star-inserted > div.fly-with-us-container > div.fly-with-us-container__content > img
m.vueling.com/assets/img/home/fly-with-us/check-in.svg
Vueling app-home-footer > div.footer > span.footer__logo > img
m.vueling.com/assets/img/home/logo-vueling.svg
Vueling youtube div.social > div.social__rss > span.social__rss__item > img
m.vueling.com/assets/img/home/social/youtube.svg
Vueling instagram div.social > div.social__rss > span.social__rss__item > img
m.vueling.com/assets/img/home/social/instagram.svg
Vueling twitter div.social > div.social__rss > span.social__rss__item > img
m.vueling.com/assets/img/home/social/twitter.svg
Vueling facebook div.social > div.social__rss > span.social__rss__item > img
m.vueling.com/assets/img/home/social/facebook.svg

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

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

Accessibility

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

ARIA

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
COOKIE POLICY We use our own and third-party cookies for analytical, personali… body.ui-mobile-viewport > div#onetrust-consent-sdk > div#onetrust-banner-sdk

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

Best practices

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

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Cookie policy div#onetrust-group-container > div#onetrust-policy > p#onetrust-policy-text > a.ot-cookie-policy-link
Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
Image elements have `[alt]` attributes
`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.
Links have a discernible name
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
Heading elements appear in a sequentially-descending order
Document has a main landmark.
Deprecated ARIA roles were not used
`[accesskey]` values are unique
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Form elements have associated labels
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
77

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
Unload event listeners are deprecated and will be removed.

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

Description
The script resource is behind a redirect, which is disallowed.
Uses HTTPS
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Displays images with correct aspect ratio
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
No issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destinationLink Text
www.vueling.com/en/customer-services/cookie-policyMore information

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

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

Send Feedback