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

43

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
cdn.cookielaw.org/scripttemplates/202502.1.0/otBannerSdk.js86400.0 s114.9 KiB
js.monitor.azure.com/scripts/b/ai.2.gbl.min.js1800.0 s46.2 KiB
www.norwegian.com/style-bundle/cms-brand.css?v=bLHHIb7YsgNRVYXxfbSQhVOIMeI86403.0 s73.6 KiB
www.norwegian.com/Images/countries-flags/es.svg86401.0 s49.1 KiB
www.norwegian.com/Images/countries-flags/us.svg86401.0 s37.7 KiB
www.norwegian.com/Images/countries-flags/uk.svg86401.0 s26.5 KiB
/logos/1a04bf16-c960-4bea-8ca5-183b663691f3/019445ca-840b...86400.0 s21.3 KiB
/cdn-cgi/challenge-platform/h/g/scripts/jsd/b0a7532ac8ec/...14400.0 s11.8 KiB
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...86400.0 s10.7 KiB
cdn.cookielaw.org/scripttemplates/otSDKStub.js86400.0 s9.1 KiB
www.norwegian.com/Images/countries-flags/fi.svg86401.0 s6.0 KiB
www.norwegian.com/Images/countries-flags/se.svg86401.0 s5.7 KiB
www.norwegian.com/Images/countries-flags/no.svg86401.0 s5.4 KiB
www.norwegian.com/Images/countries-flags/pl.svg86401.0 s4.6 KiB
www.norwegian.com/Images/countries-flags/nl.svg86401.0 s4.5 KiB
www.norwegian.com/Images/countries-flags/it.svg86401.0 s4.5 KiB
www.norwegian.com/Images/countries-flags/de.svg86401.0 s4.5 KiB
www.norwegian.com/Images/countries-flags/dk.svg86401.0 s4.4 KiB
www.norwegian.com/Images/countries-flags/fr.svg86401.0 s4.2 KiB
www.norwegian.com/script-bundle/lazysizes.js?v=3HmW99h1vglLXWpaWVnJHw-kycI86402.0 s3.4 KiB
cdn.cookielaw.org/logos/static/powered_by_logo.svg86400.0 s2.6 KiB
www.norwegian.com/Images/countries-flags/en.svg86401.0 s2.3 KiB
www.norwegian.com/Util/Find/epi-util/find.js86402.0 s2.3 KiB
/script-bundle/plainPageController.js?v=BA6egZn3-V1L5_2N_...86402.0 s2.3 KiB
www.norwegian.com/Content/img/ident.svg86401.0 s2.1 KiB
www.norwegian.com/Content/img/ident-mobile.svg86401.0 s1.5 KiB
/script-bundle/accessibility-cookie.js?v=dXpbs49Ir3bAAlKN...86402.0 s320 B

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.

URLTransfer SizeDuration
www.norwegian.com/style-bundle/cms-brand.css?v=bLHHIb7YsgNRVYXxfbSQhVOIMeI73.6 KiB752 ms
cdn.cookielaw.org/scripttemplates/otSDKStub.js9.1 KiB766 ms

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.

URLEst Savings
/Content/webfonts/NorwegianTextPro-Regular.woff2?v=2yPPwI...15 ms
/Content/webfonts/NorwegianTextPro-Bold.woff2?v=2yPPwIqAJ...15 ms
/Content/webfonts/NorwegianDisplayPro-Bold.woff2?v=2yPPwI...10 ms

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

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: 754 ms
URLTime Spent
norwegian.com/754 ms
www.norwegian.com/0.0 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

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: 150 ms 11.5 KiB
URLTransfer SizeEst Savings
www.norwegian.com/style-bundle/cms-brand.css?v=bLHHIb7YsgNRVYXxfbSQhVOIMeI73.6 KiB11.5 KiB

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: 750 ms 90.0 KiB
URLTransfer SizeEst Savings
www.norwegian.com/style-bundle/cms-brand.css?v=bLHHIb7YsgNRVYXxfbSQhVOIMeI73.4 KiB72.2 KiB
21.5 KiB17.8 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.

