Mobile 375 × 812

Desktop 1440 × 900

Score: 67 / 100
Based on 8 categories, 0 sections
Room to improve — your 15.9s 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.
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.
Heavier than average — reducing page weight saves energy and bandwidth.
The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.
Weights reflect general web best practices. Individual needs may differ.
Content-Security-Policy header is missing
Security gaps expose your site and users to attacks, eroding trust.
No Content-Security-Policy header found
Security gaps expose your site and users to attacks, eroding trust.
Page weighs 13.2 MB (4.3 MB transferred)
Performance issues directly impact user engagement and conversion rates.
No <main> landmark found
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
Soft 404: server returns HTTP 200 for non-existent pages
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
High impact, low effort — start here.
High impact, requires investment.
Small gains, minimal effort.
Nothing in this quadrant — good news.
Low impact, high effort — do last.
Nothing in this quadrant — good news.
[](https://beavercheck.com/results/231041d7-c9d5-4383-8b6c-97270bcc87da)<a href="https://beavercheck.com/results/231041d7-c9d5-4383-8b6c-97270bcc87da"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fspirit.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fspirit.comThis badge auto-updates with your latest scan result.
Your site has several issues that may be affecting user experience and business outcomes. Your LCP of 15.9s 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.
$600 investment → $1.08/month returns + USD 157,500 risk avoided
$600
6h · 5 findings
$1.08 /mo
~$13 / year
USD 157,500
if kept compliant
$100 — 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.
6.0 developer hours at $100/hr
Based on United States rates ($100/hr)
Start here for the best return on investment
$13,126 / month at risk
~$157,513 / year if left unfixed
$157,500
+6 more
$1.08 /mo
13504.2 MB/mo × 0.080 USD/GB
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.
Unique monthly visitors from your analytics
Purchases, signups, or key actions
Optional — for revenue estimation
more engaged visitors from reduced bounce
Fix 5 critical issues to capture this value
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
Your data stays in your browser — nothing is sent to our servers
Thanks for your feedback!
We'll use a cached audit if available, or offer to scan.
Industry-standard audits powered by Google Lighthouse.
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.
7.08 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
15.87 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
11.68 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.417
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
14.29 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.
37.79 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
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
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
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.
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.
Performance issues directly impact user engagement and conversion rates.
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.
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.
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.
Performance issues directly impact user engagement and conversion rates.
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Duration |
|---|---|---|
| www.spirit.com/BPb84x5I-/NEx/weUNOA/3V9trpYtYS7YXh/aioUXzp6AQ/KjB-Axd9/QkcB | 177.5 KiB | 902 ms |
| js-cdn.dynatrace.com/jstag/16dcf18d41e/bf04820crc/73bede5a20cee83c_complete.js | 82.4 KiB | 2.1 s |
| cdn.cookielaw.org/scripttemplates/otSDKStub.js | 9.1 KiB | 982 ms |
| assets.adobedtm.com/3b17361c9745/2ba699cc92bf/launch-a205ddd56998.min.js | 59.7 KiB | 1.7 s |
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
World Elite div.d-flex > div.d-flex > div.self-center > img.credit-card-img | content.spirit.com/a/5102 | 10.4 KiB | 9.2 KiB |
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.
Performance issues directly impact user engagement and conversion rates.
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.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| spirit.com/ | 821 ms |
| www.spirit.com/ | 0.0 ms |
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
Performance issues directly impact user engagement and conversion rates.
| Element | Layout shift score |
|---|---|
FLIGHT
BUNDLE & SAVE
HOTEL
CAR
CRUISE
Round Trip
1 Adult
From
To
Depart & Ret… body.en-US > app-root > main | 0.331 |
FLIGHT
BUNDLE & SAVE
HOTEL
CAR
CRUISE
Round Trip
1 Adult
From
To
Depart & Ret… body.en-US > app-root > main | 0.070 |
| 0.031 | |
| 0.022 | |
| 0.021 | |
Spirit header.spirit-header > nav.navbar > div.mobile-nav-bar > a | 0.016 |
| 0.006 | |
| 0.006 | |
| 0.004 | |
| 0.004 | |
| 0.003 | |
| 0.003 | |
| 0.003 | |
| 0.002 | |
| 0.002 |
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| www.spirit.com/styles-SMC22YWN.css | 48.5 KiB | 45.3 KiB |
| 20.4 KiB | 18.3 KiB | |
| .home-widget.multi-city-wrapper[_ngcontent-ng-c4043064263]{min-height:11.2rem} … | 13.1 KiB | 11.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.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
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.
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
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Script Evaluation | 28.2 s |
| Other | 7.1 s |
| Style & Layout | 2.8 s |
| Garbage Collection | 970 ms |
| Script Parsing & Compilation | 786 ms |
| Rendering | 326 ms |
| Parse HTML & CSS | 166 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
Performance issues directly impact user engagement and conversion rates.
| Failure reason | Failure type |
|---|---|
| The page has an unload handler in the main frame. | Actionable |
| The page has an unload handler in a sub frame. | Actionable |
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| rs.fullstory.com/rec/integrations?OrgId=NC1WY&isInFrame=false&isNative=false | 15.1 KiB | 3.9 KiB |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Performance issues directly impact user engagement and conversion rates.
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Performance issues directly impact user engagement and conversion rates.
| URL | |
|---|---|
Big Front Seat passenger receiving a drink a.ng-star-inserted > div.card-header > div.d-flex > img.sp-image | content.spirit.com/a/4446 |
Beach scene a.ng-star-inserted > div.card-header > div.d-flex > img.sp-image | content.spirit.com/a/4444 |
Group of girls laughing a.ng-star-inserted > div.card-header > div.d-flex > img.sp-image | content.spirit.com/a/4767 |
logo nav.navbar > div.mobile-nav-bar > a > img.logo | content.spirit.com/a/1679 |
More information about the performance of your application. These numbers don't directly affect the Performance score.
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.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
CHECK FOR AN OFFER div.d-flex > div.d-flex > div.align-self-center > a.cc-button |
These are opportunities to improve the legibility of your content.
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
body.en-US > iframe#px-captcha-modal body.en-US > iframe#px-captcha-modal |
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
GET TO KNOW US div.accordion > div > a#open-accordion1 > h4.footer-title |
These are opportunities to improve keyboard navigation in your application.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
click for more info div.card-body > div.d-flex > div.right-icon > i.icon-chevron-right |
click for more info div.card-body > div.d-flex > div.right-icon > i.icon-chevron-right |
click for more info div.card-body > div.d-flex > div.right-icon > i.icon-chevron-right |
Facebook div#social-nav-container just > ul.social-icons > li.me-xl-4 > a |
Twitter div#social-nav-container just > ul.social-icons > li.me-xl-4 > a |
Instagram div#social-nav-container just > ul.social-icons > li.me-xl-4 > a |
YouTube div#social-nav-container just > ul.social-icons > li.me-xl-4 > a |
Tiktok div#social-nav-container just > ul.social-icons > li.me-xl-4 > a |
These items highlight common accessibility best practices.
Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Privacy Policy div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link |
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Performance issues directly impact user engagement and conversion rates.
| URL | Aspect Ratio (Displayed) | Aspect Ratio (Actual) | |
|---|---|---|---|
logo div.row > div.col-sm-2 > a.d-flex > img.logo | content.spirit.com/a/1679 | 97 x 58 (1.67) | 97 x 27 (3.59) |
Vacation icon li.nav-list-item > label.link > div.link-icon > img | content.spirit.com/a/1692 | 20 x 24 (0.83) | 32 x 32 (1.00) |
Hotel icon li.nav-list-item > label.link > div.link-icon > img | content.spirit.com/a/1688 | 20 x 24 (0.83) | 32 x 32 (1.00) |
Car icon li.nav-list-item > label.link > div.link-icon > img | content.spirit.com/a/1691 | 20 x 24 (0.83) | 32 x 32 (1.00) |
Cruise icon li.nav-list-item > label.link > div.link-icon > img | content.spirit.com/a/1690 | 20 x 24 (0.83) | 32 x 32 (1.00) |
Flight icon li.nav-list-item > label.link > div.link-icon > img | content.spirit.com/a/2829 | 20 x 24 (0.83) | 18 x 19 (0.95) |
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Performance issues directly impact user engagement and conversion rates.
| URL | Displayed size | Actual size | Expected size | |
|---|---|---|---|---|
chevron-right div.d-flex > div.d-flex > div.chevron-alignment > img.chevron-right | content.spirit.com/a/1805 | 32 x 32 | 32 x 32 | 48 x 48 |
A character encoding declaration is required. It can be done with a `<meta>` tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more about declaring the character encoding.
Performance issues directly impact user engagement and conversion rates.
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Performance issues directly impact user engagement and conversion rates.
| Deprecation / Warning | Source |
|---|---|
| AttributionReporting | |
| Unload event listeners are deprecated and will be removed. |
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
Performance issues directly impact user engagement and conversion rates.
| Source | Description |
|---|---|
Failed to load resource: the server responded with a status of 403 () | |
Framing 'https://00000000.fls.doubleclick.net/' violates the following report-only Content Security Policy directive: "default-src 'self'". The violation has been logged, but no further action has been taken. Note that 'frame-src' was not explicitly set, so 'default-src' is used as a fallback.
| |
Framing 'https://00000000.fls.doubleclick.net/' violates the following report-only Content Security Policy directive: "default-src 'self'". The violation has been logged, but no further action has been taken. Note that 'frame-src' was not explicitly set, so 'default-src' is used as a fallback.
| |
Framing 'https://ct.pinterest.com/' violates the following report-only Content Security Policy directive: "default-src 'self'". The violation has been logged, but no further action has been taken. Note that 'frame-src' was not explicitly set, so 'default-src' is used as a fallback.
| |
Framing 'https://ct.pinterest.com/' violates the following report-only Content Security Policy directive: "default-src 'self'". The violation has been logged, but no further action has been taken. Note that 'frame-src' was not explicitly set, so 'default-src' is used as a fallback.
| |
Framing 'https://insight.adsrvr.org/' violates the following report-only Content Security Policy directive: "default-src 'self'". The violation has been logged, but no further action has been taken. Note that 'frame-src' was not explicitly set, so 'default-src' is used as a fallback.
| |
Framing 'https://match.adsrvr.org/' violates the following report-only Content Security Policy directive: "default-src 'self'". The violation has been logged, but no further action has been taken. Note that 'frame-src' was not explicitly set, so 'default-src' is used as a fallback.
| |
Framing 'https://match.adsrvr.org/' violates the following report-only Content Security Policy directive: "default-src 'self'". The violation has been logged, but no further action has been taken. Note that 'frame-src' was not explicitly set, so 'default-src' is used as a fallback.
| |
Object | |
ReferenceError: bk_addPageCtx is not defined
at <anonymous>:1:1
at https://www.spirit.com/static/d1d077d10f110c40d0c9fe606f74062ea7ab0011ba04fc:23:279
at uf.Z (https://www.spirit.com/static/d1d077d10f110c40d0c9fe606f74062ea7ab0011ba04fc:228:273)
at Object.apply (https://www.spirit.com/static/d1d077d10f110c40d0c9fe606f74062ea7ab0011ba04fc:23:267)
at https://www.googletagmanager.com/gtm.js?id=GTM-TRK4LPZ>m_auth=cVHzS7BYqjxUbMatudai8Q>m_preview=env-2:1153:429
at qR (https://www.googletagmanager.com/gtm.js?id=GTM-TRK4LPZ>m_auth=cVHzS7BYqjxUbMatudai8Q>m_preview=env-2:1155:31)
at Md.pR (https://www.googletagmanager.com/gtm.js?id=GTM-TRK4LPZ>m_auth=cVHzS7BYqjxUbMatudai8Q>m_preview=env-2:1152:92)
at Md.<anonymous> (https://www.googletagmanager.com/gtm.js?id=GTM-TRK4LPZ>m_auth=cVHzS7BYqjxUbMatudai8Q>m_preview=env-2:529:405)
at k.apply (https://www.googletagmanager.com/gtm.js?id=GTM-TRK4LPZ>m_auth=cVHzS7BYqjxUbMatudai8Q>m_preview=env-2:453:466)
at fb (https://www.googletagmanager.com/gtm.js?id=GTM-TRK4LPZ>m_auth=cVHzS7BYqjxUbMatudai8Q>m_preview=env-2:416:719) |
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.
Performance issues directly impact user engagement and conversion rates.
| Issue type |
|---|
| Cookie |
| 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.
Performance issues directly impact user engagement and conversion rates.
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.
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
Performance issues directly impact user engagement and conversion rates.
| Link destination | Link Text |
|---|---|
| cookiepedia.co.uk/giving-consent-to-cookies | More information |
Format your HTML in a way that enables crawlers to better understand your app’s content.
Industry-standard audits powered by Google Lighthouse. — Desktop
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.
927 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.97 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
29 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.65 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.62 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
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
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
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.
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.
Performance issues directly impact user engagement and conversion rates.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| /PXkp4CLSb5/captcha.js?a=c&u=d3fed800-391f-11f1-ab10-0fba... | 600.0 s | 263.6 KiB |
| client.px-cloud.net/PXkp4CLSb5/main.min.js | 600.0 s | 92.1 KiB |
| content.spirit.com/a/1679 | 1278.0 s | 7.2 KiB |
| www.spirit.com/pxns/c.js | 1800.0 s | 1.9 KiB |
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size |
|---|---|
| www.spirit.com/pxns/c.js | 1.9 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.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| spirit.com/ | 212 ms |
| www.spirit.com/ | 915 ms |
| www.spirit.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.
Performance issues directly impact user engagement and conversion rates.
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
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
| URL | Transfer Size | Est Savings |
|---|---|---|
| /PXkp4CLSb5/captcha.js?a=c&u=d3fed800-391f-11f1-ab10-0fba... | 260.7 KiB | 46.5 KiB |
| www.spirit.com/BPb84x5I-/NEx/weUNOA/3V9trpYtYS7YXh/aioUXzp6AQ/KjB-Axd9/QkcB | 178.8 KiB | 37.2 KiB |
| /BPb84x5I-/NEx/weUNOA/JX9trpYt/M2waXzp6AQ/eTEEejtI/M1MNAg... | 152.7 KiB | 28.7 KiB |
| client.px-cloud.net/PXkp4CLSb5/main.min.js | 91.8 KiB | 27.1 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.
Performance issues directly impact user engagement and conversion rates.
| URL | Total CPU Time | Script Evaluation | Script Parse |
|---|---|---|---|
| client.px-cloud.net/PXkp4CLSb5/main.min.js | 773 ms | 445 ms | 5.8 ms |
| /PXkp4CLSb5/captcha.js?a=c&u=d3fed800-391f-11f1-ab10-0fba... | 413 ms | 370 ms | 13 ms |
| www.spirit.com/static/d1d077d10f110c40d0c9fe606f74062ea7ab0011ba04fc | 240 ms | 213 ms | 2.9 ms |
| /BPb84x5I-/NEx/weUNOA/JX9trpYt/M2waXzp6AQ/eTEEejtI/M1MNAg... | 172 ms | 157 ms | 13 ms |
| www.spirit.com/BPb84x5I-/NEx/weUNOA/3V9trpYtYS7YXh/aioUXzp6AQ/KjB-Axd9/QkcB | 138 ms | 125 ms | 11 ms |
| Unattributable | 109 ms | 38 ms | 0.0 ms |
| www.spirit.com/ | 89 ms | 30 ms | 0.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
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Script Evaluation | 1.5 s |
| Style & Layout | 338 ms |
| Other | 124 ms |
| Script Parsing & Compilation | 49 ms |
| Garbage Collection | 36 ms |
| Parse HTML & CSS | 11 ms |
| Rendering | 8.8 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
Performance issues directly impact user engagement and conversion rates.
| Failure reason | Failure type |
|---|---|
| The page has an unload handler in the main frame. | Actionable |
| Only pages with a status code of 2XX can be cached. | Not actionable |
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Performance issues directly impact user engagement and conversion rates.
| URL | |
|---|---|
Logo body > div#px-captcha-wrapper > div.px-captcha-container > img.px-captcha-logo | content.spirit.com/a/1679 |
More information about the performance of your application. These numbers don't directly affect the Performance score.
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.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Reference ID d3fed800-391f-11f1-ab10-0fba2e76b8b8 body > div#px-captcha-wrapper > div.px-captcha-container > div.px-captcha-refid |
These are opportunities to improve the legibility of your content.
If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html html |
These are opportunities to improve the interpretation of your content by users in different locales.
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html html |
These items highlight common accessibility best practices.
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.
Performance issues directly impact user engagement and conversion rates.
A character encoding declaration is required. It can be done with a `<meta>` tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more about declaring the character encoding.
Performance issues directly impact user engagement and conversion rates.
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Performance issues directly impact user engagement and conversion rates.
| Deprecation / Warning | Source |
|---|---|
| Unload event listeners are deprecated and will be removed. | /PXkp4CLSb5/captcha.js?a=c&u=d3fed800-391f-11f1-ab10-0fba... line 1, col 206600 |
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
Performance issues directly impact user engagement and conversion rates.
| Source | Description |
|---|---|
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Refused to execute script from 'https://www.spirit.com/undefined' because its MIME type ('text/html') is not executable, and strict MIME type checking is enabled. |
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.
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.
Performance issues directly impact user engagement and conversion rates.
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.
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Performance issues directly impact user engagement and conversion rates.
Format your HTML in a way that enables crawlers to better understand your app’s content.
Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more about HTTP status codes.
Performance issues directly impact user engagement and conversion rates.
To appear in search results, crawlers need access to your app.
Send Feedback