Website review, no card needed

Airbnb logo

airbnb.com website review

Visit site (opens in a new tab)Reviewed 11 October 202638 issues · 76 checks

This review found 38 issues worth fixing on airbnb.com, 11 of them high impact, across 76 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

Read the full growth playbook for Airbnb

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.0 s2.8 sApr 18Oct 32.8 s
Show as table
DateReal-visitor load time (LCP)
Apr 18, 20262.9 s
Apr 25, 20262.9 s
May 2, 20262.9 s
May 9, 20262.9 s
May 16, 20262.9 s
May 23, 20262.9 s
May 30, 20262.9 s
Jun 6, 20262.9 s
Jun 13, 20263.0 s
Jun 20, 20263.0 s
Jun 27, 20263.0 s
Jul 4, 20263.0 s
Jul 11, 20263.0 s
Jul 18, 20263.0 s
Jul 25, 20263.0 s
Aug 1, 20262.9 s
Aug 8, 20263.0 s
Aug 15, 20263.0 s
Aug 22, 20263.0 s
Aug 29, 20263.0 s
Sep 5, 20263.0 s
Sep 12, 20263.0 s
Sep 19, 20262.9 s
Sep 26, 20262.9 s
Oct 3, 20262.8 s
Real-visitor tap response (INP)75th percentile, phones
272 ms252 msApr 18Oct 3270 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 2026263 ms
Apr 25, 2026263 ms
May 2, 2026262 ms
May 9, 2026261 ms
May 16, 2026256 ms
May 23, 2026254 ms
May 30, 2026255 ms
Jun 6, 2026257 ms
Jun 13, 2026259 ms
Jun 20, 2026260 ms
Jun 27, 2026259 ms
Jul 4, 2026260 ms
Jul 11, 2026260 ms
Jul 18, 2026260 ms
Jul 25, 2026260 ms
Aug 1, 2026259 ms
Aug 8, 2026259 ms
Aug 15, 2026261 ms
Aug 22, 2026262 ms
Aug 29, 2026262 ms
Sep 5, 2026263 ms
Sep 12, 2026263 ms
Sep 19, 2026265 ms
Sep 26, 2026268 ms
Oct 3, 2026270 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of airbnb.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. airbnb.com at 0.4 s0.4 s
  2. airbnb.com at 0.8 s0.8 s
  3. airbnb.com at 1.1 s1.1 s
  4. airbnb.com at 1.5 s1.5 s
  5. airbnb.com at 1.9 s1.9 s
  6. airbnb.com at 2.3 s2.3 s
  7. airbnb.com at 2.6 s2.6 s
  8. airbnb.com at 3.0 s3.0 s

Speed

8 to fix50
  • Reduce unused JavaScript

    2.5 s · 720 KiB

    About 720 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.5 s faster on a phone.

  • Reduce unused CSS

    1.9 s · 404 KiB

    About 404 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.9 s faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (muscache.com, The Trade Desk and cloudfront.net and others), adding 3.3 MB and 869 ms of main-thread time.

  • muscache.com adds 852 ms

    852 ms

    muscache.com costs a phone 852 ms of main-thread work and 3.2 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 50

    50/100

    Your mobile performance score is 50 (desktop: 58). Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    700 ms

    29 files block the first paint until they finish downloading. Deferring or inlining them could save about 700 ms.

  • Use efficient cache lifetimes

    450 ms · 59 KiB

    7 files are served with short cache lifetimes, so returning visitors download them again (59 KiB).

  • Main-thread work: 3.6 s

    A phone's processor spends 3.6 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 11 long tasks on the main thread

    11 long tasks block the main thread while loading, the longest for 182 ms. During a long task the page ignores taps.

  • Legacy JavaScript

    10 KiB

    Polyfills for old browsers add 10 KiB JavaScript that modern phones do not need.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 187 ms

    187 ms

    Your server sent the HTML in 187 ms, well inside Google's 600 ms guideline.

Core Web Vitals