Estimated savings: 1.5 s 240.1 KiB
URLTransfer SizeEst Savings
www.googletagmanager.com/gtag/js?id=G-XMQZZ1BMXF&cx=c&gtm=4e64e1&bs=ctrl160.8 KiB66.3 KiB
www.googletagmanager.com/gtag/js?id=DC-5877806&cx=c&gtm=4e64e1&bs=ctrl130.5 KiB59.2 KiB
cdn.cookielaw.org/scripttemplates/202502.1.0/otBannerSdk.js114.8 KiB59.0 KiB
www.googletagmanager.com/gtm.js?id=GTM-NVL4JDR213.9 KiB55.7 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTotal CPU TimeScript EvaluationScript Parse
www.googletagmanager.com/gtm.js?id=GTM-NVL4JDR1.4 s1.2 s103 ms
Unattributable730 ms207 ms0.0 ms
cdn.cookielaw.org/scripttemplates/202502.1.0/otBannerSdk.js499 ms229 ms110 ms
www.norwegian.com/script-bundle/lazysizes.js?v=3HmW99h1vglLXWpaWVnJHw-kycI486 ms73 ms1.3 ms
www.norwegian.com/cdn-cgi/challenge-platform/scripts/jsd/main.js373 ms356 ms3.3 ms
www.norwegian.com/354 ms63 ms9.6 ms
www.googletagmanager.com/gtag/js?id=G-XMQZZ1BMXF&cx=c&gtm=4e64e1&bs=ctrl345 ms271 ms62 ms
js.monitor.azure.com/scripts/b/ai.2.gbl.min.js276 ms216 ms30 ms
www.googletagmanager.com/gtag/js?id=DC-5877806&cx=c&gtm=4e64e1&bs=ctrl239 ms188 ms49 ms
cdn.cookielaw.org/scripttemplates/otSDKStub.js57 ms37 ms4.6 ms
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...56 ms37 ms4.4 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 Evaluation2.9 s
Other1.0 s
Script Parsing & Compilation381 ms
Style & Layout206 ms
Parse HTML & CSS167 ms
Garbage Collection110 ms
Rendering51 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

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
Norwegian Air Shuttle ASA div.menu__content > div.menu__branding > a > img.menu__logo
www.norwegian.com/Content/img/ident-mobile.svg

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

●Layout shift culprits
●Optimize DOM size
●Forced reflow
●Improve image delivery
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify JavaScript
●Avoids enormous network payloads Total size was 1,237 KiB
●User Timing marks and measures 7 user timings
●Avoid long main-thread tasks 16 long tasks found
●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 250 ms
●Avoid large layout shifts 1 layout shift found
○INP breakdown
○LCP request discovery
○Avoid non-composited animations
95

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 attributes are only allowed on an element under certain conditions. Learn more about conditional ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ul > li.ot-cat-item > div.ot-chkbox > input#ot-bnr-grp-id-C0001 ul > li.ot-cat-item > div.ot-chkbox > input#ot-bnr-grp-id-C0001

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

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Strictly Necessary Cookies div.ot-cat-lst > ul > li.ot-cat-item > h4#ot-bnr-hdr-id-C0001

These are opportunities to improve keyboard navigation in your application.

○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.
●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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Image elements do not have `[alt]` attributes that are redundant text.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with 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
○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
○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.
81

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.
js.monitor.azure.com/scripts/b/ai.2.gbl.min.js line 4, col 20343
SharedStorage
www.norwegian.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.
www.norwegian.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
Fledge
www.norwegian.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
●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 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 DOM-based XSS with Trusted Types
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Mitigate clickjacking with XFO or CSP
○Detected JavaScript libraries
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.norwegian.com/uk/booking/booking-information/legal/privacy-policy/More 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