Skip to content
Audit Complete

Results for https://swiss.com

Visit site
Netherlands Netherlands · Amsterdam Completed: Apr 15, 2026 23:04 UTC
Download JSON Download Markdown Report

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
D67

Site Health

Score: 67 / 100

Based on 8 categories, 0 sections

Room to improve — your 20.0s load time is above Google's 2.5s 'Good' threshold.

Several missing protections leave your users and data exposed.

Several issues make your site difficult for assistive technology users.

Solid SEO basics — a few optimizations could boost rankings.

Good server performance with room for optimization.

Mostly compliant — a few items need attention.

Missing metadata means poor previews on social media and search.

Heavier than average — reducing page weight saves energy and bandwidth.

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

Apple sites average 73
-6 below average
Better than 1% of Apple sites See full Apple benchmark →
Google Search Console sites average 73
-6 below average
Better than 2% of Google Search Console sites See full Google Search Console benchmark →

Top Priorities (5)

1

Content-Security-Policy header is missing

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

Security › Security Headers
2

HSTS header is missing

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

Security › Security Headers
3

No Content-Security-Policy header found

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

Security › Content Security Policy
4

Page weighs 13.3 MB (11.0 MB transferred)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Budget
5

1 image-in-link without alt text

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Alt Text Quality
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

3

High impact, low effort — start here.

Strategic

2

High impact, requires investment.

Easy Improvements

0

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

