Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
d0a7e.airbnb.com/tags.js	2566.0 s	40.3 KiB
js.adsrvr.org/conversionEvents-v1.min.js	0.0 ms	11.2 KiB
d34r8q7sht0t9k.cloudfront.net/tag.js	0.0 ms	5.8 KiB
/tag?action=view&user_id=62a14177-f845-455c-99f0-abf77e60...	0.0 ms	238 B
/tr?id=674478425975295&ev=Contact&dl=https%3A%2F%2Fwww.ai...	0.0 ms	19 B
/tr?id=674478425975295&ev=PageView&dl=https%3A%2F%2Fwww.a...	0.0 ms	16 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:2.79 source:map[column:1119 line:14 type:source-location url:https://a0.muscache.com/airbnb/static/packages/web/common/frontend/core-guest-loop/apps/core-guest-spa/initializer.1bfe543485.js urlProvider:network]] map[reflowTime:33.047 source:map[type:text value:[unattributed]]] map[reflowTime:51.256 source:map[column:532 line:18 type:source-location url:https://a0.muscache.com/airbnb/static/packages/web/common/4fe2.d18e451bb5.js urlProvider:network]]]

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.

title: Preconnected origins

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

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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: 240 ms 299.0 KiB

URL	Transfer Size	Est Savings
/airbnb/static/packages/web/common/frontend/core-guest-lo...	314.6 KiB	299.0 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

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 200 ms 295.0 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-2P6Q8PGG16&cx=c&gtm=4e6411h1	163.0 KiB	62.6 KiB
www.googletagmanager.com/gtm.js?id=GTM-46MK	171.7 KiB	52.0 KiB
a0.muscache.com/airbnb/static/packages/web/en/cfe2.d4e669892f.js	61.8 KiB	30.6 KiB
a0.muscache.com/airbnb/static/packages/web/common/ecdc.7f5695f079.js	96.6 KiB	27.1 KiB
a0.muscache.com/airbnb/static/packages/web/en/6497.206771ab41.js	36.2 KiB	26.8 KiB
/airbnb/static/packages/web/en/frontend/core-guest-loop/a...	96.2 KiB	26.6 KiB
/airbnb/static/packages/web/en/frontend/stays-search/rout...	35.5 KiB	24.5 KiB
a0.muscache.com/airbnb/static/packages/web/common/2f99.0f3cfcd6b1.js	52.8 KiB	24.4 KiB
a0.muscache.com/airbnb/static/packages/web/en/45b1.14058fde29.js	54.7 KiB	20.5 KiB

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
www.airbnb.com/	797 ms	456 ms	1.4 ms
Unattributable	690 ms	48 ms	0.0 ms
a0.muscache.com/airbnb/static/packages/web/en/4ab0.5d19bb91ce.js	426 ms	329 ms	2.2 ms
a0.muscache.com/airbnb/static/packages/web/common/2f99.0f3cfcd6b1.js	338 ms	17 ms	5.6 ms
a0.muscache.com/airbnb/static/packages/web/common/01f5.12df2efd0d.js	321 ms	244 ms	4.2 ms
www.googletagmanager.com/gtm.js?id=GTM-46MK	267 ms	239 ms	22 ms
a0.muscache.com/airbnb/static/packages/web/common/ecdc.7f5695f079.js	234 ms	216 ms	11 ms
www.googletagmanager.com/gtag/js?id=G-2P6Q8PGG16&cx=c&gtm=4e6411h1	156 ms	133 ms	18 ms
a0.muscache.com/airbnb/static/packages/web/en/cfe2.d4e669892f.js	155 ms	136 ms	7.3 ms
d0a7e.airbnb.com/tags.js	154 ms	116 ms	12 ms
a0.muscache.com/airbnb/static/packages/web/en/bf69.288b064d50.js	143 ms	86 ms	5.1 ms
/airbnb/static/packages/web/en/frontend/core-guest-loop/a...	126 ms	110 ms	12 ms
/airbnb/static/packages/web/common/frontend/core-guest-lo...	104 ms	98 ms	0.6 ms
a0.muscache.com/airbnb/static/packages/web/common/9dcb.92da8dd9e4.js	64 ms	61 ms	2.7 ms
a0.muscache.com/airbnb/static/packages/web/common/4fe2.d18e451bb5.js	63 ms	0.5 ms	2.7 ms
/airbnb/static/packages/web/common/frontend/core-guest-lo...	56 ms	0.0 ms	0.0 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.

Category	Time Spent
Script Evaluation	2.7 s
Other	1.1 s
Style & Layout	324 ms
Script Parsing & Compilation	294 ms
Garbage Collection	157 ms
Parse HTML & CSS	106 ms
Rendering	93 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 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
/airbnb/static/packages/web/common/frontend/core-guest-lo...	314.7 KiB
www.googletagmanager.com/gtm.js?id=GTM-46MK	172.0 KiB
www.googletagmanager.com/gtag/js?id=G-2P6Q8PGG16&cx=c&gtm=4e6411h1	163.0 KiB
a0.muscache.com/videos/search-bar-icons/webm/house-twirl-selected.webm	120.7 KiB
/airbnb/static/packages/web/en/frontend/airmetro/browser/...	110.5 KiB
a0.muscache.com/airbnb/static/packages/web/common/ecdc.7f5695f079.js	96.7 KiB
/airbnb/static/packages/web/en/frontend/core-guest-loop/a...	96.2 KiB
www.airbnb.com/	95.9 KiB
a0.muscache.com/videos/search-bar-icons/webm/balloon-twirl.webm	68.4 KiB
a0.muscache.com/videos/search-bar-icons/webm/house-selected.webm	62.5 KiB

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

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●Improve image delivery

●LCP breakdown

●LCP request discovery

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●User Timing marks and measures 14 user timings

●Avoid long main-thread tasks 16 long tasks found

●Image elements have explicit `width` and `height`

●Network Requests

●Network Round Trip Times 240 ms

●Server Backend Latencies 310 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

●Initial server response time was short Root document took 50 ms

●Avoid large layout shifts 3 layout shifts found

○INP breakdown

○Avoid non-composited animations

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

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
Guest favorite Guest favorite Home in Yeonnam-dong $6,710 TWD for 2 nights $6… `div.awuxh4x > div.cw9aemg > div.c14whb16 > div`
Guest favorite Guest favorite Home in Seoul $7,905 TWD for 2 nights $7,905 TW… `div.awuxh4x > div.cw9aemg > div.c14whb16 > div`
See all `div.awuxh4x > div.cw9aemg > div.c14whb16 > div`
Guest favorite Guest favorite Apartment in Sumida-ku $9,146 TWD for 2 nights … `div.awuxh4x > div.cw9aemg > div.c14whb16 > div`
Guest favorite Guest favorite Apartment in Kōtō-ku $13,283 TWD for 2 nights $… `div.awuxh4x > div.cw9aemg > div.c14whb16 > div`
See all `div.awuxh4x > div.cw9aemg > div.c14whb16 > div`
Guest favorite Guest favorite Home in Dong-gu $35,986 TWD for 2 nights $35,98… `div.awuxh4x > div.cw9aemg > div.c14whb16 > div`
Guest favorite Guest favorite Home in Dong-gu $12,934 TWD for 2 nights $12,93… `div.awuxh4x > div.cw9aemg > div.c14whb16 > div`
See all `div.awuxh4x > div.cw9aemg > div.c14whb16 > div`
Guest favorite Guest favorite Apartment in Osaka $4,900 TWD for 2 nights $4,9… `div.awuxh4x > div.cw9aemg > div.c14whb16 > div`
Guest favorite Guest favorite Apartment in Osaka $4,214 TWD for 2 nights $4,2… `div.awuxh4x > div.cw9aemg > div.c14whb16 > div`
See all `div.awuxh4x > div.cw9aemg > div.c14whb16 > div`
Guest favorite Guest favorite Place to stay in West Central District $5,535 TWD… `div.awuxh4x > div.cw9aemg > div.c14whb16 > div`
Guest favorite Guest favorite Bed and breakfast in 萬昌里 $1,952 TWD for 2 night… `div.awuxh4x > div.cw9aemg > div.c14whb16 > div`
See all `div.awuxh4x > div.cw9aemg > div.c14whb16 > div`

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.

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
English (US) `div._192cbhg > div._jro6t0 > span._9pd3yk > button.l1ovpqvx`
$ TWD `div._192cbhg > div._jro6t0 > span._9pd3yk > button.l1ovpqvx`

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

●`[role]`s are contained by their required parent element

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●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

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links have a discernible name

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Image elements have `[alt]` attributes

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Links are distinguishable without relying on color.

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

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

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 / Warning	Source
AttributionReporting	d0a7e.airbnb.com/tags.js line 1, col 113441

●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 browser errors logged to the console

●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

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

○Image elements have `[alt]` attributes