Lighthouse Mobile

· 0 checks — Mobile 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.

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.

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-DIV

nodeLabel: Stay with Locals and Meet Travelers Share Authentic Travel Experiences Sign Up …

path: 1,HTML,1,BODY,1,DIV,1,MAIN,1,DIV

selector: body.__variable_06d0dd > div.public-layout_container__P0jbi > main.public-layout_main__pMzeJ > div.default-background-layout_background__jJ9Hu

snippet: <div class="default-background-layout_background__jJ9Hu">

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

value: no origins were preconnected

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

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
connect.facebook.net/en_US/bundle/sdk.js/	1200.0 s	77.8 KiB
static.hotjar.com/c/hotjar-5054013.js?sv=6	60.0 s	6.2 KiB
connect.facebook.net/en_US/sdk.js	1200.0 s	5.0 KiB

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.

URL	Transfer Size
www.couchsurfing.com/_next/static/css/41e707f4844fd798.css	1.3 KiB
www.couchsurfing.com/_next/static/css/a3026e26ffce4ce1.css	4.5 KiB
www.couchsurfing.com/_next/static/css/18c9f0afcd137cb8.css	3.8 KiB
www.couchsurfing.com/_next/static/css/7607cb9e43dac3dc.css	897 B
www.couchsurfing.com/_next/static/css/aa021322dc339b14.css	1.4 KiB
www.couchsurfing.com/_next/static/css/6cc27ca3e0c8ea92.css	967 B
www.couchsurfing.com/_next/static/css/09a07f06d80877ff.css	1.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: 2.1 s

URL	Time Spent
couchsurfing.com/	1.0 s
www.couchsurfing.com/	1.1 s
www.couchsurfing.com/welcome	0.0 ms

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

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

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 330 ms 192.2 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=GTM-KC3GXKG	84.6 KiB	55.4 KiB
connect.facebook.net/en_US/bundle/sdk.js/	77.7 KiB	54.3 KiB
script.hotjar.com/modules.6a0f3932cb1341a35c18.js	56.1 KiB	37.7 KiB
www.couchsurfing.com/_next/static/chunks/1286-53c199d3d7e9bf7c.js	44.4 KiB	24.4 KiB
www.couchsurfing.com/_next/static/chunks/6472.979f65e4eacac81f.js	44.5 KiB	20.4 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.couchsurfing.com/_next/static/chunks/6233-4276772c5b8d0986.js	546 ms	511 ms	13 ms
Unattributable	390 ms	11 ms	0.0 ms
www.couchsurfing.com/welcome	387 ms	11 ms	19 ms
www.couchsurfing.com/_next/static/chunks/1286-53c199d3d7e9bf7c.js	238 ms	212 ms	14 ms
script.hotjar.com/modules.6a0f3932cb1341a35c18.js	172 ms	148 ms	19 ms
www.couchsurfing.com/_next/static/chunks/6472.979f65e4eacac81f.js	134 ms	112 ms	14 ms
www.couchsurfing.com/_next/static/chunks/cae36a94-de4f6f4a971ae9ca.js	113 ms	93 ms	18 ms
connect.facebook.net/en_US/bundle/sdk.js/	76 ms	54 ms	21 ms
www.googletagmanager.com/gtag/js?id=GTM-KC3GXKG	61 ms	42 ms	18 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	1.3 s
Other	477 ms
Style & Layout	235 ms
Script Parsing & Compilation	211 ms
Parse HTML & CSS	56 ms
Garbage Collection	42 ms
Rendering	18 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

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

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Avoids enormous network payloads Total size was 850 KiB

●Avoid long main-thread tasks 9 long tasks found

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

●Network Requests

●Network Round Trip Times 100 ms

●Server Backend Latencies 260 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

○INP breakdown

○User Timing marks and measures

○Avoid non-composited animations

○Avoid large layout shifts

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

When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
English `div.footer_container__SPP1V > section.footer_internalLinksRow__vQsZD > div.MuiInputBase-root > div.MuiSelect-select`

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Log In `header.MuiPaper-root > nav.MuiToolbar-root > div.header_rightGroup__WNzBQ > button.MuiButtonBase-root`
Join `div.home-page_cards__Y1Lye > div.card_card__R8e1Q > form.sign-up-form_form__YEjuc > button.MuiButtonBase-root`
CONNECT WITH US `div.footer_container__SPP1V > section.footer_socialAndAppsRow__MIHUB > div.footer_socialLinks__7pShi > h3`
MOBILE APPS `div.footer_container__SPP1V > section.footer_socialAndAppsRow__MIHUB > div.footer_socialLinks__7pShi > h3`
© 1999 - 2026 Couchsurfing International, Inc. `footer.footer_footer__LUXkQ > div.footer_container__SPP1V > section.footer_legalLinksRow__xJpGG > span.footer_legalLink__fAT6O`
Terms `nav > ul > li > a.footer_legalLink__fAT6O`
Privacy `nav > ul > li > a.footer_legalLink__fAT6O`
Sitemap `nav > ul > li > a.footer_legalLink__fAT6O`

These are opportunities to improve the legibility of your content.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
nav > ul > li > a.MuiButtonBase-root `nav > ul > li > a.MuiButtonBase-root`
nav > ul > li > a.MuiButtonBase-root `nav > ul > li > a.MuiButtonBase-root`
nav > ul > li > a.MuiButtonBase-root `nav > ul > li > a.MuiButtonBase-root`
nav > ul > li > a.MuiButtonBase-root `nav > ul > li > a.MuiButtonBase-root`
nav > ul > li > a.MuiButtonBase-root `nav > ul > li > a.MuiButtonBase-root`
nav > ul > li > a.MuiButtonBase-root `nav > ul > li > a.MuiButtonBase-root`

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.

○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

●`[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.

●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

●Document has a `<title>` element

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

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

●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

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

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

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○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

○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

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

○Skip links are focusable.

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

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

○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

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.

Source	Description
www.couchsurfing.com/icon.ico?92c0960e5187896d	`Failed to load resource: the server responded with a status of 404 ()`
rest.iad-05.braze.com/api/v3/data/	`Failed to load resource: the server responded with a status of 404 ()`

●Uses HTTPS

●Avoids deprecated APIs

●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

●Mitigate DOM-based XSS with Trusted Types

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Ensure proper origin isolation with COOP

○Mitigate clickjacking with XFO or CSP

○Detected JavaScript libraries

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`