Mobile 375 × 812

Desktop 1440 × 900

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.
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.
HSTS 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 18.4 MB (6.3 MB transferred)
Performance issues directly impact user engagement and conversion rates.
(program):2: 656ms CPU time
Performance issues directly impact user engagement and conversion rates.
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/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.comThis badge auto-updates with your latest scan result.
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.
$550 investment → $1.58/month returns + USD 157,500 risk avoided
$550
6h · 5 findings
$1.58 /mo
~$19 / year
USD 157,500
if kept compliant
$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.
5.5 developer hours at $100/hr
Based on United States rates ($100/hr)
Start here for the best return on investment
$13,127 / month at risk
~$157,519 / year if left unfixed
$157,500
+5 more
$1.58 /mo
19753.3 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 4 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.
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
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 |
|---|---|---|
| ads.pubmatic.com/AdServer/js/pwt/167312/18979/pwt.js | 157143.0 s | 136.4 KiB |
| bat.bing.com/p/insights/s/0.8.59 | 86400.0 s | 15.6 KiB |
| /rimg/provider-logos/airlines/v/AS.png?crop=false&width=1... | 435600.0 s | 12.8 KiB |
| /rimg/provider-logos/airlines/v/UA.png?crop=false&width=1... | 673200.0 s | 10.9 KiB |
| /rimg/provider-logos/airlines/v/AA.png?crop=false&width=1... | 514800.0 s | 5.7 KiB |
| /rp.gif?id=a2_gkgghllr96c8&event=PageVisit&integration=no... | 0.0 ms | 666 B |
| /rimg/provider-logos/airlines/v/DL.png?crop=false&width=1... | 496800.0 s | 4.5 KiB |
| /rimg/provider-logos/airlines/v/B6.png?crop=false&width=1... | 763200.0 s | 3.9 KiB |
| /?env=mweb&zdid=1110&eventType=pageview&gdpr=1&gdpr_conse... | 0.0 ms | 368 B |
| pagead2.googlesyndication.com/pagead/osd.js?fcd=true | 3600.0 s | 76 B |
| /tr/?id=1347583438592982&ev=PageView&ts=1776293781&fbp=fb... | 0.0 ms | 19 B |
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.
Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.
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.
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.
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 | |
|---|---|---|---|
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 KiB | 12.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 KiB | 11.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 KiB | 10.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 KiB | 10.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.
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 |
|---|---|
| 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.
Performance issues directly impact user engagement and conversion rates.
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 |
|---|---|---|
| content.r9cdn.net/frontier/assets/BmDQ7hE1B4.css | 23.9 KiB | 23.9 KiB |
| content.r9cdn.net/frontier/assets/7RrfH3V-LA.css | 19.3 KiB | 17.2 KiB |
| content.r9cdn.net/frontier/assets/DvNDqPpQ39.css | 11.6 KiB | 11.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.
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 | 10.2 s |
| Other | 6.2 s |
| Style & Layout | 3.1 s |
| Rendering | 1.5 s |
| Parse HTML & CSS | 797 ms |
| Script Parsing & Compilation | 651 ms |
| Garbage Collection | 223 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 |
|---|---|
| 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 |
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 | |
|---|---|
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.
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.
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.
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.
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.
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.
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.
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.
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 |
|---|
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.
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 |
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 | /gtag/destination?id=AW-988306736&l=unifiedDataLayer&cx=c... line 575, col 244 |
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 |
|---|---|
Not signed in with the identity provider. |
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.
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.
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
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.
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.
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.
Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.
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.
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 |
|---|---|---|
| ads.pubmatic.com/AdServer/js/pwt/167312/18979/pwt.js | 157108.0 s | 136.4 KiB |
| bat.bing.com/p/insights/s/0.8.59 | 86400.0 s | 15.6 KiB |
| /rimg/provider-logos/airlines/v/AS.png?crop=false&width=1... | 435600.0 s | 12.8 KiB |
| /rimg/provider-logos/airlines/v/UA.png?crop=false&width=1... | 673200.0 s | 10.9 KiB |
| /rimg/provider-logos/airlines/v/AA.png?crop=false&width=1... | 514800.0 s | 5.7 KiB |
| /rp.gif?id=a2_gkgghllr96c8&event=PageVisit&integration=no... | 0.0 ms | 666 B |
| /rimg/provider-logos/airlines/v/DL.png?crop=false&width=1... | 496800.0 s | 4.4 KiB |
| /rimg/provider-logos/airlines/v/B6.png?crop=false&width=1... | 763200.0 s | 3.9 KiB |
| /?env=web&zdid=1110&eventType=pageview&gdpr=1&gdpr_consen... | 0.0 ms | 368 B |
| /tr/?id=1347583438592982&ev=PageView&ts=1776293816&fbp=fb... | 0.0 ms | 19 B |
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.
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 | |
|---|---|---|---|
div.E9x1-container > div.E98K > div.OnKJ > img.Ez1T div.E9x1-container > div.E98K > div.OnKJ > img.Ez1T | content.r9cdn.net/frontier/assets/tDvMG0XMPE.png | 92.3 KiB | 84.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.png | 87.3 KiB | 79.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.png | 79.7 KiB | 71.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-.png | 76.8 KiB | 69.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.png | 75.6 KiB | 67.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.png | 69.1 KiB | 61.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.png | 64.0 KiB | 56.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-.png | 55.9 KiB | 48.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 KiB | 12.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 KiB | 12.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 KiB | 11.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 KiB | 11.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 KiB | 10.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 KiB | 5.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.
Performance issues directly impact user engagement and conversion rates.
| URL | Time 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
Performance issues directly impact user engagement and conversion rates.
| Element | Layout 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.
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.
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 | 2.9 s |
| Other | 1.6 s |
| Style & Layout | 888 ms |
| Rendering | 306 ms |
| Script Parsing & Compilation | 199 ms |
| Parse HTML & CSS | 177 ms |
| Garbage Collection | 124 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 |
|---|---|
| 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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| content.r9cdn.net/frontier/assets/BmDQ7hE1B4.css | 23.9 KiB | 23.9 KiB |
| content.r9cdn.net/frontier/assets/7RrfH3V-LA.css | 19.3 KiB | 16.7 KiB |
| content.r9cdn.net/frontier/assets/DvNDqPpQ39.css | 11.6 KiB | 11.6 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 | |
|---|---|
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.
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.
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.
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.
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.
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 |
|---|
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.
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 |
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 | /gtag/destination?id=AW-undefined&l=unifiedDataLayer&cx=c... line 546, col 244 |
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 |
|---|---|
accounts.google.com/gsi/client line 85, col 88 | [GSI_LOGGER]: FedCM get() rejects with NetworkError: Error retrieving a token. |
Not signed in with the identity provider. |
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.
Send Feedback