Skip to content
Audit Complete

Results for https://kayak.com

Visit site
Corporate / Enterprise · estimated Tracking: leads
United States United States · Santa Clara Completed: Apr 15, 2026 22:57 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)
C73

Site Health

Score: 73 / 100

Based on 8 categories, 0 sections

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

Several missing protections leave your users and data exposed.

Mostly accessible, but some users still face barriers.

Well-optimized for search — your content is discoverable.

Good server performance with room for optimization.

Mostly compliant — a few items need attention.

Rich content metadata — your pages look great everywhere.

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

CMS sites average 73
At average
Better than 37% of CMS sites
Apple sites average 73
At average
Better than 37% of Apple sites See full Apple 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 18.4 MB (6.3 MB transferred)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Budget
5

(program):2: 656ms CPU time

Performance issues directly impact user engagement and conversion rates.

Performance › JS Execution Cost
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%2Fkayak.com)](https://beavercheck.com/results/8014db20-cc1e-458f-ba22-529456154a41)
<a href="https://beavercheck.com/results/8014db20-cc1e-458f-ba22-529456154a41"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fkayak.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fkayak.com

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 25.3s exceeds Google's 2.5s 'Good' threshold and the 2 performance issues below directly contribute to it. 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 25.3s — fixing the 2 performance criticals could bring it under Google's 2.5s 'Good' threshold.

Return on Investment

$550 investment → $1.58/month returns + USD 157,500 risk avoided

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

Investment

$550

6h · 5 findings

Monthly returns

$1.58 /mo

~$19 / year

  • Bandwidth savings $1.58

Regulatory risk avoided

USD 157,500

if kept compliant

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

$150 — 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

$550

5.5 developer hours at $100/hr

Based on United States rates ($100/hr)

Quick wins
$150 3 fixes in ~90 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions
$ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

$13,127 / month at risk

~$157,519 / year if left unfixed

Compliance Risk

$157,500

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

+5 more

Bandwidth Waste

$1.58 /mo

19753.3 MB/mo × 0.080 USD/GB

  • Optimize transfer: save ~2.0 MB per page load
    Saves $1.58/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 4 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.

26
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
83
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
77
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.

11.52 s

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

25.31 s

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

4.40 s

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

0.000

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

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

35.30 s

Detailed Report

Audit breakdown by category with detailed findings.

26

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 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:46.663 source:map[column:924696 line:56 type:source-location url:https://content.r9cdn.net/frontier/assets/nNPJO96_9o.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:333.685 source:map[type:text value:[unattributed]]] map[reflowTime:1.116 source:map[column:774097 line:55 type:source-location url:https://content.r9cdn.net/frontier/assets/nNPJO96_9o.js urlProvider:network]] map[reflowTime:1.177 source:map[column:132 line:0 type:source-location url:https://content.r9cdn.net/frontier/assets/D6ZMVZf3Zd.js urlProvider:network]] map[reflowTime:23.986 source:map[column:18670 line:32 type:source-location url:https://content.r9cdn.net/frontier/assets/nNPJO96_9o.js urlProvider:network]] map[reflowTime:0.35 source:map[column:315567 line:58 type:source-location url:https://content.r9cdn.net/frontier/assets/nNPJO96_9o.js urlProvider:network]] map[reflowTime:46.663 source:map[column:925005 line:55 type:source-location url:https://content.r9cdn.net/frontier/assets/nNPJO96_9o.js urlProvider:network]]]

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:511.302 label:Time to first byte subpart:timeToFirstByte] map[duration:3421.409 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-DIV
nodeLabel: This site uses cookies and other tracking technologies for essential, functiona…
path: 1,HTML,1,BODY,13,DIV,1,DIV,1,DIV,0,DIV,0,DIV,2,DIV,0,DIV
selector: div.c-ulo-viewport > div.c-ulo-content > div.Qe5W > div.Do64-text-block-1
snippet: <div class="Do64-text-block-1">

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.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.
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
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
content.r9cdn.net/frontier/assets/DSHOTusBkw.css48.4 KiB304 ms
content.r9cdn.net/frontier/assets/7RrfH3V-LA.css19.6 KiB
content.r9cdn.net/frontier/assets/BmBrDXV6Yp.css1.1 KiB
content.r9cdn.net/frontier/assets/Cb1Xz24qo1.css939 B
content.r9cdn.net/frontier/assets/DmSx52iOrm.css1.3 KiB152 ms
content.r9cdn.net/frontier/assets/BrpUSp4CV5.css397 B
content.r9cdn.net/frontier/assets/D8LrqMZ-5A.css612 B
content.r9cdn.net/frontier/assets/C3WVumoHQt.css409 B
content.r9cdn.net/frontier/assets/C6aObLIDsf.css935 B
content.r9cdn.net/frontier/assets/CN9dH5qokQ.css1023 B
content.r9cdn.net/frontier/assets/DdooitUOI4.css536 B
content.r9cdn.net/frontier/assets/C6JCcGfJS4.css1.9 KiB
content.r9cdn.net/frontier/assets/uMSmTC25Mq.css630 B
content.r9cdn.net/frontier/assets/DsGFGJsxPI.css707 B
content.r9cdn.net/frontier/assets/C8Fh-zxCXt.css319 B
content.r9cdn.net/frontier/assets/D9LyFc7oBg.css696 B
content.r9cdn.net/frontier/assets/jmFeWyq6mj.css400 B
content.r9cdn.net/frontier/assets/CUaD-XPpy8.css357 B
content.r9cdn.net/frontier/assets/DuXg3g23wy.css586 B
content.r9cdn.net/frontier/assets/BK04Fk7hW-.css582 B
content.r9cdn.net/frontier/assets/C2g3grerNY.css413 B
content.r9cdn.net/frontier/assets/CXCCOARfeG.css385 B
content.r9cdn.net/frontier/assets/CWD6ux67sk.css1.3 KiB
content.r9cdn.net/frontier/assets/DAyQ3bgura.css386 B
content.r9cdn.net/frontier/assets/G3DBTKKOxf.css2.5 KiB
content.r9cdn.net/frontier/assets/y2Gk7eeVtH.css2.7 KiB152 ms
content.r9cdn.net/frontier/assets/CgrbDvyJvs.css480 B
content.r9cdn.net/frontier/assets/7OCFJSfnve.css1.3 KiB
content.r9cdn.net/frontier/assets/Dizxt3XUpa.css1.8 KiB
content.r9cdn.net/frontier/assets/CjIgltI2sX.css1.4 KiB
content.r9cdn.net/frontier/assets/D69tlAGlGs.css921 B
content.r9cdn.net/frontier/assets/BMtOkAWiMq.css461 B
content.r9cdn.net/frontier/assets/Dx8smn8a-i.css952 B
content.r9cdn.net/frontier/assets/DfTROKXHUH.css651 B
content.r9cdn.net/frontier/assets/vTTsoscZFF.css564 B
content.r9cdn.net/frontier/assets/BySq7ncAdn.css705 B
content.r9cdn.net/frontier/assets/BkpAH7cyjN.css1.1 KiB
content.r9cdn.net/frontier/assets/Dj5BNtaZ6v.css1.9 KiB
content.r9cdn.net/frontier/assets/C4z5eMDb50.css434 B
content.r9cdn.net/frontier/assets/DkWcedeDl-.css433 B
content.r9cdn.net/frontier/assets/CT5D0ALSmA.css867 B
content.r9cdn.net/frontier/assets/jqKuHyVAUP.css823 B
content.r9cdn.net/frontier/assets/DqoKsp7QrE.css279 B
content.r9cdn.net/frontier/assets/CuArLKpDyC.css422 B
content.r9cdn.net/frontier/assets/DrVRj8cgNk.css1.1 KiB
content.r9cdn.net/frontier/assets/FuWoj0B03x.css438 B
content.r9cdn.net/frontier/assets/CN9YnRYNQ7.css315 B
content.r9cdn.net/frontier/assets/DLO2pqpLVk.css782 B
content.r9cdn.net/frontier/assets/CmcSKsElwD.css827 B
content.r9cdn.net/frontier/assets/CT8HnFqo_x.css1.2 KiB
content.r9cdn.net/frontier/assets/CMClTv_-47.css602 B
content.r9cdn.net/frontier/assets/CDb4vgIzIk.css585 B
content.r9cdn.net/frontier/assets/Cw7bz0u3V2.css874 B
content.r9cdn.net/frontier/assets/DAJmCM_Dbf.css675 B
content.r9cdn.net/frontier/assets/qSI4DtpTXd.css1.1 KiB
content.r9cdn.net/frontier/assets/D4DU8yXsog.css718 B
content.r9cdn.net/frontier/assets/D9he9dtLwj.css560 B
content.r9cdn.net/frontier/assets/CIk86tRFvQ.css573 B
content.r9cdn.net/frontier/assets/C48lOcN_Qy.css783 B
content.r9cdn.net/frontier/assets/CSnVX0UD7O.css522 B
content.r9cdn.net/frontier/assets/DT6D2ktTMh.css1.8 KiB
content.r9cdn.net/frontier/assets/MSZTgszF4T.css300 B
content.r9cdn.net/frontier/assets/Cz4_xqKJ5Z.css849 B
content.r9cdn.net/frontier/assets/Bil2pyID-1.css506 B
content.r9cdn.net/frontier/assets/DHcnDz4Un9.css529 B
content.r9cdn.net/frontier/assets/BC-J_N9y0L.css538 B
content.r9cdn.net/frontier/assets/Cj84S4mq2a.css2.8 KiB
content.r9cdn.net/frontier/assets/DWHZfwVMMQ.css361 B
content.r9cdn.net/frontier/assets/CyT_MJWEzk.css411 B
content.r9cdn.net/frontier/assets/Bup3JOFJgq.css328 B
content.r9cdn.net/frontier/assets/DTA7O72QmX.css2.8 KiB
content.r9cdn.net/frontier/assets/Dy3s8LI9wL.css568 B
content.r9cdn.net/frontier/assets/Dy97FWM6kN.css24.6 KiB998 ms
content.r9cdn.net/frontier/assets/C6zD-rdnAw.css506 B152 ms
content.r9cdn.net/frontier/assets/BFkKrMeiG9.css2.9 KiB
content.r9cdn.net/frontier/assets/Cr1phVD3_k.css2.6 KiB
content.r9cdn.net/frontier/assets/DAbJAmBprB.css5.5 KiB
content.r9cdn.net/frontier/assets/DlQ9y3glJZ.css5.3 KiB

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.

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
div.CxMh > div.c4hc > div.c4hc-image > img.DU4n div.CxMh > div.c4hc > div.c4hc-image > img.DU4n
/rimg/provider-logos/airlines/v/AS.png?crop=false&width=1...12.5 KiB12.0 KiB
div.CxMh > div.c4hc > div.c4hc-image > img.DU4n div.CxMh > div.c4hc > div.c4hc-image > img.DU4n
/res/images/people/avatar-1.png?v=cfaf5a64667edf6169023e3...12.3 KiB11.3 KiB
div.CxMh > div.c4hc > div.c4hc-image > img.DU4n div.CxMh > div.c4hc > div.c4hc-image > img.DU4n
/res/images/people/avatar-2.png?v=d8c9229643d04552ba0f027...11.4 KiB10.5 KiB
div.CxMh > div.c4hc > div.c4hc-image > img.DU4n div.CxMh > div.c4hc > div.c4hc-image > img.DU4n
/rimg/provider-logos/airlines/v/UA.png?crop=false&width=1...10.5 KiB10.1 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

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: 300 ms 52.6 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.

URLTotal CPU TimeScript EvaluationScript Parse
content.r9cdn.net/frontier/assets/CcD8mPq4Km.js5.4 s4.1 s7.6 ms
Unattributable4.1 s1.2 s0.0 ms
www.kayak.com/4.1 s102 ms36 ms
content.r9cdn.net/frontier/assets/CH9QYAfBte.js1.7 s282 ms1.2 ms
(program):2656 ms612 ms0.0 ms
/pagead/managed/js/gpt/m202604100101/pubads_impl.js639 ms552 ms63 ms
/gtag/js?id=G-PWCRSK2Y5Y&l=unifiedDataLayer&cx=c&gtm=4e64e1603 ms479 ms50 ms
content.r9cdn.net/frontier/assets/nNPJO96_9o.js454 ms163 ms10 ms
/gtag/destination?id=AW-988306736&l=unifiedDataLayer&cx=c...340 ms294 ms43 ms
/gtag/destination?id=DC-5142311&l=unifiedDataLayer&cx=c&g...339 ms286 ms49 ms
fundingchoicesmessages.google.com/i/12907657?ers=3317 ms291 ms22 ms
www.googletagmanager.com/gtm.js?id=GTM-PSCCSHQ&l=unifiedDataLayer283 ms225 ms50 ms
/gtag/destination?id=AW-undefined&l=unifiedDataLayer&cx=c...272 ms213 ms55 ms
ads.pubmatic.com/AdServer/js/pwt/167312/18979/pwt.js267 ms223 ms41 ms
analytics.tiktok.com/i18n/pixel/static/main.MWE0ZWQ3ZWQwMA.js243 ms198 ms40 ms
www.googletagservices.com/tag/js/gpt.js199 ms183 ms16 ms
content.r9cdn.net/frontier/assets/BQ5AqrHTm4.js178 ms150 ms0.5 ms
w.usabilla.com/cae7978c119b.js?lv=1100 ms77 ms6.4 ms
content.r9cdn.net/frontier/assets/DhyWS2VAVr.css96 ms0.0 ms0.0 ms
72164059993b.cdn4.forter.com/sn/72164059993b/script.js91 ms40 ms46 ms
bat.bing.com/p/insights/s/0.8.5977 ms65 ms4.8 ms
ep2.adtrafficquality.google/sodar/sodar2.js73 ms67 ms2.6 ms
analytics.tiktok.com/i18n/pixel/static/identify_5cff1caf.js61 ms41 ms20 ms
content.r9cdn.net/frontier/assets/DSHOTusBkw.css60 ms0.0 ms0.0 ms
bat.bing.com/bat.js56 ms51 ms4.9 ms
/_/mss/boq-content-ads-contributor/_/js/k=boq-content-ads...56 ms4.3 ms0.0 ms
/f/AGSKWxX1QbJrVf8cBHYBU9esK3js0udYquDiRrKLE-Xd_PsZPITOVj...53 ms36 ms1.4 ms
content.r9cdn.net/frontier/assets/DjXBEESAVV.js51 ms41 ms0.2 ms
accounts.google.com/gsi/client51 ms27 ms24 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation10.2 s
Other6.2 s
Style & Layout3.1 s
Rendering1.5 s
Parse HTML & CSS797 ms
Script Parsing & Compilation651 ms
Garbage Collection223 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
Pages with cache-control:no-store header cannot enter back/forward cache.Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.Not actionable

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
div.CxMh > div.c4hc > div.c4hc-image > img.DU4n div.CxMh > div.c4hc > div.c4hc-image > img.DU4n
/rimg/provider-logos/airlines/v/B6.png?crop=false&width=1...
div.CxMh > div.c4hc > div.c4hc-image > img.DU4n div.CxMh > div.c4hc > div.c4hc-image > img.DU4n
/rimg/provider-logos/airlines/v/AS.png?crop=false&width=1...
div.CxMh > div.c4hc > div.c4hc-image > img.DU4n div.CxMh > div.c4hc > div.c4hc-image > img.DU4n
/rimg/provider-logos/airlines/v/DL.png?crop=false&width=1...
div.CxMh > div.c4hc > div.c4hc-image > img.DU4n div.CxMh > div.c4hc > div.c4hc-image > img.DU4n
/rimg/provider-logos/airlines/v/UA.png?crop=false&width=1...
div.CxMh > div.c4hc > div.c4hc-image > img.DU4n div.CxMh > div.c4hc > div.c4hc-image > img.DU4n
/rimg/provider-logos/airlines/v/AA.png?crop=false&width=1...

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

Layout shift culprits
Optimize DOM size
Font display
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 17 user timings
Avoid long main-thread tasks 20 long tasks found
Avoid non-composited animations 24 animated elements found
Network Requests
Network Round Trip Times 70 ms
Server Backend Latencies 160 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 480 ms
INP breakdown
LCP request discovery
Avoid large layout shifts
83

Accessibility

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

ARIA

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.c-ulo > div.c-ulo-viewport > div.c-ulo-content > span div.c-ulo > div.c-ulo-viewport > div.c-ulo-content > span

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
Get more on the app. Faster search, more features, fewer ads. Get the app body.bd-default > div > div.c1yxs > div.c-ulo
Welcome to KAYAK This site uses cookies and other tracking technologies for ess… body.bd-default > div > div.c1yxs > div.c-ulo

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.c0H07-privacy > div.O4Ux > span > button.JCQa div.c0H07-privacy > div.O4Ux > span > button.JCQa

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body.bd-default > input body.bd-default > input

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.

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
Las Vegas div.P_Ok-wrapper > div.P_Ok-header > div.P_Ok-container > h3.P_Ok-title
How do I find travel deals on KAYAK? li.c9xAl > details.HABP > summary.HABP-button > h4.c9xAl-question

These are opportunities to improve keyboard navigation in your application.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Chea main.WKSW > div#main-search-form > div.c1LP5 > div.MjM6
English div.w6G7-pickers > div.ONcV > div.ONcV-country-picker > button.RxNS
$ USD footer.w6G7 > div.w6G7-pickers > div.ONcV > button.RxNS
Get the app div.eGu4 > div.eGu4-full-content > span.AFFP > div.eGu4-install-button
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]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Image elements have `[alt]` attributes
`[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
ARIA toggle fields have accessible names
Background and foreground colors have a sufficient contrast ratio
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links are distinguishable without relying on color.
Links have a discernible name
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
Skip links are focusable.
Document has a main landmark.
Deprecated ARIA roles were not used
Identical links have the same purpose.
`[accesskey]` values are unique
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 `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
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.
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
AttributionReporting

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
Not signed in with the identity provider.
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
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
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

38
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.
77
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.

2.26 s

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

3.79 s

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

513 ms

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

0.114

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

4.00 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.87 s

Detailed Report

Audit breakdown by category with detailed findings.

38

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.

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.114056] map[node:map[boundingRect:map[bottom:1991 height:550 left:0 right:1350 top:1441 width:1350] lhId:page-1-DIV nodeLabel:For travel pros KAYAK.ai BETA Get travel questions answered Best Time to Travel… path:1,HTML,1,BODY,1,DIV,0,DIV,1,DIV,2,DIV,0,MAIN,2,DIV,1,DIV,2,DIV selector:main.WKSW > div.Seuf > div.q9wv > div snippet:<div> type:node] score:0.060482] map[node:map[boundingRect:map[bottom:1991 height:550 left:0 right:1350 top:1441 width:1350] lhId:page-1-DIV nodeLabel:For travel pros KAYAK.ai BETA Get travel questions answered Best Time to Travel… path:1,HTML,1,BODY,1,DIV,0,DIV,1,DIV,2,DIV,0,MAIN,2,DIV,1,DIV,2,DIV selector:main.WKSW > div.Seuf > div.q9wv > div snippet:<div> type:node] score:0.05331] map[score:0.000264]]

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:35.278 source:map[column:1953 line:25 type:source-location url:https://content.r9cdn.net/frontier/assets/CcD8mPq4Km.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:425.803 source:map[type:text value:[unattributed]]] map[reflowTime:1.253 source:map[column:924074 line:55 type:source-location url:https://content.r9cdn.net/frontier/assets/nNPJO96_9o.js urlProvider:network]] map[reflowTime:1.365 source:map[column:19043 line:1 type:source-location url:https://content.r9cdn.net/frontier/assets/BQ5AqrHTm4.js urlProvider:network]] map[reflowTime:1.809 source:map[column:774097 line:55 type:source-location url:https://content.r9cdn.net/frontier/assets/nNPJO96_9o.js urlProvider:network]] map[reflowTime:0.729 source:map[column:651 line:0 type:source-location url:https://content.r9cdn.net/frontier/assets/Dji7UQ8w2p.js urlProvider:network]] map[reflowTime:31.487 source:map[column:315567 line:58 type:source-location url:https://content.r9cdn.net/frontier/assets/nNPJO96_9o.js urlProvider:network]]]

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:395.808 label:Time to first byte subpart:timeToFirstByte] map[duration:2035.805 label:Resource load delay subpart:resourceLoadDelay] map[duration:507.88 label:Resource load duration subpart:resourceLoadDuration] map[duration:325.92 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-IMG
nodeLabel: div.E9x1-container > div.E98K > div.OnKJ > img.Ez1T
path: 1,HTML,1,BODY,1,DIV,0,DIV,1,DIV,2,DIV,0,MAIN,0,DIV,0,SECTION,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,1,IMG
selector: div.E9x1-container > div.E98K > div.OnKJ > img.Ez1T
snippet: <img class="Ez1T" loading="lazy" width="220" height="220" src="https://content.r9cdn.net/frontier/assets/B78-YSGPh-.png" srcset="https://content.r9cdn.net/frontier/assets/YHji6z5a7N.png 1.5x, https://con…" alt="" aria-hidden="true">

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: div.E9x1-container > div.E98K > div.OnKJ > img.Ez1T
path: 1,HTML,1,BODY,1,DIV,0,DIV,1,DIV,2,DIV,0,MAIN,0,DIV,0,SECTION,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,1,IMG
selector: div.E9x1-container > div.E98K > div.OnKJ > img.Ez1T
snippet: <img class="Ez1T" loading="lazy" width="220" height="220" src="https://content.r9cdn.net/frontier/assets/B78-YSGPh-.png" srcset="https://content.r9cdn.net/frontier/assets/YHji6z5a7N.png 1.5x, https://con…" alt="" aria-hidden="true">

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.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.
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
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.

URLTransfer SizeDuration
content.r9cdn.net/frontier/assets/7RrfH3V-LA.css19.6 KiB
content.r9cdn.net/frontier/assets/DAJmCM_Dbf.css727 B
content.r9cdn.net/frontier/assets/Dizxt3XUpa.css1.7 KiB
content.r9cdn.net/frontier/assets/CyT_MJWEzk.css405 B
content.r9cdn.net/frontier/assets/CgrbDvyJvs.css490 B
content.r9cdn.net/frontier/assets/D4DU8yXsog.css763 B
content.r9cdn.net/frontier/assets/C2g3grerNY.css302 B
content.r9cdn.net/frontier/assets/C4z5eMDb50.css473 B
content.r9cdn.net/frontier/assets/BkpAH7cyjN.css1.0 KiB
content.r9cdn.net/frontier/assets/D69tlAGlGs.css1007 B
content.r9cdn.net/frontier/assets/BMtOkAWiMq.css528 B
content.r9cdn.net/frontier/assets/Dx8smn8a-i.css960 B
content.r9cdn.net/frontier/assets/DfTROKXHUH.css563 B
content.r9cdn.net/frontier/assets/vTTsoscZFF.css511 B
content.r9cdn.net/frontier/assets/DkWcedeDl-.css477 B
content.r9cdn.net/frontier/assets/Dj5BNtaZ6v.css1.8 KiB
content.r9cdn.net/frontier/assets/C8Fh-zxCXt.css337 B
content.r9cdn.net/frontier/assets/D9LyFc7oBg.css723 B
content.r9cdn.net/frontier/assets/jmFeWyq6mj.css413 B
content.r9cdn.net/frontier/assets/BK04Fk7hW-.css560 B
content.r9cdn.net/frontier/assets/Cb1Xz24qo1.css953 B
content.r9cdn.net/frontier/assets/DuXg3g23wy.css503 B
content.r9cdn.net/frontier/assets/CUaD-XPpy8.css460 B
content.r9cdn.net/frontier/assets/DmSx52iOrm.css1.3 KiB
content.r9cdn.net/frontier/assets/BrpUSp4CV5.css320 B
content.r9cdn.net/frontier/assets/BmBrDXV6Yp.css1.1 KiB
content.r9cdn.net/frontier/assets/DSHOTusBkw.css48.5 KiB
content.r9cdn.net/frontier/assets/C3WVumoHQt.css377 B
content.r9cdn.net/frontier/assets/CN9dH5qokQ.css981 B
content.r9cdn.net/frontier/assets/C6aObLIDsf.css992 B
content.r9cdn.net/frontier/assets/C6JCcGfJS4.css1.9 KiB
content.r9cdn.net/frontier/assets/DdooitUOI4.css459 B
content.r9cdn.net/frontier/assets/D8LrqMZ-5A.css547 B
content.r9cdn.net/frontier/assets/DrVRj8cgNk.css1.2 KiB
content.r9cdn.net/frontier/assets/FuWoj0B03x.css411 B
content.r9cdn.net/frontier/assets/CN9YnRYNQ7.css315 B
content.r9cdn.net/frontier/assets/DLO2pqpLVk.css797 B
content.r9cdn.net/frontier/assets/CmcSKsElwD.css798 B
content.r9cdn.net/frontier/assets/Cw7bz0u3V2.css885 B
content.r9cdn.net/frontier/assets/CDb4vgIzIk.css697 B
content.r9cdn.net/frontier/assets/CT8HnFqo_x.css1.1 KiB
content.r9cdn.net/frontier/assets/CMClTv_-47.css608 B
content.r9cdn.net/frontier/assets/qSI4DtpTXd.css1.1 KiB
content.r9cdn.net/frontier/assets/D9he9dtLwj.css490 B
content.r9cdn.net/frontier/assets/CIk86tRFvQ.css549 B
content.r9cdn.net/frontier/assets/C48lOcN_Qy.css874 B
content.r9cdn.net/frontier/assets/CSnVX0UD7O.css462 B
content.r9cdn.net/frontier/assets/DsGFGJsxPI.css706 B
content.r9cdn.net/frontier/assets/uMSmTC25Mq.css753 B
content.r9cdn.net/frontier/assets/CXCCOARfeG.css307 B
content.r9cdn.net/frontier/assets/DT6D2ktTMh.css1.7 KiB
content.r9cdn.net/frontier/assets/CWD6ux67sk.css1.4 KiB
content.r9cdn.net/frontier/assets/7OCFJSfnve.css1.3 KiB
content.r9cdn.net/frontier/assets/MSZTgszF4T.css265 B
content.r9cdn.net/frontier/assets/Bup3JOFJgq.css438 B
content.r9cdn.net/frontier/assets/DAyQ3bgura.css417 B
content.r9cdn.net/frontier/assets/BySq7ncAdn.css698 B
content.r9cdn.net/frontier/assets/G3DBTKKOxf.css2.5 KiB
content.r9cdn.net/frontier/assets/y2Gk7eeVtH.css2.7 KiB
content.r9cdn.net/frontier/assets/CjIgltI2sX.css1.4 KiB
content.r9cdn.net/frontier/assets/jqKuHyVAUP.css853 B
content.r9cdn.net/frontier/assets/DqoKsp7QrE.css389 B
content.r9cdn.net/frontier/assets/CuArLKpDyC.css403 B
content.r9cdn.net/frontier/assets/Cz4_xqKJ5Z.css836 B
content.r9cdn.net/frontier/assets/Bil2pyID-1.css509 B
content.r9cdn.net/frontier/assets/DHcnDz4Un9.css506 B
content.r9cdn.net/frontier/assets/BC-J_N9y0L.css620 B
content.r9cdn.net/frontier/assets/DWHZfwVMMQ.css398 B
content.r9cdn.net/frontier/assets/Cj84S4mq2a.css2.8 KiB
content.r9cdn.net/frontier/assets/DTA7O72QmX.css2.8 KiB
content.r9cdn.net/frontier/assets/Dy97FWM6kN.css24.4 KiB338 ms
content.r9cdn.net/frontier/assets/Dy3s8LI9wL.css425 B
content.r9cdn.net/frontier/assets/CT5D0ALSmA.css964 B
content.r9cdn.net/frontier/assets/BFkKrMeiG9.css2.8 KiB
content.r9cdn.net/frontier/assets/DAbJAmBprB.css5.5 KiB
content.r9cdn.net/frontier/assets/Cr1phVD3_k.css2.9 KiB
content.r9cdn.net/frontier/assets/DlQ9y3glJZ.css5.3 KiB
content.r9cdn.net/frontier/assets/C6zD-rdnAw.css494 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.

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
div.E9x1-container > div.E98K > div.OnKJ > img.Ez1T div.E9x1-container > div.E98K > div.OnKJ > img.Ez1T
content.r9cdn.net/frontier/assets/tDvMG0XMPE.png92.3 KiB84.4 KiB
div.E9x1-container > div.E98K > div.OnKJ > img.Ez1T div.E9x1-container > div.E98K > div.OnKJ > img.Ez1T
content.r9cdn.net/frontier/assets/BAWXupsgkG.png87.3 KiB79.4 KiB
div.E9x1-container > div.E98K > div.OnKJ > img.Ez1T div.E9x1-container > div.E98K > div.OnKJ > img.Ez1T
content.r9cdn.net/frontier/assets/BnHJJLI5dK.png79.7 KiB71.8 KiB
div.E9x1-container > div.E98K > div.OnKJ > img.Ez1T div.E9x1-container > div.E98K > div.OnKJ > img.Ez1T
content.r9cdn.net/frontier/assets/B78-YSGPh-.png76.8 KiB69.0 KiB
div.E9x1-container > div.E98K > div.OnKJ > img.Ez1T div.E9x1-container > div.E98K > div.OnKJ > img.Ez1T
content.r9cdn.net/frontier/assets/C4mMXIMv2W.png75.6 KiB67.8 KiB
div.E9x1-container > div.E98K > div.OnKJ > img.Ez1T div.E9x1-container > div.E98K > div.OnKJ > img.Ez1T
content.r9cdn.net/frontier/assets/CUXpOgsxPJ.png69.1 KiB61.2 KiB
div.E9x1-container > div.E98K > div.OnKJ > img.Ez1T div.E9x1-container > div.E98K > div.OnKJ > img.Ez1T
content.r9cdn.net/frontier/assets/CAvTY9b4SO.png64.0 KiB56.1 KiB
div.E9x1-container > div.E98K > div.OnKJ > img.Ez1T div.E9x1-container > div.E98K > div.OnKJ > img.Ez1T
content.r9cdn.net/frontier/assets/D9SjeOszg-.png55.9 KiB48.0 KiB
div.CxMh > div.c4hc > div.c4hc-image > img.DU4n div.CxMh > div.c4hc > div.c4hc-image > img.DU4n
/res/images/people/avatar-3.png?v=00227cc2d66e60b9a38e87a...13.2 KiB12.9 KiB
div.CxMh > div.c4hc > div.c4hc-image > img.DU4n div.CxMh > div.c4hc > div.c4hc-image > img.DU4n
/rimg/provider-logos/airlines/v/AS.png?crop=false&width=1...12.5 KiB12.4 KiB
div.CxMh > div.c4hc > div.c4hc-image > img.DU4n div.CxMh > div.c4hc > div.c4hc-image > img.DU4n
/res/images/people/avatar-1.png?v=cfaf5a64667edf6169023e3...12.3 KiB11.9 KiB
div.CxMh > div.c4hc > div.c4hc-image > img.DU4n div.CxMh > div.c4hc > div.c4hc-image > img.DU4n
/res/images/people/avatar-2.png?v=d8c9229643d04552ba0f027...11.4 KiB11.1 KiB
div.CxMh > div.c4hc > div.c4hc-image > img.DU4n div.CxMh > div.c4hc > div.c4hc-image > img.DU4n
/rimg/provider-logos/airlines/v/UA.png?crop=false&width=1...10.5 KiB10.4 KiB
div.CxMh > div.c4hc > div.c4hc-image > img.DU4n div.CxMh > div.c4hc > div.c4hc-image > img.DU4n
/rimg/provider-logos/airlines/v/AA.png?crop=false&width=1...5.3 KiB5.2 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: 207 ms
URLTime Spent
kayak.com/207 ms
www.kayak.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

Why this matters

Performance issues directly impact user engagement and conversion rates.

ElementLayout shift score
For travel pros KAYAK.ai BETA Get travel questions answered Best Time to Travel… main.WKSW > div.Seuf > div.q9wv > div
0.060
For travel pros KAYAK.ai BETA Get travel questions answered Best Time to Travel… main.WKSW > div.Seuf > div.q9wv > div
0.053
0.000

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.

Diagnostics

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 Evaluation2.9 s
Other1.6 s
Style & Layout888 ms
Rendering306 ms
Script Parsing & Compilation199 ms
Parse HTML & CSS177 ms
Garbage Collection124 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
Pages with cache-control:no-store header cannot enter back/forward cache.Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.Not actionable

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

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
div.CxMh > div.c4hc > div.c4hc-image > img.DU4n div.CxMh > div.c4hc > div.c4hc-image > img.DU4n
/rimg/provider-logos/airlines/v/B6.png?crop=false&width=1...
div.CxMh > div.c4hc > div.c4hc-image > img.DU4n div.CxMh > div.c4hc > div.c4hc-image > img.DU4n
/rimg/provider-logos/airlines/v/AS.png?crop=false&width=1...
div.CxMh > div.c4hc > div.c4hc-image > img.DU4n div.CxMh > div.c4hc > div.c4hc-image > img.DU4n
/rimg/provider-logos/airlines/v/DL.png?crop=false&width=1...
div.CxMh > div.c4hc > div.c4hc-image > img.DU4n div.CxMh > div.c4hc > div.c4hc-image > img.DU4n
/rimg/provider-logos/airlines/v/UA.png?crop=false&width=1...
div.CxMh > div.c4hc > div.c4hc-image > img.DU4n div.CxMh > div.c4hc > div.c4hc-image > img.DU4n
/rimg/provider-logos/airlines/v/AA.png?crop=false&width=1...

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

Optimize DOM size
Font display
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 17 user timings
Avoid long main-thread tasks 18 long tasks found
Avoid non-composited animations 26 animated elements found
Network Requests
Network Round Trip Times 70 ms
Server Backend Latencies 160 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 370 ms
INP breakdown
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

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.c-ulo > div.c-ulo-viewport > div.c-ulo-content > span div.c-ulo > div.c-ulo-viewport > div.c-ulo-content > span

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
Welcome to KAYAK This site uses cookies and other tracking technologies for ess… body.bd-default > div > div.c1yxs > div.c-ulo

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
Las Vegas div.P_Ok-wrapper > div.P_Ok-header > div.P_Ok-container > h3.P_Ok-title
How do I find travel deals on KAYAK? li.c9xAl > details.HABP > summary.HABP-button > h4.c9xAl-question

These are opportunities to improve keyboard navigation in your application.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Flights to L main.WKSW > div#main-search-form > div.c1LP5 > div.MjM6
English div.jy7a-pickers > div.ONcV > div.ONcV-country-picker > button.RxNS
$ USD div.jy7a > div.jy7a-pickers > div.ONcV > button.RxNS
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]` 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.
`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
ARIA input fields have accessible names
Elements use only permitted ARIA attributes
Background and foreground colors have a sufficient contrast ratio
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links are distinguishable without relying on color.
Links have a discernible name
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
Skip links are focusable.
Document has a main landmark.
Deprecated ARIA roles were not used
Identical links have the same purpose.
`[accesskey]` values are unique
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
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
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.
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
AttributionReporting

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
[GSI_LOGGER]: FedCM get() rejects with NetworkError: Error retrieving a token.
Not signed in with the identity provider.
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
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
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