Skip to content
https://singaporeair.com

Lighthouse Desktop

· 0 checks — Desktop 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.

53

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.singaporeair.com/assets/scripts/ins_260415_v1.js0.0 ms428.4 KiB
www.singaporeair.com/assets/scripts/widget-n2607.js0.0 ms349.1 KiB
www.singaporeair.com/assets/digitalweb/build/p-eebaef32.entry.js0.0 ms156.8 KiB
/UsehSITbjfvYl/Tj2y/aBxOHXuRxY/1cYEJmbLtbhNmJ1rEm/XiFNdAE...21600.0 s179.3 KiB
/UsehSITbjfvYl/Tj2y/aBxOHXuRxY/thYEJmYSQ7NE/ck9YdAE/eiB/p...21600.0 s154.0 KiB
www.singaporeair.com/assets/scripts/homepagepopup-n2607.js0.0 ms73.5 KiB
www.singaporeair.com/assets/scripts/lib1-n2607.js0.0 ms52.0 KiB
www.singaporeair.com/assets/scripts/login-n2607.js0.0 ms50.4 KiB
www.singaporeair.com/assets/scripts/lib2-n2607.js0.0 ms31.1 KiB
www.singaporeair.com/assets/scripts/lib0-n2607.js0.0 ms29.0 KiB
www.singaporeair.com/assets/scripts/toolbar-n2607.js0.0 ms28.4 KiB
www.singaporeair.com/assets/scripts/lib3-n2607.js0.0 ms28.0 KiB
www.singaporeair.com/assets/digitalweb/build/digitalweb-components-v17.css0.0 ms20.8 KiB
www.singaporeair.com/assets/style/home-core-n2607.css0.0 ms15.5 KiB
www.singaporeair.com/assets/digitalweb/build/p-1d257de5.js0.0 ms14.4 KiB
www.singaporeair.com/UsehSITbjfvYl/Tj2y/aBxOHXuRxY/thYE3c/JlUmdAE/MTQ/ScGh8UUEq86400.0 s28.2 KiB
www.singaporeair.com/assets/digitalweb/build/p-20313209.js0.0 ms10.2 KiB
www.singaporeair.com/ruxitagentjs_ICA7NVfghqrux_10333260303165926.js1195278.0 s86.0 KiB
www.singaporeair.com/assets/digitalweb/build/p-3d3f98b9.js0.0 ms7.3 KiB
s.go-mpulse.net/boomerang/URWKD-92TAT-8TXKV-MQBNA-5JJXP604800.0 s56.8 KiB
www.singaporeair.com/assets/digitalweb/build/digitalweb-components-v17.esm.js0.0 ms4.7 KiB
www.singaporeair.com/assets/style/fonts-n2607.css0.0 ms3.9 KiB
www.singaporeair.com/assets/NuData/generated/nudata_tracker.js0.0 ms3.5 KiB
www.singaporeair.com/assets/digitalweb/build/p-00532f24.js0.0 ms3.1 KiB
www.singaporeair.com/assets/fonts/sigvar_serial-light-webfont.ttf1209600.0 s29.7 KiB
www.singaporeair.com/assets/fonts/proximanova-light-webfont.ttf1209600.0 s27.3 KiB
www.singaporeair.com/assets/fonts/proximanova-bold-webfont.woff21209600.0 s23.2 KiB
www.singaporeair.com/assets/fonts/proximanova-regular-webfont.woff21209600.0 s22.6 KiB
www.singaporeair.com/assets/fonts/proximanova-semibold-webfont.woff21209600.0 s22.5 KiB
www.singaporeair.com/assets/fonts/sia.woff1209600.0 s22.2 KiB
www.singaporeair.com/assets/fonts/proximanova-light-webfont.woff21209600.0 s22.2 KiB
www.singaporeair.com/assets/fonts/sia.ttf1209600.0 s22.0 KiB
www.singaporeair.com/assets/fonts/sigvar_serial-light-webfont.woff21209600.0 s22.0 KiB
www.singaporeair.com/assets/digitalweb/build/p-73f15aa2.js0.0 ms1.9 KiB
www.singaporeair.com/assets/digitalweb/build/p-351b7322.js0.0 ms1.6 KiB
www.singaporeair.com/UsehSITbjfvYl/Tj2y/aBxOHXuRxY/thYE3c/JlUmdAE/fHB/4Ykc-CkhY86400.0 s1.8 KiB
www.singaporeair.com/assets/images/svg/singapore-airlines.svg2577582.0 s7.1 KiB
www.singaporeair.com/assets/images/svg/icon-copy-blue.svg2577582.0 s4.2 KiB
www.singaporeair.com/assets/images/svg/icons/search.svg2577586.0 s4.2 KiB
www.singaporeair.com/assets/images/svg/icons/chevron-blue.svg2577581.0 s4.2 KiB
www.singaporeair.com/assets/images/svg/icons/chevron.svg2577583.0 s4.1 KiB
www.singaporeair.com/assets/images/svg/profile.svg2577582.0 s4.0 KiB
www.singaporeair.com/assets/images/svg/icons/tooltip-close.svg2577583.0 s3.9 KiB
www.singaporeair.com/assets/images/svg/sparkleFLR.svg2577583.0 s3.9 KiB
www.singaporeair.com/assets/images/svg/icons/ico-alert--orange.svg2577581.0 s3.8 KiB
www.singaporeair.com/assets/fonts/sia-1.woff1209600.0 s3.4 KiB
www.singaporeair.com/assets/fonts/sia-1.ttf1209600.0 s3.4 KiB
www.singaporeair.com/assets/fonts/sia-3.woff1209600.0 s2.0 KiB
www.singaporeair.com/assets/fonts/sia-3.ttf1209600.0 s2.0 KiB
www.singaporeair.com/assets/images/svg/logos/tr.svg2577582.0 s1.9 KiB
www.singaporeair.com/assets/images/svg/logos/sq.svg2577583.0 s1.8 KiB
www.singaporeair.com/assets/images/svg/logos/si.svg2577582.0 s1.8 KiB
/v2/collect?p=eyJyZWYiOiJodHRwczovL3d3dy5zaW5nYXBvcmVhaXI...14400.0 s220 B
www.singaporeair.com/assets/images/svg/icons/dropdown.svg2577583.0 s1.5 KiB
www.singaporeair.com/assets/images/svg/icons/ico-clock.svg2577587.0 s1.4 KiB
/v2/collect?p=eyJyZWYiOiJodHRwczovL3d3dy5zaW5nYXBvcmVhaXI...14400.0 s143 B
/v2/collect?p=eyJyZWYiOiJodHRwczovL3d3dy5zaW5nYXBvcmVhaXI...14400.0 s97 B
/v2/collect?p=eyJyZWYiOiJodHRwczovL3d3dy5zaW5nYXBvcmVhaXI...14400.0 s97 B
/v2/collect?p=eyJyZWYiOiJodHRwczovL3d3dy5zaW5nYXBvcmVhaXI...14400.0 s97 B
/v2/collect?p=eyJyZWYiOiJodHRwczovL3d3dy5zaW5nYXBvcmVhaXI...14400.0 s96 B
www.singaporeair.com/assets/fonts/sigvar_serial-regular-webfont.woff21209600.0 s0 B

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:218.57 label:Time to first byte subpart:timeToFirstByte] map[duration:1622.472 label:Resource load delay subpart:resourceLoadDelay] map[duration:18.361 label:Resource load duration subpart:resourceLoadDuration] map[duration:1243.893 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-DIV
nodeLabel: div#masthead > div.header_wrapper > div.masthead_wrapper > div#masthead_banner_image
path: 1,HTML,1,BODY,7,DIV,4,DIV,0,DIV,0,DIV,1,DIV
selector: div#masthead > div.header_wrapper > div.masthead_wrapper > div#masthead_banner_image
snippet: <div class="blurcontain blur_image ins-set-banner-c12817" id="masthead_banner_image" style="cursor: pointer;">

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#masthead > div.header_wrapper > div.masthead_wrapper > div#masthead_banner_image
path: 1,HTML,1,BODY,7,DIV,4,DIV,0,DIV,0,DIV,1,DIV
selector: div#masthead > div.header_wrapper > div.masthead_wrapper > div#masthead_banner_image
snippet: <div class="blurcontain blur_image ins-set-banner-c12817" id="masthead_banner_image" style="cursor: pointer;">

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

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.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 40 ms 24.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.

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 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 Evaluation1.9 s
Other358 ms
Script Parsing & Compilation181 ms
Style & Layout65 ms
Garbage Collection55 ms
Parse HTML & CSS47 ms
Rendering16 ms

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 2.8 KiB

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
●Forced reflow
●Improve image delivery
●Modern HTTP
●Optimize viewport for mobile
●Minify JavaScript
●Avoid long main-thread tasks 7 long tasks found
●Avoid non-composited animations 4 animated elements found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 20 ms
●Server Backend Latencies 260 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 210 ms
●Avoid large layout shifts 4 layout shifts found
○INP breakdown
○User Timing marks and measures
83

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

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body > img body > img

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.

Tables and lists

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
RESERVAR UN VIAJE div.contents_wrapper > div.tab-view-container > div.tab-title-container > li.tab-title-container__list
GESTIONAR RESERVA div.contents_wrapper > div.tab-view-container > div.tab-title-container > li.tab-title-container__list
FACTURACIÓN div.contents_wrapper > div.tab-view-container > div.tab-title-container > li.tab-title-container__list
ESTADO DEL VUELO div.contents_wrapper > div.tab-view-container > div.tab-title-container > li.tab-title-container__list
HORARIOS DE VUELOS div.contents_wrapper > div.tab-view-container > div.tab-title-container > li.tab-title-container__list

These are opportunities to improve the experience of reading tabular or list data using 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.

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
GESTIONAR RESERVA div.contents_wrapper > div.tab-view-container > div.tab-title-container > li.tab-title-container__list
FACTURACIÓN div.contents_wrapper > div.tab-view-container > div.tab-title-container > li.tab-title-container__list
ESTADO DEL VUELO div.contents_wrapper > div.tab-view-container > div.tab-title-container > li.tab-title-container__list
HORARIOS DE VUELOS div.contents_wrapper > div.tab-view-container > div.tab-title-container > li.tab-title-container__list

These are opportunities to improve keyboard navigation in your application.

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
No div.toolbar__content > ul.toolbar__control > li > a.languageSwitch
2 div.dwc--LocaleSelector__Root > span.dwc--LocaleSelector__HideNonDesktop > span.dwc--SiaHeader__HeaderFeedback > a.dwc--SiaHeader__FeedbackHelp
INICIAR SESIÓN span > div.dwc--SiaHeader__NavLogin > div.dwc--SiaHeader__NavLoginCell > button.dwc--SiaHeader__NavLink
REGISTRARSE span > div.dwc--SiaHeader__NavLogin > div.dwc--SiaHeader__NavLoginCell > a.dwc--SiaHeader__NavLink
DISCOVER MORE div.masthead_copy > div.masthead_content > p.masthead_intro_link > a.sp-custom-c12817
○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
●Form elements have associated labels
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○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
○Heading elements appear in a sequentially-descending order
○`<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.
○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
Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.

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
A bad HTTP response code (404) was received when fetching the script.
A bad HTTP response code (404) was received when fetching the script.
Failed to load resource: net::ERR_NAME_NOT_RESOLVED
Permissions policy violation: payment is not allowed in this document.
Permissions policy violation: payment is not allowed in this document.
TypeError: Failed to register a ServiceWorker for scope ('https://www.singaporeair.com/') with script ('https://www.singaporeair.com/akam-sw.js'): A bad HTTP response code (404) was received when fetching the script.
TypeError: Failed to register a ServiceWorker for scope ('https://www.singaporeair.com/') with script ('https://www.singaporeair.com/akam-sw.js'): A bad HTTP response code (404) was received when fetching the script.

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
●Mitigate DOM-based XSS with Trusted Types
●Detected JavaScript libraries
○Redirects HTTP traffic to HTTPS
○Use a strong HSTS policy
○Ensure proper origin isolation with COOP
○Mitigate clickjacking with XFO or CSP
75

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.

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
No div.toolbar__content > ul.toolbar__control > li > a.languageSwitch
AÑADIR OTRO APELLIDO form#gds-retrieval-form-new > div.add-another-lastname > div.divider-line-container > a.add-lastname-button

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

Content Best Practices

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body > img body > img

Canonical links suggest which URL to show in search results. Learn more about canonical links.

Why this matters

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

Source: MDN Permissions-Policy

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

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

Send Feedback