Skip to content
https://aircanada.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.

28

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
www.aircanada.com/home/vendor.436b440afc06d651.js18408.0 s328.5 KiB
www.aircanada.com/home/main.d033cf8802380eb9.js21566.0 s200.6 KiB
www.aircanada.com/6jkv/xGJ0/jfQ_/WDDX/sw/Y7OaLzwrkOJzpNXE5S/EltsWg/dQd/0ewtKPG0B21600.0 s177.6 KiB
/6jkv/xGJ0/jfQ_/WDDX/sw/SbOaLzufkOYD/UkZyWg/VGs/fOBwefmYN...21600.0 s153.5 KiB
assets.adobedtm.com/14307738146c/2d72065f81e7/launch-9e3b3ffc9904.min.js3600.0 s96.4 KiB
www.aircanada.com/assets/b23d8f289e32edec2065f3c335af8c367001194a011600.0 s62.4 KiB
cdn.cookielaw.org/scripttemplates/202408.1.0/otBannerSdk.js86400.0 s110.4 KiB
www.aircanada.com/home/867.5c6ecab26fe17306.js16090.0 s58.7 KiB
p11.techlab-cdn.com/e/65226_747628217.js600.0 s32.7 KiB
www.aircanada.com/home/298.70b89edf9b45d9c6.js320.0 s24.5 KiB
p11.techlab-cdn.com/e/65319_1825172608.js600.0 s18.3 KiB
/ac/applications/achomebeta/content/1.0.2140/assets/img/l...2584644.0 s177.3 KiB
www.aircanada.com/home/978.ae7e6789f96a9634.js315.0 s12.9 KiB
/ac/applications/achomebeta/content/1.0.2140/assets/img/n...2584651.0 s108.2 KiB
www.aircanada.com/home/styles.8dc6e083c14ad84a.css16958.0 s11.9 KiB
www.aircanada.com/home/polyfills.da2356291a9cd820.js25707.0 s11.7 KiB
/ac/applications/achomebeta/content/1.0.2140/assets/img/n...2584645.0 s69.0 KiB
p11.techlab-cdn.com/e/65257_1825202461.js600.0 s7.0 KiB
/logos/082a8d33-cfc3-4da9-b069-db3379cdd69f/018dd13f-b436...86400.0 s15.6 KiB
www.aircanada.com/home/544.0911ceee1c669e46.js317.0 s6.5 KiB
www.aircanada.com/home/57.a29490220bf04e01.js70235.0 s13.1 KiB
s.go-mpulse.net/boomerang/95K7G-R6KA6-85CWB-9YW8G-QLP3N604800.0 s56.5 KiB
www.aircanada.com/home/124.83811dadc72a01ce.js284.0 s5.3 KiB
/ac/applications/achomebeta/content/1.0.2140/assets/img/p...2584663.0 s53.0 KiB
/ac/applications/achomebeta/content/1.0.2140/assets/img/g...2584651.0 s51.6 KiB
/ac/applications/achomebeta/content/1.0.2140/assets/img/n...2584645.0 s49.8 KiB
www.aircanada.com/home/926.ce90fc4e3a1c539b.js65814.0 s9.6 KiB
www.aircanada.com/home/331.6d01cd94d534631d.js295.0 s4.1 KiB
cdn.cookielaw.org/scripttemplates/otSDKStub.js86400.0 s9.1 KiB
www.aircanada.com/home/274.d6426a9b204844b1.js44504.0 s7.0 KiB
www.aircanada.com/home/575.5100448214a90582.js65373.0 s7.7 KiB
www.aircanada.com/home/770.93ff7e19627a0a47.js7832.0 s4.7 KiB
/ac/applications/achomebeta/content/1.0.2140/assets/img/p...2584660.0 s36.5 KiB
www.aircanada.com/home/19.a44d73de03d5fc6b.js20880.0 s5.1 KiB
www.aircanada.com/home/860.1fcfdc4651f7805a.js38894.0 s5.4 KiB
www.aircanada.com/home/940.6c18e3c0aed3e563.js14976.0 s2.9 KiB
www.aircanada.com/home/common.a3f77af452d198f5.js66442.0 s4.1 KiB
p11.techlab-cdn.com/e/64885_1825202492.js600.0 s2.0 KiB
www.aircanada.com/home/runtime.453919a8577c3fd2.js43726.0 s2.7 KiB
cdn.cookielaw.org/logos/static/powered_by_logo.svg86400.0 s2.6 KiB
www.aircanada.com/home/695.25262becbe9f7ae5.js22253.0 s1.5 KiB
/14307738146c/2d72065f81e7/a20a2f2f98c6/RC2e8efcc5990847a...3600.0 s1.0 KiB
/14307738146c/2d72065f81e7/a20a2f2f98c6/RC3aa392ec6b714af...3600.0 s967 B
/ac/applications/achomebeta/content/1.0.2140/assets/img/n...2584742.0 s7.3 KiB
/14307738146c/2d72065f81e7/a20a2f2f98c6/RC6cb52b49b6fa427...3600.0 s746 B
/14307738146c/2d72065f81e7/a20a2f2f98c6/RC6bb2ba695e064cf...3600.0 s681 B
www.aircanada.com/home/scripts.bdab446f78523dc8.js66770.0 s1.0 KiB
/ac/applications/achomebeta/content/1.0.2140/assets/img/l...2584644.0 s3.5 KiB
/ac/applications/achomebeta/content/1.0.2140/assets/img/l...2584665.0 s2.0 KiB
/ac/applications/achomebeta/content/1.0.2140/assets/img/l...2584645.0 s862 B

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:2.435 source:map[type:text value:[unattributed]]] map[reflowTime:2.164 source:map[column:942027 line:0 type:source-location url:https://www.aircanada.com/home/main.d033cf8802380eb9.js urlProvider:network]] map[reflowTime:5.86 source:map[column:15207 line:0 type:source-location url:https://www.aircanada.com/home/544.0911ceee1c669e46.js urlProvider:network]] map[reflowTime:20.604 source:map[column:3666 line:0 type:source-location url:https://www.aircanada.com/home/544.0911ceee1c669e46.js urlProvider:network]] map[reflowTime:4.1 source:map[column:23504 line:0 type:source-location url:https://www.aircanada.com/home/57.a29490220bf04e01.js urlProvider:network]] map[reflowTime:11.606 source:map[column:1.28466e+06 line:0 type:source-location url:https://www.aircanada.com/home/main.d033cf8802380eb9.js urlProvider:network]]]

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:415.69 label:Time to first byte subpart:timeToFirstByte] map[duration:1908.412 label:Resource load delay subpart:resourceLoadDelay] map[duration:27.934 label:Resource load duration subpart:resourceLoadDuration] map[duration:177.526 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-DIV
nodeLabel: div.ngx-ac-container > div.ac-primary-padded-content > ac-dynamic-bk.main-header-container > div.gradient
path: 1,HTML,1,BODY,0,AC-HOME-ROOT,0,DIV,7,DIV,0,MAIN,0,DIV,3,AC-FLIGHTS,0,DIV,0,DIV,0,DIV,0,AC-DYNAMIC-BK,0,DIV
selector: div.ngx-ac-container > div.ac-primary-padded-content > ac-dynamic-bk.main-header-container > div.gradient
snippet: <div class="gradient main-wrapper bg-animation-desktop" style="background-image: url(&quot;https://kilo-content.aircanada.com/ac/applications/…&quot;);">

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-DIV
nodeLabel: div.ngx-ac-container > div.ac-primary-padded-content > ac-dynamic-bk.main-header-container > div.gradient
path: 1,HTML,1,BODY,0,AC-HOME-ROOT,0,DIV,7,DIV,0,MAIN,0,DIV,3,AC-FLIGHTS,0,DIV,0,DIV,0,DIV,0,AC-DYNAMIC-BK,0,DIV
selector: div.ngx-ac-container > div.ac-primary-padded-content > ac-dynamic-bk.main-header-container > div.gradient
snippet: <div class="gradient main-wrapper bg-animation-desktop" style="background-image: url(&quot;https://kilo-content.aircanada.com/ac/applications/…&quot;);">

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.

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
value: no origins were preconnected
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.

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
Noticias sobre viajes y novedades section.news-and-updates__wrapper > div.news-and-updates__requirements > picture.news-and-updates__requirements__background > img
/ac/applications/achomebeta/content/1.0.2140/assets/img/n...107.7 KiB82.1 KiB
div.cards-carrousel__card > ac-card > div.ac-card > img.ac-card-img div.cards-carrousel__card > ac-card > div.ac-card > img.ac-card-img
/ac/applications/achomebeta/content/1.0.2140/assets/img/n...68.3 KiB48.8 KiB
div.cards-carrousel__card > ac-card > div.ac-card > img.ac-card-img div.cards-carrousel__card > ac-card > div.ac-card > img.ac-card-img
/ac/applications/achomebeta/content/1.0.2140/assets/img/n...49.1 KiB29.6 KiB
div.pos-banner-component > div.pos-card-container > picture.ng-star-inserted > img.pos-card-container__image div.pos-banner-component > div.pos-card-container > picture.ng-star-inserted > img.pos-card-container__image
/ac/applications/achomebeta/content/1.0.2140/assets/img/p...35.8 KiB20.1 KiB

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation8.3 s
Other1.4 s
Style & Layout760 ms
Script Parsing & Compilation343 ms
Rendering258 ms
Parse HTML & CSS241 ms
Garbage Collection214 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
Pages with cache-control:no-store header cannot enter back/forward cache.Actionable
The page has an unload handler in a sub frame.Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.Not 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 41.6 KiB
URLTransfer SizeEst Savings
21.0 KiB18.7 KiB
@keyframes fadeIn{0%{opacity:0} …12.5 KiB12.3 KiB
@keyframes _ngcontent-ng-c2003155099_fadeIn{0%{opacity:0} …11.0 KiB10.6 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
A Star Alliance member Se abre en una ventana nueva div.ngx-ac-wrapper > div.ngx-ac-libra-footer-star-alliance > a.ng-star-inserted > img.ng-star-inserted
/ac/applications/achomebeta/content/1.0.2140/assets/img/l...

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

●Layout shift culprits
●Document request latency
●Optimize DOM size
●Font display
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●User Timing marks and measures 40 user timings
●Avoid long main-thread tasks 20 long tasks found
●Avoid non-composited animations 1 animated element found
●Network Requests
●Network Round Trip Times 20 ms
●Server Backend Latencies 210 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 410 ms
●Avoid large layout shifts 9 layout shifts found
○INP breakdown
90

Accessibility

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

ARIA

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Disfrute del control aduanero previo de EE. UU. en Canadá Siéntase como un loc… div.peak-scroller-container > div.carousel-container > div.cards-carrousel__cards-container > div.cards-carrousel__card
¡Que no se lo cuenten! Este verano, esté donde el mondo cobra vida, en ciudade… div.peak-scroller-container > div.carousel-container > div.cards-carrousel__cards-container > div.cards-carrousel__card
Redefina su forma de relajarse Vuele con total comodidad en la clase Signature… div.peak-scroller-container > div.carousel-container > div.cards-carrousel__cards-container > div.cards-carrousel__card

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

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Reservar con puntos Aeroplan abc-checkbox.search-type-toggle-checkbox > div.abc-form-element-container > div.abc-form-element-wrapper > input#bkmg-mobile-tablet_searchTypeToggle

These are opportunities to improve keyboard navigation in your application.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Condiciones de uso div.ngx-ac-libra-footer-address-wrapper > div.ngx-ac-libra-footer-additional-links > div.ngx-ac-libra-footer-additional-link > a
Política de privacidad div.ngx-ac-libra-footer-address-wrapper > div.ngx-ac-libra-footer-additional-links > div.ngx-ac-libra-footer-additional-link > a
Condiciones generales de transporte y tarifas div.ngx-ac-libra-footer-address-wrapper > div.ngx-ac-libra-footer-additional-links > div.ngx-ac-libra-footer-additional-link > a
Política sobre cookies y tecnologías de seguimiento div.ngx-ac-libra-footer-address-wrapper > div.ngx-ac-libra-footer-additional-links > div.ngx-ac-libra-footer-additional-link > a
Sello div.ngx-ac-libra-footer-address-wrapper > div.ngx-ac-libra-footer-additional-links > div.ngx-ac-libra-footer-additional-link > a

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
Unirse ahora ngx-ac-aco-user-menu.ng-tns-c2490803833-0 > div.libra-controls > abc-button.libra-join > button#libraUserMenu-joinNow
Descargue nuestra aplicación móvil Acceda a su tarjeta de Aeroplan digital en l… div.ngx-ac-wrapper > div.ngx-ac-libra-footer-column > div.ngx-ac-libra-footer-award-container > div.ngx-ac-libra-footer-app-install
nuestra política sobre cookies y tecnologías de seguimiento. div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link
○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●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.
●`[accesskey]` values are unique
●`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
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●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
○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.
○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.
○`[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.
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
77

Best Practices

General

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
Failed to load resource: the server responded with a status of 403 ()

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

●Uses HTTPS
●Avoids 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
83

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
/es/es/aco/home/fly/onboard/cabin-features/signature-serv...Más información

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

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
Ir a reservar un vuelo div#skipNav > ul.ngx-ac-skip-link-list > li.ngx-ac-skip-link-item > a.ngx-ac-skip-link
Ir a contenido div#skipNav > ul.ngx-ac-skip-link-list > li.ngx-ac-skip-link-item > a.ngx-ac-skip-link
Ir a navegación principal div#skipNav > ul.ngx-ac-skip-link-list > li.ngx-ac-skip-link-item > a.ngx-ac-skip-link
Ir a los enlaces de pie de página div#skipNav > ul.ngx-ac-skip-link-list > li.ngx-ac-skip-link-item > a.ngx-ac-skip-link

To appear in search results, crawlers need access to your app.

○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
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`
○robots.txt is valid

Send Feedback