Skip to content
https://flysas.com

Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

27

Performance

Insights

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Performance issues directly impact user engagement and conversion rates.

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

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:351.514 label:Time to first byte subpart:timeToFirstByte] map[duration:20.498 label:Resource load delay subpart:resourceLoadDelay] map[duration:169.793 label:Resource load duration subpart:resourceLoadDuration] map[duration:1990.814 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-IMG
nodeLabel: Europe. Elevated.
path: 1,HTML,1,BODY,4,DIV,0,DIV,3,DIV,1,MAIN,4,DIV,0,DIV,0,DIV,0,IMG
selector: div._1o9gtn29 > div._1204gqzh > div._125ytsv2 > img.od8ddx0
snippet: <img alt="Europe. Elevated." width="1600" height="720" decoding="async" data-nimg="1" class="od8ddx0 _125ytsv3" style="color:transparent" srcset="https://components.flysas.com/content/assets/ctfassets/oz9qk43ly6yk/10X5MO…" src="https://components.flysas.com/content/assets/ctfassets/oz9qk43ly6yk/10X5MO…">

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG
nodeLabel: Europe. Elevated.
path: 1,HTML,1,BODY,4,DIV,0,DIV,3,DIV,1,MAIN,4,DIV,0,DIV,0,DIV,0,IMG
selector: div._1o9gtn29 > div._1204gqzh > div._125ytsv2 > img.od8ddx0
snippet: <img alt="Europe. Elevated." width="1600" height="720" decoding="async" data-nimg="1" class="od8ddx0 _125ytsv3" style="color:transparent" srcset="https://components.flysas.com/content/assets/ctfassets/oz9qk43ly6yk/10X5MO…" src="https://components.flysas.com/content/assets/ctfassets/oz9qk43ly6yk/10X5MO…">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
value: no origins were preconnected
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTransfer SizeDuration
www.flysas.com/_next/static/css/b3390c8ef63e3334.css888 B
www.flysas.com/_next/static/css/ece99d5ffbeccbb1.css7.9 KiB150 ms
www.flysas.com/_next/static/css/d5505f63b5075061.css231 B
www.flysas.com/_next/static/css/17a0679e77eb3d44.css417 B
www.flysas.com/_next/static/css/0d7d846195e77d43.css647 B
www.flysas.com/_next/static/css/6f21a74f3995cb56.css415 B
www.flysas.com/_next/static/css/dffb509cb598e900.css193 B
www.flysas.com/_next/static/css/a952bdd2c29c129c.css337 B
www.flysas.com/_next/static/css/af6499bbad414025.css1.5 KiB
www.flysas.com/_next/static/css/155523968b8d07b4.css800 B
www.flysas.com/_next/static/css/559f24d61a468531.css1.2 KiB150 ms
www.flysas.com/_next/static/css/41aa4294df80b9c5.css223 B
www.flysas.com/_next/static/css/04d4c0854e291a21.css1.0 KiB
www.flysas.com/_next/static/css/d2bac2e6ebcfc245.css481 B
www.flysas.com/_next/static/css/bfe959eab655a479.css505 B
www.flysas.com/_next/static/css/7b76e130d85e6278.css1.2 KiB
www.flysas.com/_next/static/css/883e369252b080e2.css452 B
www.flysas.com/_next/static/css/9b97001cbc3934ad.css292 B
www.flysas.com/_next/static/css/5631d54cc9eebd10.css728 B150 ms
www.flysas.com/_next/static/css/72f46646ba2e07b7.css1.5 KiB
www.flysas.com/_next/static/css/77bb337127b5a725.css293 B
www.flysas.com/_next/static/css/a5726c06c0649870.css561 B
www.flysas.com/_next/static/css/cb6e9332e883d68c.css592 B
www.flysas.com/_next/static/css/5d40f18029eddaa5.css1.4 KiB150 ms
www.flysas.com/_next/static/css/7cc1580584876ee3.css3.5 KiB
www.flysas.com/_next/static/css/db720b873701748a.css1.1 KiB
www.flysas.com/_next/static/css/70f4c115c3f6176b.css1.1 KiB
www.flysas.com/_next/static/css/c2cbf91ecf0323ac.css567 B
www.flysas.com/_next/static/css/5ff9436be6d5ade1.css404 B
www.flysas.com/_next/static/css/a7a01fc94a2ff2d9.css680 B
www.flysas.com/_next/static/css/1d75097eb852659b.css770 B
www.flysas.com/_next/static/css/d86665e7f854757d.css2.0 KiB
www.flysas.com/_next/static/css/aad156d8bcfbf94e.css309 B150 ms
www.flysas.com/_next/static/css/aeb95d39888dd23d.css644 B
www.flysas.com/_next/static/css/8f41a197393194cd.css210 B
www.flysas.com/_next/static/css/ce137039358737d0.css1.6 KiB
www.flysas.com/_next/static/css/0311bbf6e3ae1485.css696 B
www.flysas.com/_next/static/css/e0b7e092ebc481e2.css349 B
www.flysas.com/_next/static/css/2f140deccdff0966.css662 B
www.flysas.com/_next/static/css/ca6ce8e58dae83fd.css280 B
www.flysas.com/_next/static/css/c03f0069f1d4cf50.css379 B
www.flysas.com/_next/static/css/9ca449a8ced2fcf6.css840 B
www.flysas.com/_next/static/css/16a45a3e1fc7c833.css455 B
www.flysas.com/_next/static/css/2f42a9b893be8130.css2.0 KiB
www.flysas.com/_next/static/css/c0385ba789aef1da.css905 B
www.flysas.com/_next/static/css/df4be6ee66ec11b2.css846 B
www.flysas.com/_next/static/css/dca11ce0df2427ae.css1.5 KiB
www.flysas.com/_next/static/css/86ae11326a200642.css490 B
www.flysas.com/_next/static/css/9cea99567c797ed8.css180 B
www.flysas.com/_next/static/css/42a98115102a99f3.css221 B
www.flysas.com/_next/static/css/84e8d2f3ab1d1d15.css2.6 KiB
www.flysas.com/_next/static/css/2ea3ed1fe52952d8.css1.5 KiB
www.flysas.com/_next/static/css/02d39a0b5ac2d126.css996 B
www.flysas.com/_next/static/css/a4196b8975f33691.css1.3 KiB
www.flysas.com/_next/static/css/3f602fc51e9077a1.css876 B
www.flysas.com/_next/static/css/1769e7f6dbbbf971.css167 B

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.

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
Europe. Elevated. div._1o9gtn29 > div._1204gqzh > div._125ytsv2 > img.od8ddx0
/content/assets/ctfassets/oz9qk43ly6yk/10X5MO3dFa2wF35I22...107.4 KiB99.5 KiB

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.6 s
URLTime Spent
flysas.com/763 ms
www.flysas.com/796 ms
www.flysas.com/en0.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.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation7.4 s
Other1.6 s
Script Parsing & Compilation981 ms
Style & Layout767 ms
Garbage Collection196 ms
Parse HTML & CSS170 ms
Rendering70 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 28.0 KiB

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
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Avoids enormous network payloads Total size was 2,443 KiB
●User Timing marks and measures 8 user timings
●Avoid long main-thread tasks 20 long tasks found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 10 ms
●Server Backend Latencies 170 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 70 ms
○INP breakdown
○Avoid non-composited animations
○Avoid large layout shifts
100

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.

○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 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.
●Select elements have associated label elements.
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links 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.
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with 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
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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.
○Elements with visible text labels have matching accessible names.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
77

Best Practices

General

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
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 ()
Failed to load resource: the server responded with a status of 401 ()

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

●Uses HTTPS
●Avoids third-party cookies
●Allows users to paste into input fields
●Avoids requesting the geolocation permission on page load
●Avoids requesting the notification permission on page load
●Displays images with correct aspect ratio
●Serves images with appropriate resolution
●Page has the HTML doctype
●Properly defines charset
●No issues in the `Issues` panel in Chrome Devtools
●Ensure CSP is effective against XSS attacks
●Ensure proper origin isolation with COOP
●Mitigate DOM-based XSS with Trusted Types
●Detected JavaScript libraries
○Redirects HTTP traffic to HTTPS
○Use a strong HSTS policy
○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