C — https://norwegian.com | BeaverCheck Audit

Site Health

Score: 78 / 100

Based on 8 categories, 0 sections

Decent speed, but optimizing further could improve engagement.

Good foundation, but a few gaps could be exploited.

Several issues make your site difficult for assistive technology users.

Solid SEO basics — a few optimizations could boost rankings.

Solid infrastructure — fast server responses across the board.

Mostly compliant — a few items need attention.

Missing metadata means poor previews on social media and search.

Lean and efficient — low environmental impact per visit.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

AngularJS sites average 73

At average

Better than 88% of AngularJS sites See full AngularJS benchmark →

Cloudflare Turnstile sites average 73

At average

Better than 87% of Cloudflare Turnstile sites See full Cloudflare Turnstile benchmark →

Top Priorities (5)

HSTS header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers

56 third-party resources (100% of weight)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Inventory

Cross-Origin-Embedder-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers

Cross-Origin-Opener-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers

DMARC policy is none — monitoring only

Security gaps expose your site and users to attacks, eroding trust.

Security › Email Security

View fix priority matrix

Fix Priority Matrix

5 findings

Impact

Quick Wins

High impact, low effort — start here.

Strategic

High impact, requires investment.

Easy Improvements

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fnorwegian.com)](https://beavercheck.com/results/dbeec07f-f59a-45e1-916c-bc144ca91e6f)

HTML

<a href="https://beavercheck.com/results/dbeec07f-f59a-45e1-916c-bc144ca91e6f"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fnorwegian.com" alt="BeaverCheck Score"></a>

Image URL

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

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 10.4s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. Addressing the critical issues below would have the most immediate impact on your user trust.

4 security gaps detected — browsers may warn visitors about your site.

Your LCP is 10.4s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.

Could reach Estimate based on resolving critical issues

Return on Investment

$400 investment → $2,326/month returns + USD 157,500 risk avoided

Payback period: < 1 month First-year ROI: +6877%

Investment

$400

4h · 5 findings

Monthly returns

$2,326 /mo

~$27,907 / year

Conversions recovered $2,325
Bandwidth savings $0.30

Regulatory risk avoided

USD 157,500

if kept compliant

ADA Title III USD 150,000
CCPA/CPRA USD 7,500

Payback period

0 12mo 24mo

$200 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

$400

4.0 developer hours at $100/hr

Based on United States rates ($100/hr)

Quick wins

$200 4 fixes in ~120 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions

Custom rate

$ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

$13,125 / month at risk

~$157,504 / year if left unfixed

Compliance Risk

$157,500

ADA Title IIICCPA/CPRA

No privacy policy link detected
CCPA/CPRA: USD 2,500 – USD 7,500
Trackers detected but no cookie policy found
CCPA/CPRA: USD 2,500 – USD 7,500
Trackers detected but no privacy policy found
CCPA/CPRA: USD 2,500 – USD 7,500

+3 more

Bandwidth Waste

$0.30 /mo

3800.9 MB/mo × 0.080 USD/GB

Optimize transfer: save ~380 KB per page load
Saves $0.30/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Monthly visitors

Unique monthly visitors from your analytics

Conversion rate (%)

Purchases, signups, or key actions

Avg. order value

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue

Current bounce (est.)

After fixes (est.)

Estimated bounce reduction

Fix 1 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

Best Practices

SEO

Core Web Vitals

Key metrics that affect user experience.

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

2.34 s

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

10.40 s

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

2.24 s

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

0.000

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

3.71 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

10.96 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

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

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

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more ▾

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

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.

Request	Cache TTL	Transfer Size
cdn.cookielaw.org/scripttemplates/202502.1.0/otBannerSdk.js	86400.0 s	114.9 KiB
js.monitor.azure.com/scripts/b/ai.2.gbl.min.js	1800.0 s	46.2 KiB
www.norwegian.com/style-bundle/cms-brand.css?v=bLHHIb7YsgNRVYXxfbSQhVOIMeI	86403.0 s	73.6 KiB
www.norwegian.com/Images/countries-flags/es.svg	86401.0 s	49.1 KiB
www.norwegian.com/Images/countries-flags/us.svg	86401.0 s	37.7 KiB
www.norwegian.com/Images/countries-flags/uk.svg	86401.0 s	26.5 KiB
/logos/1a04bf16-c960-4bea-8ca5-183b663691f3/019445ca-840b...	86400.0 s	21.3 KiB
/cdn-cgi/challenge-platform/h/g/scripts/jsd/b0a7532ac8ec/...	14400.0 s	11.8 KiB
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...	86400.0 s	10.7 KiB
cdn.cookielaw.org/scripttemplates/otSDKStub.js	86400.0 s	9.1 KiB
www.norwegian.com/Images/countries-flags/fi.svg	86401.0 s	6.0 KiB
www.norwegian.com/Images/countries-flags/se.svg	86401.0 s	5.7 KiB
www.norwegian.com/Images/countries-flags/no.svg	86401.0 s	5.4 KiB
www.norwegian.com/Images/countries-flags/pl.svg	86401.0 s	4.6 KiB
www.norwegian.com/Images/countries-flags/nl.svg	86401.0 s	4.5 KiB
www.norwegian.com/Images/countries-flags/it.svg	86401.0 s	4.5 KiB
www.norwegian.com/Images/countries-flags/de.svg	86401.0 s	4.5 KiB
www.norwegian.com/Images/countries-flags/dk.svg	86401.0 s	4.4 KiB
www.norwegian.com/Images/countries-flags/fr.svg	86401.0 s	4.2 KiB
www.norwegian.com/script-bundle/lazysizes.js?v=3HmW99h1vglLXWpaWVnJHw-kycI	86402.0 s	3.4 KiB
cdn.cookielaw.org/logos/static/powered_by_logo.svg	86400.0 s	2.6 KiB
www.norwegian.com/Images/countries-flags/en.svg	86401.0 s	2.3 KiB
www.norwegian.com/Util/Find/epi-util/find.js	86402.0 s	2.3 KiB
/script-bundle/plainPageController.js?v=BA6egZn3-V1L5_2N_...	86402.0 s	2.3 KiB
www.norwegian.com/Content/img/ident.svg	86401.0 s	2.1 KiB
www.norwegian.com/Content/img/ident-mobile.svg	86401.0 s	1.5 KiB
/script-bundle/accessibility-cookie.js?v=dXpbs49Ir3bAAlKN...	86402.0 s	320 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.

URL	Transfer Size	Duration
www.norwegian.com/style-bundle/cms-brand.css?v=bLHHIb7YsgNRVYXxfbSQhVOIMeI	73.6 KiB	752 ms
cdn.cookielaw.org/scripttemplates/otSDKStub.js	9.1 KiB	766 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.

URL	Est 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

URL	Time 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

URL	Transfer Size	Est Savings
www.norwegian.com/style-bundle/cms-brand.css?v=bLHHIb7YsgNRVYXxfbSQhVOIMeI	73.6 KiB	11.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

URL	Transfer Size	Est Savings
www.norwegian.com/style-bundle/cms-brand.css?v=bLHHIb7YsgNRVYXxfbSQhVOIMeI	73.4 KiB	72.2 KiB
	21.5 KiB	17.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

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more ▾

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Estimated savings: 1.5 s 240.1 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-XMQZZ1BMXF&cx=c&gtm=4e64e1&bs=ctrl	160.8 KiB	66.3 KiB
www.googletagmanager.com/gtag/js?id=DC-5877806&cx=c&gtm=4e64e1&bs=ctrl	130.5 KiB	59.2 KiB
cdn.cookielaw.org/scripttemplates/202502.1.0/otBannerSdk.js	114.8 KiB	59.0 KiB
www.googletagmanager.com/gtm.js?id=GTM-NVL4JDR	213.9 KiB	55.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.

URL	Total CPU Time	Script Evaluation	Script Parse
www.googletagmanager.com/gtm.js?id=GTM-NVL4JDR	1.4 s	1.2 s	103 ms
Unattributable	730 ms	207 ms	0.0 ms
cdn.cookielaw.org/scripttemplates/202502.1.0/otBannerSdk.js	499 ms	229 ms	110 ms
www.norwegian.com/script-bundle/lazysizes.js?v=3HmW99h1vglLXWpaWVnJHw-kycI	486 ms	73 ms	1.3 ms
www.norwegian.com/cdn-cgi/challenge-platform/scripts/jsd/main.js	373 ms	356 ms	3.3 ms
www.norwegian.com/	354 ms	63 ms	9.6 ms
www.googletagmanager.com/gtag/js?id=G-XMQZZ1BMXF&cx=c&gtm=4e64e1&bs=ctrl	345 ms	271 ms	62 ms
js.monitor.azure.com/scripts/b/ai.2.gbl.min.js	276 ms	216 ms	30 ms
www.googletagmanager.com/gtag/js?id=DC-5877806&cx=c&gtm=4e64e1&bs=ctrl	239 ms	188 ms	49 ms
cdn.cookielaw.org/scripttemplates/otSDKStub.js	57 ms	37 ms	4.6 ms
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...	56 ms	37 ms	4.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.

Category	Time Spent
Script Evaluation	2.9 s
Other	1.0 s
Script Parsing & Compilation	381 ms
Style & Layout	206 ms
Parse HTML & CSS	167 ms
Garbage Collection	110 ms
Rendering	51 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 reason	Failure 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

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.

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 / Warning	Source
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

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 destination	Link 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`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

Accessibility

Best Practices

SEO

Core Web Vitals

Key metrics that affect user experience. — Desktop

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

653 ms

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

2.22 s

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

255 ms

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

0.000

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

1.62 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

2.28 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more ▾

Source: Google web.dev / Lighthouse

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.

Request	Cache TTL	Transfer Size
cdn.cookielaw.org/scripttemplates/202502.1.0/otBannerSdk.js	86400.0 s	114.9 KiB
js.monitor.azure.com/scripts/b/ai.2.gbl.min.js	1800.0 s	46.2 KiB
www.norwegian.com/style-bundle/cms-brand.css?v=bLHHIb7YsgNRVYXxfbSQhVOIMeI	86403.0 s	73.5 KiB
www.norwegian.com/Images/countries-flags/es.svg	86401.0 s	48.8 KiB
www.norwegian.com/Images/countries-flags/us.svg	86401.0 s	37.7 KiB
www.norwegian.com/Images/countries-flags/uk.svg	86401.0 s	26.8 KiB
/logos/1a04bf16-c960-4bea-8ca5-183b663691f3/019445ca-840b...	86400.0 s	21.4 KiB
/cdn-cgi/challenge-platform/h/g/scripts/jsd/b0a7532ac8ec/...	14400.0 s	12.4 KiB
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...	86400.0 s	10.7 KiB
cdn.cookielaw.org/scripttemplates/otSDKStub.js	86400.0 s	9.1 KiB
www.norwegian.com/Images/countries-flags/fi.svg	86401.0 s	5.9 KiB
www.norwegian.com/Images/countries-flags/se.svg	86401.0 s	5.5 KiB
www.norwegian.com/Images/countries-flags/no.svg	86401.0 s	5.4 KiB
www.norwegian.com/Images/countries-flags/pl.svg	86401.0 s	4.6 KiB
www.norwegian.com/Images/countries-flags/nl.svg	86401.0 s	4.5 KiB
www.norwegian.com/Images/countries-flags/it.svg	86401.0 s	4.5 KiB
www.norwegian.com/Images/countries-flags/fr.svg	86401.0 s	4.5 KiB
www.norwegian.com/Images/countries-flags/de.svg	86401.0 s	4.5 KiB
www.norwegian.com/Images/countries-flags/dk.svg	86401.0 s	4.4 KiB
www.norwegian.com/script-bundle/lazysizes.js?v=3HmW99h1vglLXWpaWVnJHw-kycI	86402.0 s	3.3 KiB
cdn.cookielaw.org/logos/static/powered_by_logo.svg	86400.0 s	2.5 KiB
www.norwegian.com/Util/Find/epi-util/find.js	86402.0 s	2.4 KiB
www.norwegian.com/Images/countries-flags/en.svg	86401.0 s	2.3 KiB
www.norwegian.com/Content/img/ident.svg	86401.0 s	2.3 KiB
/script-bundle/plainPageController.js?v=vXtO0lMnV-65pIzpW...	86402.0 s	2.3 KiB
www.norwegian.com/Content/img/ident-mobile.svg	86401.0 s	898 B
/script-bundle/accessibility-cookie.js?v=dXpbs49Ir3bAAlKN...	86402.0 s	320 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.

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.

URL	Transfer Size	Duration
www.norwegian.com/style-bundle/cms-brand.css?v=bLHHIb7YsgNRVYXxfbSQhVOIMeI	73.5 KiB	122 ms
cdn.cookielaw.org/scripttemplates/otSDKStub.js	9.1 KiB	219 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.

URL	Est Savings
/Content/webfonts/NorwegianDisplayPro-Bold.woff2?v=2yPPwI...	20 ms
/Content/webfonts/NorwegianTextPro-Bold.woff2?v=2yPPwIqAJ...	20 ms
/Content/webfonts/NorwegianTextPro-Regular.woff2?v=2yPPwI...	15 ms

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.

Estimated savings: 206 ms

URL	Time Spent
norwegian.com/	206 ms
www.norwegian.com/	0.0 ms

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

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: 40 ms 11.5 KiB

URL	Transfer Size	Est Savings
www.norwegian.com/style-bundle/cms-brand.css?v=bLHHIb7YsgNRVYXxfbSQhVOIMeI	73.5 KiB	11.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: 160 ms 90.0 KiB

URL	Transfer Size	Est Savings
www.norwegian.com/style-bundle/cms-brand.css?v=bLHHIb7YsgNRVYXxfbSQhVOIMeI	73.4 KiB	72.0 KiB
	21.5 KiB	18.0 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

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more ▾

Source: Google web.dev / Lighthouse

Estimated savings: 240 ms 240.2 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-XMQZZ1BMXF&cx=c&gtm=4e64e1&bs=ctrl2	160.8 KiB	66.3 KiB
www.googletagmanager.com/gtag/js?id=DC-5877806&cx=c&gtm=4e64e1&bs=ctrl2	130.5 KiB	59.2 KiB
cdn.cookielaw.org/scripttemplates/202502.1.0/otBannerSdk.js	114.8 KiB	59.0 KiB
www.googletagmanager.com/gtm.js?id=GTM-NVL4JDR	213.9 KiB	55.7 KiB

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 reason	Failure 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.svg

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

●Time to Interactive 2.3 s

●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,238 KiB

●User Timing marks and measures 7 user timings

●JavaScript execution time 0.7 s

●Minimizes main-thread work 1.2 s

●Avoid long main-thread tasks 5 long tasks found

●Network Requests

●Network Round Trip Times 20 ms

●Server Backend Latencies 310 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 230 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

○Avoid non-composited animations

Accessibility

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

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.

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 / Warning	Source
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
Unload event listeners are deprecated and will be removed.	js.monitor.azure.com/scripts/b/ai.2.gbl.min.js line 4, col 20343

●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

SEO

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 destination	Link 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`

Results for https://norwegian.com

Site Health

How you compare

Top Priorities (5)

Fix Priority Matrix

Quick Wins

Strategic

Easy Improvements

Deprioritize

What fixing these means

Return on Investment

Investment

Monthly returns

Regulatory risk avoided

Payback period

Estimated Remediation Cost

Cost by category

Cost by effort level

What Inaction Is Costing You

Compliance Risk

Bandwidth Waste

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

ARIA

Navigation

Best Practices

General

SEO

Content Best Practices

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

ARIA

Navigation

Best Practices

General

SEO

Content Best Practices

Keyboard Shortcuts