0

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fswiss.com)](https://beavercheck.com/results/67a44cea-af80-4c0f-9866-0926e21f3356)
<a href="https://beavercheck.com/results/67a44cea-af80-4c0f-9866-0926e21f3356"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fswiss.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fswiss.com

This badge auto-updates with your latest scan result.

What fixing these means

Your site has several issues that may be affecting user experience and business outcomes. Your LCP of 20.0s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.

3 security gaps detected — browsers may warn visitors about your site.
Your LCP is 20.0s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.
1 accessibility issue excludes users who rely on assistive technology.
C
Could reach Estimate based on resolving critical issues

Return on Investment

CHF 650 investment → CHF 2.45/month returns + CHF 250,000 risk avoided

Payback period: > 2 years First-year ROI: -95%

Investment

CHF 650

5h · 5 findings

Monthly returns

CHF 2.45 /mo

~CHF 29 / year

  • Bandwidth savings CHF 2.45

Regulatory risk avoided

CHF 250,000

if kept compliant

  • nDSG/FADP CHF 250,000

CHF 195 — 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

CHF650

5.0 developer hours at CHF130/hr

Based on Switzerland rates (CHF130/hr)

Quick wins
CHF195 3 fixes in ~90 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions
CHF /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

CHF 20,836 / month at risk

~CHF 250,029 / year if left unfixed

Compliance Risk

CHF 250,000

nDSG/FADP
  • Privacy Policy not detected
    nDSG/FADP: CHF 1,000 – CHF 250,000

Bandwidth Waste

CHF 2.45 /mo

34611.8 MB/mo × 0.071 CHF/GB

  • Optimize transfer: save ~3.5 MB per page load
    Saves CHF 2.45/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

Unique monthly visitors from your analytics

Purchases, signups, or key actions

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 5 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...

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

12
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
92
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
73
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
100
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

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.

10.58 s

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

20.05 s

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

6.87 s

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

0.259

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

10.58 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.

26.96 s

Detailed Report

Audit breakdown by category with detailed findings.

12

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.

RequestCache TTLTransfer Size
/digitalhangar/design-system/releases/v1.26.2/standalone/...300.0 s307.4 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/e9044abc.chunk.js21600.0 s344.9 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/c8171bb1.chunk.js21600.0 s264.2 KiB
tags.tiqcdn.com/utag/lufthansa/lx-main/prod/utag.js300.0 s121.0 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/95fab3c7.chunk.js21600.0 s167.4 KiB
/digitalhangar/design-system/releases/v1.26.2/standalone/...300.0 s79.7 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/ce4d771e.chunk.js21600.0 s117.6 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/cf106378.chunk.js21600.0 s84.5 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/2f085645.chunk.js21600.0 s84.2 KiB
/digitalhangar/design-system/releases/v1.26.2/standalone/...300.0 s55.0 KiB
/digitalhangar/design-system/releases/v1.26.2/standalone/...300.0 s53.8 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/32e58ef6.chunk.js21600.0 s74.7 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/806c3834.chunk.js21600.0 s73.7 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/043f45bb.chunk.js21600.0 s66.2 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/fb2d2b94.chunk.js21600.0 s52.3 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/2a615625.chunk.js21600.0 s44.7 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/83d05b10.chunk.js21600.0 s37.3 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/css/index.5aNb6p1H.css21600.0 s36.7 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/707de846.chunk.js21600.0 s33.5 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/0eb5d549.chunk.js21600.0 s31.6 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/989e4325.chunk.js21600.0 s19.4 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/57cf59a3.chunk.js21600.0 s14.6 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/155a58db.chunk.js21600.0 s14.5 KiB
www.swiss.com/cdn-cgi/challenge-platform/h/g/scripts/jsd/b0a7532ac8ec/main.js?14400.0 s13.2 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/3d77f7d5.chunk.js21600.0 s14.0 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/1d25a90e.chunk.js21600.0 s13.6 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/5f0e358f.chunk.js21600.0 s13.4 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/4222fc3f.chunk.js21600.0 s12.9 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/b7469618.chunk.js21600.0 s11.6 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/f6b5a18b.chunk.js21600.0 s10.2 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/84c00550.chunk.js21600.0 s9.8 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/7c0c2ff7.chunk.js21600.0 s8.9 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/125a84da.chunk.js21600.0 s7.9 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/68172297.chunk.js21600.0 s7.9 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/5f8296e9.chunk.js21600.0 s7.4 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/0980613c.chunk.js21600.0 s6.9 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/56c199cf.chunk.js21600.0 s5.5 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/f82f9313.chunk.js21600.0 s5.3 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/1340f53e.chunk.js21600.0 s4.6 KiB
/digitalhangar/design-system/releases/v1.26.2/standalone/...300.0 s2.8 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/87bdaa02.chunk.js21600.0 s4.2 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/1d8fa131.chunk.js21600.0 s4.2 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/39f4b737.chunk.js21600.0 s4.2 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/68db732a.chunk.js21600.0 s4.1 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/a5b5c629.chunk.js21600.0 s3.6 KiB
rum.hlx.page/.rum/@adobe/helix-rum-js@%5E2/dist/rum-standalone.js3600.0 s2.9 KiB
tags.tiqcdn.com/utag/tiqapp/utag.currency.js?utv=ut4.46.20260415220309300.0 s2.2 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/291f5a73.chunk.js21600.0 s2.7 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/18bd621f.chunk.js21600.0 s2.5 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/eedbe3a4.chunk.js21600.0 s1.8 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/da6c70b1.chunk.js21600.0 s890 B
/utag/tiqapp/utag.v.js?a=lufthansa/lx-main/202604061108&c...300.0 s431 B
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/711f07d6.chunk.js21600.0 s623 B
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/3edbda2c.chunk.js21600.0 s593 B
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/a98b6959.chunk.js21600.0 s363 B

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]
items: [map[node:map[type:text value:Total] score:0.259356] map[node:map[boundingRect:map[bottom:1919 height:806 left:22 right:390 top:1113 width:368] lhId:page-17-DIV nodeLabel:Explore the world Discover worldwide offers for your next journey with SWISS Br… path:1,HTML,1,BODY,4,DIV,5,DIV,0,DIV,0,DIV,5,DIV selector:div.contentpage > div.content-wrapper > div.container-content > div.twocolumn snippet:<div class="twocolumn column event"> type:node] score:0.258375] map[node:map[boundingRect:map[bottom:498 height:20 left:53 right:357 top:478 width:304] lhId:page-20-DIV nodeLabel:Amsterdam - Schiphol path:1,HTML,1,BODY,4,DIV,5,DIV,0,DIV,0,DIV,1,DIV,1,DIV,0,DIV,2,DIV,0,DIV,0,SECTION,1,DIV,0,DIV,0,DIV,0,DIV,0,FORM,1,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV,0,INPUT,a,#document-fragment,1,DIV selector:div snippet:<div> type:node] score:0.000478] map[node:map[boundingRect:map[bottom:108 height:27 left:306 right:390 top:81 width:84] lhId:page-16-DIV nodeLabel:Login & Registration Navigation path:1,HTML,1,BODY,4,DIV,3,HEADER,1,DIV,1,DIV,1,DIV,0,DIV selector:div.common-header > div.common-header-wrapper > div.common-header-nav-wrap > div.common-header-meta-links snippet:<div class="common-header-meta-links align-items-center justify-content-end d-flex"> type:node] score:0.000318 subItems:map[items:[map[cause:Unsized image element]] type:subitems]] map[node:map[boundingRect:map[bottom:803 height:1 left:22 right:390 top:802 width:368] lhId:page-19-DIV nodeLabel:div.divider path:1,HTML,1,BODY,4,DIV,5,DIV,0,DIV,0,DIV,2,DIV,0,DIV,0,MAUI-DIVIDER,a,#document-fragment,1,DIV selector:div.divider snippet:<div role="presentation" class=" divider maui lx "> type:node] score:0.000185]]

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:0.244 source:map[type:text value:[unattributed]]] map[reflowTime:13.283 source:map[column:14 line:67323 type:source-location url:https://www.swiss.com/digitalhangar/design-system/releases/v1.26.2/standalone/packages/maui-design-system.js urlProvider:network]] map[reflowTime:16.346 source:map[column:16 line:67708 type:source-location url:https://www.swiss.com/digitalhangar/design-system/releases/v1.26.2/standalone/packages/maui-design-system.js urlProvider:network]] map[reflowTime:5.483 source:map[column:23 line:67410 type:source-location url:https://www.swiss.com/digitalhangar/design-system/releases/v1.26.2/standalone/packages/maui-design-system.js urlProvider:network]]]

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
427256349 div.teaser > a.teaser > div.image-wrapper > img
/content/dam/lx/images/frontify_variations/7/c-373574264-...228.8 KiB217.9 KiB
div.moving-image > div.w-100 > figure > img.w-100 div.moving-image > div.w-100 > figure > img.w-100
/content/dam/lx/images/header-images--homepage/mobile--he...274.9 KiB209.1 KiB
166015743 div.moving-image > div.w-100 > figure > img.w-100
/content/dam/lx/images/frontify_variations/4/c-1125997604...147.4 KiB137.8 KiB
div.fareteaser-recommendation-image > div.image-wrapper > maui-image > img div.fareteaser-recommendation-image > div.image-wrapper > maui-image > img
/content/dam/lx/images/offers/fareteaserdynamic/Destinati...147.9 KiB130.6 KiB
At the hotel div.teaser > a.teaser > div.image-wrapper > img
/content/dam/lx/images/frontify_variations/9/c-993297045-...123.0 KiB115.1 KiB
At the hotel div.moving-image > div.w-100 > figure > img.w-100
/content/dam/lx/images/frontify_variations/10/c-183986234...104.3 KiB97.6 KiB
At the hotel div.teaser > a.teaser > div.image-wrapper > img
/content/dam/lx/images/frontify_variations/6/c-2046679427...97.1 KiB90.9 KiB
div.teaser > a.teaser > div.image-wrapper > img div.teaser > a.teaser > div.image-wrapper > img
/content/dam/lx/images/local_images/profile/LX048_Travel_...91.5 KiB85.6 KiB
SWISS Business div.moving-image > div.w-100 > figure > img.w-100
/content/dam/lx/images/frontify_variations/3/c-1411859553...89.6 KiB83.8 KiB
div.fareteaser-recommendation-image > div.image-wrapper > maui-image > img div.fareteaser-recommendation-image > div.image-wrapper > maui-image > img
/content/dam/lx/images/offers/destination/fra-square.jpg....51.1 KiB33.8 KiB
div.fareteaser-recommendation-image > div.image-wrapper > maui-image > img div.fareteaser-recommendation-image > div.image-wrapper > maui-image > img
/content/dam/lx/images/offers/destination/tia-square.jpg....39.4 KiB22.1 KiB
div.fareteaser-recommendation-image > div.image-wrapper > maui-image > img div.fareteaser-recommendation-image > div.image-wrapper > maui-image > img
/content/dam/lx/images/offers/destination/sha-square.jpg....39.1 KiB21.8 KiB
div.fareteaser-recommendation-image > div.image-wrapper > maui-image > img div.fareteaser-recommendation-image > div.image-wrapper > maui-image > img
/content/dam/lx/images/offers/destination/ath-square.jpg....37.2 KiB19.9 KiB
div.fareteaser-recommendation-image > div.image-wrapper > maui-image > img div.fareteaser-recommendation-image > div.image-wrapper > maui-image > img
/content/dam/lx/images/offers/destination/muc-square.jpg....36.5 KiB19.2 KiB
div.fareteaser-recommendation-image > div.image-wrapper > maui-image > img div.fareteaser-recommendation-image > div.image-wrapper > maui-image > img
/content/dam/lx/images/offers/destination/bkk-square.jpg....30.8 KiB13.5 KiB
div.fareteaser-recommendation-image > div.image-wrapper > maui-image > img div.fareteaser-recommendation-image > div.image-wrapper > maui-image > img
/content/dam/lx/images/offers/destination/zrh-square.jpg....25.3 KiB8.0 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]
items: [map[duration:229.854 label:Time to first byte subpart:timeToFirstByte] map[duration:2804.926 label:Resource load delay subpart:resourceLoadDelay] map[duration:33.785 label:Resource load duration subpart:resourceLoadDuration] map[duration:77.523 label:Element render delay subpart:elementRenderDelay]]
lhId: page-1-IMG
nodeLabel: div.moving-image > div.w-100 > figure > img.w-100
path: 1,HTML,1,BODY,4,DIV,5,DIV,0,DIV,0,DIV,1,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,FIGURE,0,IMG
selector: div.moving-image > div.w-100 > figure > img.w-100
snippet: <img src="https://www.swiss.com/content/dam/lx/images/header-images--homepage/mobile…" srcset="/content/dam/lx/images/header-images--homepage/mobile--header-images/Heade…" alt="" class="w-100 h-100 object-cover">

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-1-IMG
nodeLabel: div.moving-image > div.w-100 > figure > img.w-100
path: 1,HTML,1,BODY,4,DIV,5,DIV,0,DIV,0,DIV,1,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,FIGURE,0,IMG
selector: div.moving-image > div.w-100 > figure > img.w-100
snippet: <img src="https://www.swiss.com/content/dam/lx/images/header-images--homepage/mobile…" srcset="/content/dam/lx/images/header-images--homepage/mobile--header-images/Heade…" alt="" class="w-100 h-100 object-cover">

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
value: No additional origins are good candidates for preconnecting

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.6 s

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

ElementLayout shift score
Explore the world Discover worldwide offers for your next journey with SWISS Br… div.contentpage > div.content-wrapper > div.container-content > div.twocolumn
0.258
Amsterdam - Schiphol div
0.000
Login & Registration Navigation div.common-header > div.common-header-wrapper > div.common-header-nav-wrap > div.common-header-meta-links
0.000
div.divider div.divider
0.000

Diagnostics

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 450 ms 96.7 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: 900 ms 154.1 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

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 Evaluation13.2 s
Other5.7 s
Style & Layout1.5 s
Parse HTML & CSS453 ms
Rendering388 ms
Garbage Collection303 ms
Script Parsing & Compilation253 ms

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
SWISS Business div.moving-image > div.w-100 > figure > img.w-100
/content/dam/lx/images/frontify_variations/3/c-1411859553...
At the hotel div.moving-image > div.w-100 > figure > img.w-100
/content/dam/lx/images/frontify_variations/10/c-183986234...
427256349 div.teaser > a.teaser > div.image-wrapper > img
/content/dam/lx/images/frontify_variations/7/c-373574264-...
At the hotel div.teaser > a.teaser > div.image-wrapper > img
/content/dam/lx/images/frontify_variations/9/c-993297045-...
At the hotel div.teaser > a.teaser > div.image-wrapper > img
/content/dam/lx/images/frontify_variations/6/c-2046679427...
div.teaser > a.teaser > div.image-wrapper > img div.teaser > a.teaser > div.image-wrapper > img
/content/dam/lx/images/local_images/profile/LX048_Travel_...
Homepage div.py-7 > div.grid-col-3 > maui-navigation-link > img.swiss-footer-logo
www.swiss.com/etc/designs/lx/clientlib-all/vite/img/star-alliance.svg

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

Optimize DOM size
Modern HTTP
Optimize viewport for mobile
Minify CSS
Avoid long main-thread tasks 20 long tasks found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 20 ms
Server Backend Latencies 290 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 40 ms
INP breakdown
User Timing marks and measures
Avoid non-composited animations
92

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

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#cm-consentDesc > div.checkBoxOption > label#ck_4_label > span#checkmark_ck_4 div#cm-consentDesc > div.checkBoxOption > label#ck_4_label > span#checkmark_ck_4

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Privacy Settings We use cookies and similar technologies that are necessary to… body.maui-theme-lx > div#__tealiumGDPRcpPrefs > div#cm-dial-v211

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
Route network div.teaser > a.teaser > div.card-content > h4.heading-copytext-large

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
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
`[role]` values are valid
`[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.
`button`, `link`, and `menuitem` elements have accessible names
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
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
Background and foreground colors have a sufficient contrast ratio
Document has a `<title>` element
`<frame>` or `<iframe>` elements have a title
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
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
ARIA IDs are unique
Elements with visible text labels have matching accessible names.
`[accesskey]` values are unique
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements 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
No form fields have multiple labels
`<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
Links are distinguishable without relying on color.
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.
73

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
SharedStorage
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.
Fledge

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 401 ()
Framing 'https://shop.swiss.com/' violates the following Content Security Policy directive: "frame-ancestors 'self'". The request has been blocked.

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Issue type
Content security policy

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
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
100

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.

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

36
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
89
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
73
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
100
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

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.

1.42 s

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

4.14 s

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

1.52 s

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

0.078

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

3.21 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.

5.21 s

Detailed Report

Audit breakdown by category with detailed findings.

36

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.

RequestCache TTLTransfer Size
/digitalhangar/design-system/releases/v1.26.2/standalone/...300.0 s307.9 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/e9044abc.chunk.js21600.0 s344.9 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/c8171bb1.chunk.js21600.0 s264.1 KiB
tags.tiqcdn.com/utag/lufthansa/lx-main/prod/utag.js300.0 s121.0 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/95fab3c7.chunk.js21600.0 s166.6 KiB
/digitalhangar/design-system/releases/v1.26.2/standalone/...300.0 s79.8 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/ce4d771e.chunk.js21600.0 s117.6 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/cf106378.chunk.js21600.0 s84.4 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/2f085645.chunk.js21600.0 s83.5 KiB
/digitalhangar/design-system/releases/v1.26.2/standalone/...300.0 s54.3 KiB
/digitalhangar/design-system/releases/v1.26.2/standalone/...300.0 s53.8 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/32e58ef6.chunk.js21600.0 s74.7 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/806c3834.chunk.js21600.0 s73.7 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/043f45bb.chunk.js21600.0 s67.0 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/fb2d2b94.chunk.js21600.0 s52.2 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/2a615625.chunk.js21600.0 s44.6 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/83d05b10.chunk.js21600.0 s37.4 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/css/index.5aNb6p1H.css21600.0 s36.7 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/707de846.chunk.js21600.0 s33.5 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/0eb5d549.chunk.js21600.0 s31.5 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/989e4325.chunk.js21600.0 s19.4 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/155a58db.chunk.js21600.0 s14.5 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/1d25a90e.chunk.js21600.0 s14.5 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/3d77f7d5.chunk.js21600.0 s14.0 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/57cf59a3.chunk.js21600.0 s13.7 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/5f0e358f.chunk.js21600.0 s13.3 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/4222fc3f.chunk.js21600.0 s12.9 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/b7469618.chunk.js21600.0 s12.5 KiB
www.swiss.com/cdn-cgi/challenge-platform/h/g/scripts/jsd/b0a7532ac8ec/main.js?14400.0 s11.2 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/f6b5a18b.chunk.js21600.0 s10.1 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/7c0c2ff7.chunk.js21600.0 s9.7 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/84c00550.chunk.js21600.0 s9.6 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/125a84da.chunk.js21600.0 s7.9 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/68172297.chunk.js21600.0 s7.9 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/5f8296e9.chunk.js21600.0 s7.3 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/0980613c.chunk.js21600.0 s7.0 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/56c199cf.chunk.js21600.0 s5.5 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/1340f53e.chunk.js21600.0 s5.4 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/f82f9313.chunk.js21600.0 s5.3 KiB
/digitalhangar/design-system/releases/v1.26.2/standalone/...300.0 s2.9 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/39f4b737.chunk.js21600.0 s4.2 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/1d8fa131.chunk.js21600.0 s4.2 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/87bdaa02.chunk.js21600.0 s4.1 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/68db732a.chunk.js21600.0 s4.1 KiB
rum.hlx.page/.rum/@adobe/helix-rum-js@%5E2/dist/rum-standalone.js3600.0 s2.9 KiB
tags.tiqcdn.com/utag/tiqapp/utag.currency.js?utv=ut4.46.20260415220339300.0 s2.2 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/a5b5c629.chunk.js21600.0 s3.1 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/291f5a73.chunk.js21600.0 s3.0 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/18bd621f.chunk.js21600.0 s2.5 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/eedbe3a4.chunk.js21600.0 s1.8 KiB
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/da6c70b1.chunk.js21600.0 s878 B
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/3edbda2c.chunk.js21600.0 s685 B
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/711f07d6.chunk.js21600.0 s678 B
/utag/tiqapp/utag.v.js?a=lufthansa/lx-main/202604061108&c...300.0 s430 B
www.swiss.com/etc/designs/lx/clientlib-all/vite/js/a98b6959.chunk.js21600.0 s270 B

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:2.067 source:map[column:16 line:67722 type:source-location url:https://www.swiss.com/digitalhangar/design-system/releases/v1.26.2/standalone/packages/maui-design-system.js urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:54.247 source:map[type:text value:[unattributed]]] map[reflowTime:14.433 source:map[column:14 line:67323 type:source-location url:https://www.swiss.com/digitalhangar/design-system/releases/v1.26.2/standalone/packages/maui-design-system.js urlProvider:network]] map[reflowTime:9.88 source:map[column:16 line:67708 type:source-location url:https://www.swiss.com/digitalhangar/design-system/releases/v1.26.2/standalone/packages/maui-design-system.js urlProvider:network]] map[reflowTime:6.271 source:map[column:23 line:67410 type:source-location url:https://www.swiss.com/digitalhangar/design-system/releases/v1.26.2/standalone/packages/maui-design-system.js urlProvider:network]] map[reflowTime:3.113 source:map[column:171 line:0 type:source-location url: urlProvider:network]] map[reflowTime:5.386 source:map[column:3422 line:0 type:source-location url: urlProvider:network]] map[reflowTime:2.458 source:map[column:1438 line:0 type:source-location url:https://www.swiss.com/cdn-cgi/challenge-platform/scripts/jsd/main.js urlProvider:network]] map[reflowTime:1.68 source:map[column:3350 line:3 type:source-location url:https://www.swiss.com/etc/designs/lx/clientlib-all/vite/js/app.ce522133.js urlProvider:network]]]

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
427256349 div.teaser > a.teaser > div.image-wrapper > img
/content/dam/lx/images/frontify_variations/7/c-373574264-...228.8 KiB222.7 KiB
div.fareteaser-recommendation-image > div.image-wrapper > maui-image > img div.fareteaser-recommendation-image > div.image-wrapper > maui-image > img
/content/dam/lx/images/offers/fareteaserdynamic/Destinati...147.9 KiB130.3 KiB
166015743 div.moving-image > div.w-100 > figure > img.w-100
/content/dam/lx/images/frontify_variations/4/c-1125997604...147.4 KiB124.3 KiB
At the hotel div.teaser > a.teaser > div.image-wrapper > img
/content/dam/lx/images/frontify_variations/9/c-993297045-...123.0 KiB118.6 KiB
At the hotel div.teaser > a.teaser > div.image-wrapper > img
/content/dam/lx/images/frontify_variations/6/c-2046679427...97.1 KiB93.7 KiB
div.teaser > a.teaser > div.image-wrapper > img div.teaser > a.teaser > div.image-wrapper > img
/content/dam/lx/images/local_images/profile/LX048_Travel_...91.5 KiB88.2 KiB
At the hotel div.moving-image > div.w-100 > figure > img.w-100
/content/dam/lx/images/frontify_variations/10/c-183986234...104.3 KiB88.1 KiB
div.moving-image > div.w-100 > figure > img.w-100 div.moving-image > div.w-100 > figure > img.w-100
/content/dam/lx/images/header-images--homepage/desktop--h...186.9 KiB84.9 KiB
SWISS Business div.moving-image > div.w-100 > figure > img.w-100
/content/dam/lx/images/frontify_variations/3/c-1411859553...89.6 KiB75.7 KiB
div.fareteaser-recommendation-image > div.image-wrapper > maui-image > img div.fareteaser-recommendation-image > div.image-wrapper > maui-image > img
/content/dam/lx/images/offers/destination/fra-square.jpg....51.1 KiB33.5 KiB
div.fareteaser-recommendation-image > div.image-wrapper > maui-image > img div.fareteaser-recommendation-image > div.image-wrapper > maui-image > img
/content/dam/lx/images/offers/destination/tia-square.jpg....39.4 KiB21.7 KiB
div.fareteaser-recommendation-image > div.image-wrapper > maui-image > img div.fareteaser-recommendation-image > div.image-wrapper > maui-image > img
/content/dam/lx/images/offers/destination/sha-square.jpg....39.1 KiB21.4 KiB
div.fareteaser-recommendation-image > div.image-wrapper > maui-image > img div.fareteaser-recommendation-image > div.image-wrapper > maui-image > img
/content/dam/lx/images/offers/destination/ath-square.jpg....37.2 KiB19.5 KiB
div.fareteaser-recommendation-image > div.image-wrapper > maui-image > img div.fareteaser-recommendation-image > div.image-wrapper > maui-image > img
/content/dam/lx/images/offers/destination/muc-square.jpg....36.5 KiB18.8 KiB
div.fareteaser-recommendation-image > div.image-wrapper > maui-image > img div.fareteaser-recommendation-image > div.image-wrapper > maui-image > img
/content/dam/lx/images/offers/destination/bkk-square.jpg....30.8 KiB13.1 KiB
div.fareteaser-recommendation-image > div.image-wrapper > maui-image > img div.fareteaser-recommendation-image > div.image-wrapper > maui-image > img
/content/dam/lx/images/offers/destination/zrh-square.jpg....25.3 KiB7.6 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]
items: [map[duration:228.975 label:Time to first byte subpart:timeToFirstByte] map[duration:3032.912 label:Resource load delay subpart:resourceLoadDelay] map[duration:32.208 label:Resource load duration subpart:resourceLoadDuration] map[duration:154.735 label:Element render delay subpart:elementRenderDelay]]
lhId: page-7-IMG
nodeLabel: div.moving-image > div.w-100 > figure > img.w-100
path: 1,HTML,1,BODY,4,DIV,5,DIV,0,DIV,0,DIV,1,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,FIGURE,0,IMG
selector: div.moving-image > div.w-100 > figure > img.w-100
snippet: <img src="https://www.swiss.com/content/dam/lx/images/header-images--homepage/deskto…" srcset="/content/dam/lx/images/header-images--homepage/desktop--header-images/high…" alt="" class="w-100 h-100 object-cover">

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-7-IMG
nodeLabel: div.moving-image > div.w-100 > figure > img.w-100
path: 1,HTML,1,BODY,4,DIV,5,DIV,0,DIV,0,DIV,1,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,FIGURE,0,IMG
selector: div.moving-image > div.w-100 > figure > img.w-100
snippet: <img src="https://www.swiss.com/content/dam/lx/images/header-images--homepage/deskto…" srcset="/content/dam/lx/images/header-images--homepage/desktop--header-images/high…" alt="" class="w-100 h-100 object-cover">

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
value: No additional origins are good candidates for preconnecting

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

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: 476 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.

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 JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 80 ms 96.8 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: 120 ms 151.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

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 Evaluation3.3 s
Other1.7 s
Style & Layout375 ms
Rendering127 ms
Parse HTML & CSS116 ms
Garbage Collection100 ms
Script Parsing & Compilation67 ms

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
SWISS Business div.moving-image > div.w-100 > figure > img.w-100
/content/dam/lx/images/frontify_variations/3/c-1411859553...
At the hotel div.moving-image > div.w-100 > figure > img.w-100
/content/dam/lx/images/frontify_variations/10/c-183986234...
427256349 div.teaser > a.teaser > div.image-wrapper > img
/content/dam/lx/images/frontify_variations/7/c-373574264-...
At the hotel div.teaser > a.teaser > div.image-wrapper > img
/content/dam/lx/images/frontify_variations/9/c-993297045-...
At the hotel div.teaser > a.teaser > div.image-wrapper > img
/content/dam/lx/images/frontify_variations/6/c-2046679427...
div.teaser > a.teaser > div.image-wrapper > img div.teaser > a.teaser > div.image-wrapper > img
/content/dam/lx/images/local_images/profile/LX048_Travel_...
Homepage div.py-7 > div.grid-col-3 > maui-navigation-link > img.swiss-footer-logo
www.swiss.com/etc/designs/lx/clientlib-all/vite/img/star-alliance.svg

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

Layout shift culprits
Optimize DOM size
Modern HTTP
Optimize viewport for mobile
Minify CSS
Avoid long main-thread tasks 17 long tasks found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 20 ms
Server Backend Latencies 330 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 40 ms
Avoid large layout shifts 11 layout shifts found
INP breakdown
User Timing marks and measures
Avoid non-composited animations
89

Accessibility

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

ARIA

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#cm-consentDesc > div.checkBoxOption > label#ck_4_label > span#checkmark_ck_4 div#cm-consentDesc > div.checkBoxOption > label#ck_4_label > span#checkmark_ck_4

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Privacy Settings We use cookies and similar technologies that are necessary to… body.maui-theme-lx > div#__tealiumGDPRcpPrefs > div#cm-dial-v211

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
Route network div.teaser > a.teaser > div.card-content > h4.heading-copytext-large

These are opportunities to improve keyboard navigation in your application.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Book & Prepare My booking Discover SWISS div.common-header-nav-wrap > div#nav > nav.header-navigation > ul

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

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
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
`[role]` values are valid
`[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.
`button`, `link`, and `menuitem` elements have accessible names
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
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
Background and foreground colors have a sufficient contrast ratio
Document has a `<title>` element
`<frame>` or `<iframe>` elements have a title
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links have a discernible name
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
ARIA IDs are unique
Elements with visible text labels have matching accessible names.
`[accesskey]` values are unique
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements 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
No form fields have multiple labels
`<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
Links are distinguishable without relying on color.
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.
73

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
SharedStorage
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.
Fledge

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 401 ()
Framing 'https://shop.swiss.com/' violates the following Content Security Policy directive: "frame-ancestors 'self'". The request has been blocked.

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Issue type
Content security policy

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
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
100

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.

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