10 to fix0
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Largest Contentful Paint: 19.9 s

    19.9 s

    Your largest element takes 19.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Inspiration for future getaways”.

  • Time to Interactive: 24.3 s

    24.3 s

    The page becomes fully interactive after 24.3 s. Good is under 3.8 s.

  • Speed Index: 8.3 s

    8.3 s

    Visually, the page fills in at 8.3 s (Speed Index). Good is under 3.4 s.

  • Real-user LCP: 3.4 s

    3.4 s

    Real visitors wait 3.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 357 ms

    357 ms

    Real visitors wait 357 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.15

    0.15

    For real visitors the layout shifts by 0.15 (75th percentile). Good is under 0.1.

  • Real-user TTFB: 829 ms

    829 ms

    Real visitors wait 829 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Total Blocking Time: 597 ms

    597 ms

    Scripts block taps and scrolling for 597 ms in total while the page loads. Good is under 200 ms.

  • First Contentful Paint: 2.0 s

    2.0 s

    The first text or image appears after 2.0 s on a phone. Good is under 1.8 s.

  • Tap response (INP) held steady for real visitors

    +2%

    Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 263 ms to 270 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    0%

    Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 2.9 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

2 checks passed
  • Real-user FCP: 1.5 s

    1.5 s

    Real visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

1 to fix85
  • Page weight: 3.9 MB in 178 requests

    3.9 MB

    Your homepage downloads 3.9 MB in 178 requests on a phone: scripts 3.2 MB (104), stylesheets 423 KiB (1) and HTML 93 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • About 1.1 g of CO₂ per visit

    1.10 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.10 g of CO₂e: 131.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

4 to fixGoogle 9091
  • [role]s are not contained by their required parent element

    [role]s are not contained by their required parent element (4 elements).

  • Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

    Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (1 element).

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (3 elements)

    All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (2 elements).

1 checks passed
  • 33 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 34 WCAG 2.2 A/AA and best-practice rules on the phone render: 33 passed and 1 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 10085
  • Title is long (74 characters)

    Your title is 74 characters, so Google will cut it off around 60: “Airbnb: Vacation Rentals, Cabins, Beach Houses, Unique Homes & Experiences”.

  • Structured data has 1 problem

    Structured data found (WebSite) but with 1 problem, for example “WebSite: missing name”.

  • No XML sitemap

    No XML sitemap at https://www.airbnb.com/sitemap-master-index.xml.gz, so Google discovers your pages only by following links.

  • 10 internal links, 0 external

    The homepage links to 10 pages on airbnb.com and 0 external pages.

5 checks passed
  • Meta description: 132 characters

    Your meta description is 132 characters: “Get an Airbnb for every kind of trip → 8 million vacation rentals → 2 million Guest Favorites → 220+ countries and regi…”.

  • One H1 headline

    Your main headline reads: “Airbnb homepage”.

  • Canonical URL set

    The canonical URL is https://www.airbnb.com/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

AI search readiness

2 to fix60
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • Parts of the site are closed to 3 AI crawlers

    Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User) and Perplexity (PerplexityBot) read the homepage but closes other sections to them, so answers about those pages can't cite you.

  • No llms.txt

    There is no https://www.airbnb.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

  • Opted out of AI training for 3 crawlers

    robots.txt blocks GPTBot, ClaudeBot and Applebot-Extended, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

Other pages

4 to fix75
  • 2 linked pages hidden from search

    https://www.airbnb.com/homes and https://www.airbnb.com/co-hosts/home are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 6 pages share a title

    /, https://www.airbnb.com/homes, https://www.airbnb.com/experiences, https://www.airbnb.com/services, https://www.airbnb.com/help and https://www.airbnb.com/co-hosts/home all use the title “Airbnb: Vacation Rentals, Cabins, Beach Houses, Unique Homes & Experi…”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages without a meta description

    https://www.airbnb.com/help and https://www.airbnb.com/co-hosts/home have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.airbnb.com/co-hosts/home has no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://www.airbnb.com/experiences and https://www.airbnb.com/services have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 1 page slow to respond

    https://www.airbnb.com/co-hosts/home took over 3 s to send its HTML from our server.

  • 7 internal pages checked

    We fetched 7 pages linked from your homepage and read each the way a search engine does.

3 checks passed
  • Linked pages load

    All 7 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a title

    All 7 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'getRegistration')”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    6 of 7 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix50
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • Only about 30 words

    The homepage has only about 30 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

2 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Log in or sign up”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

Privacy and tracking

  • 7 cookies set on arrival

    7

    Opening the homepage sets 7 cookies (measured from a US location before any click).

  • No consent tool detected

    No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

  • 2 other companies contacted

    Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at airbnb.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on airbnb.com, including 18 speed issues, 3 SEO issues and 5 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25