Skip to content
Audit Complete

Results for https://headspace.com

Visit site
E-commerce · estimated Tracking: purchases
Spain Spain · Madrid Completed: Apr 21, 2026 22:47 UTC
Share card preview
Share on X Share on LinkedIn Share on Reddit Share on Hacker News Share via Email Download share image Embed Badge
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)
C77

Site Health

Score: 77 / 100

Based on 8 categories, 0 sections

Decent speed, but optimizing further could improve engagement.

Good foundation, but a few gaps could be exploited.

Several issues make your site difficult for assistive technology users.

Well-optimized for search — your content is discoverable.

Solid infrastructure — fast server responses across the board.

Strong compliance posture across regulations.

Rich content metadata — your pages look great everywhere.

Reasonable footprint with room for optimization.

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

Cart Functionality · 356 peers
You 77
·
Avg 72
At average
0 50 100
Better than 88% of Cart Functionality sites See full Cart Functionality benchmark →
Contentful · 66 peers
You 77
·
Avg 73
At average
0 50 100
Better than 83% of Contentful sites See full Contentful benchmark →

Top Priorities (5)

1

HSTS header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
2

8 button(s) with no accessible text

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Link & Button Quality
3

No H1 heading found

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Heading Hierarchy
4

130 third-party resources (100% of weight)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Inventory
5

131 HTTP requests — consider bundling or reducing

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Budget
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

1

High impact, low effort — start here.

Strategic

4

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%2Fheadspace.com)](https://beavercheck.com/results/61441d0e-cd4c-4d49-8981-297a9b5ff321)
<a href="https://beavercheck.com/results/61441d0e-cd4c-4d49-8981-297a9b5ff321"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fheadspace.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fheadspace.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 16.4s exceeds Google's 2.5s 'Good' threshold and the 2 performance issues below directly contribute to it. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.

1 security gap detected — browsers may warn visitors about your site.
2 accessibility issues exclude users who rely on assistive technology.
Your LCP is 16.4s — fixing the 2 performance criticals could bring it under Google's 2.5s 'Good' threshold.
B
Could reach Estimate based on resolving critical issues

Conversion Barriers

3 critical 3 warning

6 barrier(s) likely increasing bounce by ~28%.

Speed (2)

Page takes 16.4s to load

+12% bounce

Users abandon at ~3s — you're 13.9s over the 2.5s threshold

Fix: Optimize render-blocking resources, preload the hero image, and compress images

Page feels frozen for 1.6s

+5% bounce

Clicks on the primary CTA are ignored while JavaScript runs

Fix: Break up long tasks; defer non-critical JavaScript to post-hydration

Trust (2)

No HSTS header

+1% bounce

Returning visitors are briefly exposed to downgrade attacks on first request

Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Navigation (2)

No skip-to-content link

+1% bounce

Keyboard and screen-reader users must tab through the entire header on every page

Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

8 broken link(s) on the page

+5% bounce

Clicks land on 404s — trust drops and the session often ends

Fix: Fix or remove the broken destinations surfaced on the Content tab

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

€638 investment → €0.63/month returns + EUR 120,500,000 risk avoided

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

Investment

€638

8h · 5 findings

Monthly returns

€0.63 /mo

~€7.51 / year

  • Bandwidth savings €0.63

Regulatory risk avoided

EUR 120,500,000

if kept compliant

  • ePrivacy Directive EUR 100,000,000
  • GDPR EUR 20,000,000
  • EAA EUR 500,000

€43 — 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

€638

7.5 developer hours at €85/hr

Based on European Union rates (€85/hr)

Quick wins
€43 1 fixes in ~30 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

€10,041,667 / month at risk

~€120,500,008 / year if left unfixed

Compliance Risk

€120,500,000

ePrivacy DirectiveGDPREAA
  • No privacy policy link detected
    GDPR: EUR 10,000 – EUR 20,000,000
  • Trackers detected but no cookie policy found
    GDPR: EUR 5,000 – EUR 10,000,000
  • Trackers detected but no cookie policy found
    GDPR: EUR 10,000 – EUR 20,000,000

+7 more

Bandwidth Waste

€0.63 /mo

8445.1 MB/mo × 0.074 EUR/GB

  • Optimize transfer: save ~845 KB per page load
    Saves €0.63/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 3 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.

40
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
80
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
96
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
92
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.

1.96 s

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

16.39 s

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

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

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

16.79 s

Detailed Report

Audit breakdown by category with detailed findings.

40

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.

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.

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:33.893 source:map[column:3222 line:2 type:source-location url:https://www.headspace.com/web-marketing-ssr/_next/static/chunks/1a0bb58acbf0b64b.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:13.026 source:map[column:3307 line:1 type:source-location url:https://www.headspace.com/web-marketing-ssr/_next/static/chunks/99d95ce90602ecc5.js urlProvider:network]] map[reflowTime:7.668 source:map[column:3240 line:1 type:source-location url:https://www.headspace.com/web-marketing-ssr/_next/static/chunks/2badd6ee75fd8c34.js urlProvider:network]] map[reflowTime:12.825 source:map[column:20811 line:27 type:source-location url:https://www.headspace.com/web-marketing-ssr/_next/static/chunks/3d2826b45ab622f0.js urlProvider:network]] map[reflowTime:0.374 source:map[column:1959 line:1 type:source-location url:https://www.headspace.com/web-marketing-ssr/_next/static/chunks/aa99defd249a0799.js urlProvider:network]] map[reflowTime:0.631 source:map[column:28146 line:1 type:source-location url:https://www.headspace.com/web-marketing-ssr/_next/static/chunks/acef2f75a2e09886.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:373.404 label:Time to first byte subpart:timeToFirstByte] map[duration:2268.642 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-image
nodeLabel: g#__lottie_element_73 > g > image
path: 1,HTML,1,BODY,2,DIV,0,MAIN,0,DIV,0,DIV,0,DIV,0,DIV,4,DIV,2,DIV,0,DIV,0,DIV,3,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,svg,0,defs,11,mask,0,use,a,#document-fragment,0,g,0,g,0,image
selector: g#__lottie_element_73 > g > image
snippet: <image width="953px" height="2052px" preserveAspectRatio="xMidYMid slice" xlink:href="data:image/webp;base64,UklGRlIUAABXRUJQVlA4WAoAAAAQAAAAuAMAAwgAQUxQSMQFAAA…">

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

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
3 XR (featured tab) div.css-hsndhj > div.css-uk4blr > div.css-1ghcia1 > img
/7eroL3xuLOcFmA8syXUURf/8a96742ca71fc4a30df92bc99033860c/...36.3 KiB28.7 KiB
Jan '25 Campaign Explore Screen Mock div.css-1q921eg > div.css-1dmsota > div.css-9fi4om > img.css-cnin99
/1PZPNpQTJTlXQGGTCoSwpJ/8d7354aa03d2bada6b93b5c326edfb2c/...25.7 KiB24.2 KiB
Image (hero with carousel) div.css-eahfdh > div.css-5fdnnx > div.css-1ghcia1 > img
/5pirBM9z8X75FdOGjFnBID/c378cfeff2a4f8fa03ac0b8422ec58a6/...26.3 KiB22.6 KiB
d-deepdive div.css-1q921eg > div.css-1er1l76 > div.css-bsd05i > img.css-cnin99
/7mX035RsbYG48uXqLpbPE2/8a9b19a53d4fb1346ead0bc94fc86ec7/...23.6 KiB20.4 KiB
desktop hero 2 june5 2x 1 copy div.css-37k3ha > div.css-12auco2 > picture > img.css-uwwqev
/6VpOlWMhXWZPcWW4MpGU7/1565fd18e33da0d5e2c46715b5bcff96/m...18.1 KiB12.9 KiB
5 Ebb 1x div.css-hsndhj > div.css-uk4blr > div.css-1ghcia1 > img
/257VMfFX7e1wGy2MhRzUl6/1d57fc4eab72991b1703f54c82ce99d0/...13.3 KiB12.7 KiB
desktop hero 1 june5 2x 1 copy div.css-37k3ha > div.css-12auco2 > picture > img.css-uwwqev
/knWuaYQdTnPg6o6VPtH1K/a0e32e013ebad294eb678f92334eba49/m...17.2 KiB12.3 KiB

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

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.

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
headspace.com/790 ms
www.headspace.com/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

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

Estimated savings: 1.2 s 253.4 KiB
URLTransfer SizeEst Savings
cdn.amplitude.com/libs/plugin-session-replay-browser-1.25.0-min.js.gz128.2 KiB100.2 KiB
/gtm.js?id=GTM-M92JXMV&gtm_auth=16iCHRn1z7748mckvKDXyw&gt...142.0 KiB66.5 KiB
www.headspace.com/web-marketing-ssr/_next/static/chunks/c00d49f0c10b04ae.js69.7 KiB34.4 KiB
www.headspace.com/web-marketing-ssr/_next/static/chunks/92df9b1810b1aa1b.js77.8 KiB26.6 KiB
www.headspace.com/web-marketing-ssr/_next/static/chunks/3d2826b45ab622f0.js62.4 KiB25.7 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.

URLTotal CPU TimeScript EvaluationScript Parse
www.headspace.com/web-marketing-ssr/_next/static/chunks/1a0bb58acbf0b64b.js3.1 s2.8 s17 ms
www.headspace.com/web-marketing-ssr/_next/static/chunks/c15c7cf7199d6fd1.js2.9 s1.0 s4.2 ms
www.headspace.com/web-marketing-ssr/_next/static/chunks/d775b5b016d581e0.js1.5 s244 ms7.9 ms
Unattributable717 ms41 ms0.0 ms
www.headspace.com/672 ms19 ms1.4 ms
www.headspace.com/web-marketing-ssr/_next/static/chunks/e9bc471870d3795c.js553 ms493 ms3.5 ms
www.headspace.com/web-marketing-ssr/_next/static/chunks/3d2826b45ab622f0.js312 ms280 ms31 ms
/web-marketing-ssr/_next/static/chunks/turbopack-40d0ce1d...305 ms304 ms0.8 ms
/web-marketing-ssr/_next/static/chunks/turbopack-4e420115...298 ms296 ms0.9 ms
www.headspace.com/web-marketing-ssr/_next/static/chunks/1176527437f54d87.js194 ms167 ms0.8 ms
www.headspace.com/web-marketing-ssr/_next/static/chunks/147a85d641673945.js176 ms152 ms1.0 ms
cdn.amplitude.com/libs/plugin-session-replay-browser-1.25.0-min.js.gz174 ms134 ms36 ms
/gtm.js?id=GTM-M92JXMV&gtm_auth=16iCHRn1z7748mckvKDXyw&gt...161 ms129 ms31 ms
www.headspace.com/web-marketing-ssr/_next/static/chunks/45d9171378f09c0e.js95 ms62 ms1.2 ms
www.headspace.com/web-marketing-ssr/_next/static/chunks/c00d49f0c10b04ae.js89 ms68 ms20 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 Evaluation6.3 s
Other3.7 s
Style & Layout705 ms
Script Parsing & Compilation343 ms
Rendering339 ms
Garbage Collection162 ms
Parse HTML & CSS81 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

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.

URLTransfer Size
/5m9VJCmN6BVAY3lB1Uv7Qm/c4f37868139210511b607491c7e0f559/...896.8 KiB
/gtm.js?id=GTM-M92JXMV&gtm_auth=16iCHRn1z7748mckvKDXyw&gt...142.4 KiB
cdn.amplitude.com/libs/plugin-session-replay-browser-1.25.0-min.js.gz130.8 KiB
www.headspace.com/web-marketing-ssr/_next/static/chunks/92df9b1810b1aa1b.js81.3 KiB
/v3n26e09qg2r/5LLXVejkCFopJVRCZMSwdK/08b6c6d83292f679954d...79.3 KiB
www.headspace.com/web-marketing-ssr/_next/static/chunks/c00d49f0c10b04ae.js70.2 KiB
www.headspace.com/64.6 KiB
www.headspace.com/web-marketing-ssr/_next/static/chunks/3d2826b45ab622f0.js62.9 KiB
www.headspace.com/web-marketing-ssr/_next/static/chunks/1a0bb58acbf0b64b.js60.7 KiB
cdn.amplitude.com/libs/analytics-browser-2.25.1-min.js.gz49.9 KiB

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

●Use efficient cache lifetimes
●Layout shift culprits
●Optimize DOM size
●Font display
●Modern HTTP
●Render blocking requests
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Reduce unused CSS
●User Timing marks and measures 6 user timings
●Avoid long main-thread tasks 18 long tasks found
●Avoid non-composited animations 4 animated elements found
●Image elements have explicit `width` and `height`
●Network Requests
●Network Round Trip Times 20 ms
●Server Backend Latencies 40 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 320 ms
○INP breakdown
○LCP request discovery
○Avoid large layout shifts
80

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 a `progressbar` element 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 how to label `progressbar` elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.css-dymk12 > div.css-2ohn2g > div.css-13ndvf0 > div.css-1z038j1 div.css-dymk12 > div.css-2ohn2g > div.css-13ndvf0 > div.css-1z038j1
div.css-dymk12 > div.css-2ohn2g > div.css-13ndvf0 > div.css-1z038j1 div.css-dymk12 > div.css-2ohn2g > div.css-13ndvf0 > div.css-1z038j1
div.css-dymk12 > div.css-2ohn2g > div.css-13ndvf0 > div.css-1z038j1 div.css-dymk12 > div.css-2ohn2g > div.css-13ndvf0 > div.css-1z038j1

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Ebb div.css-fpmqj3 > svg > g > g
You div.css-fpmqj3 > svg > g > g

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
header#navbar-header-header > div.css-1b5cois > nav.css-4kugue > button.css-v74ccp header#navbar-header-header > div.css-1b5cois > nav.css-4kugue > button.css-v74ccp
div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-12nesms div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-12nesms
div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-1hati0i div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-1hati0i
div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-1hati0i div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-1hati0i
div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-1hati0i div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-1hati0i
div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-1hati0i div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-1hati0i
div.css-hfwumi > div.css-13unig > div > button.css-1qi2pw5 div.css-hfwumi > div.css-13unig > div > button.css-1qi2pw5
div.css-hfwumi > div.css-13unig > div > button.css-1qi2pw5 div.css-hfwumi > div.css-13unig > div > button.css-1qi2pw5

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.

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
Stress less div.css-gd0lmb > div.css-14ntoh4 > div.css-h02uj7 > div.css-m6qmz1
0.0k div.css-15vu3re > div.css-12uavp7 > div.css-10xddwb > p.css-1vuavp0
meditating div.css-15vu3re > div.css-12uavp7 > div.css-10xddwb > p.css-1xr9gj
Join the millions who use Headspace every day div.css-1m771rd > div.css-15vu3re > div.css-12uavp7 > h2.css-161yfi3
App Store Rating div.css-12uavp7 > div.css-ulqck6 > div.css-3io4e8 > p.css-1vw7yqm
0M+ div.css-12uavp7 > div.css-ulqck6 > div.css-3io4e8 > p.css-3kok21
Downloads div.css-12uavp7 > div.css-ulqck6 > div.css-3io4e8 > p.css-1vw7yqm
0M+ div.css-12uavp7 > div.css-ulqck6 > div.css-3io4e8 > p.css-3kok21
Minutes Meditated div.css-12uavp7 > div.css-ulqck6 > div.css-3io4e8 > p.css-1vw7yqm
Selected Awards div.css-12uavp7 > div.css-ulqck6 > div.css-3io4e8 > p.css-1vw7yqm

These are opportunities to improve the legibility of your content.

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
Meet Ebb div.css-hsndhj > div.css-15vu3re > div.css-1kp8ita > h5.css-hblk6z
My Headspace div.css-1hg1vm1 > div.css-yh8ihz > div.css-1clntmr > h4.css-1j454q2

These are opportunities to improve keyboard navigation in your application.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-12nesms div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-12nesms
div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-1hati0i div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-1hati0i
div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-1hati0i div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-1hati0i
div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-1hati0i div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-1hati0i
div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-1hati0i div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-1hati0i

These items highlight common accessibility best practices.

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

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.

SourceDescription
www.headspace.com/web-marketing-ssr/_next/static/chunks/1a0bb58acbf0b64b.js line 1, col 40310
Error: Minified React error #418; visit https://react.dev/errors/418?args[]=HTML&args[]= for the full message or use the non-minified dev environment for full errors and additional helpful warnings. at rR (https://www.headspace.com/web-marketing-ssr/_next/static/chunks/1a0bb58acbf0b64b.js:2:40311) at oW (https://www.headspace.com/web-marketing-ssr/_next/static/chunks/1a0bb58acbf0b64b.js:2:90177) at ub (https://www.headspace.com/web-marketing-ssr/_next/static/chunks/1a0bb58acbf0b64b.js:2:121264) at https://www.headspace.com/web-marketing-ssr/_next/static/chunks/1a0bb58acbf0b64b.js:2:121109 at uv (https://www.headspace.com/web-marketing-ssr/_next/static/chunks/1a0bb58acbf0b64b.js:2:121117) at ui (https://www.headspace.com/web-marketing-ssr/_next/static/chunks/1a0bb58acbf0b64b.js:2:116492) at uX (https://www.headspace.com/web-marketing-ssr/_next/static/chunks/1a0bb58acbf0b64b.js:2:139624) at MessagePort.R (https://www.headspace.com/web-marketing-ssr/_next/static/chunks/1a0bb58acbf0b64b.js:2:3461)
www.headspace.com/auth/profile
Failed to load resource: the server responded with a status of 401 ()
www.headspace.com/auth/profile
Failed to load resource: the server responded with a status of 401 ()
static.headspace.com/fonts/apercu/apercu_mono_pro_regular.woff2
Failed to load resource: the server responded with a status of 404 ()
static.headspace.com/fonts/apercu/apercu_mono_pro_bold.woff2
Failed to load resource: the server responded with a status of 404 ()
static.headspace.com/fonts/apercu/apercu_mono_pro_medium.woff2
Failed to load resource: the server responded with a status of 404 ()
static.headspace.com/fonts/apercu/apercu_mono_pro_light.woff2
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
●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
92

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.

Content Best Practices

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destinationLink Text
www.headspace.com/meditationLearn more
www.headspace.com/mental-healthLearn more
organizations.headspace.com/?origin=homepageLearn more

Format your HTML in a way that enables crawlers to better understand your app’s content.

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

65
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
78
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
96
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
92
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.

544 ms

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

3.34 s

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

249 ms

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

0.099

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

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

3.36 s

Detailed Report

Audit breakdown by category with detailed findings.

65

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.

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.

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:32.833 source:map[column:3222 line:2 type:source-location url:https://www.headspace.com/web-marketing-ssr/_next/static/chunks/1a0bb58acbf0b64b.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:32.468 source:map[column:20811 line:27 type:source-location url:https://www.headspace.com/web-marketing-ssr/_next/static/chunks/3d2826b45ab622f0.js urlProvider:network]] map[reflowTime:0.365 source:map[column:1959 line:1 type:source-location url:https://www.headspace.com/web-marketing-ssr/_next/static/chunks/aa99defd249a0799.js urlProvider:network]] map[reflowTime:10.726 source:map[column:20924 line:27 type:source-location url:https://www.headspace.com/web-marketing-ssr/_next/static/chunks/3d2826b45ab622f0.js urlProvider:network]] map[reflowTime:1.237 source:map[column:28146 line:1 type:source-location url:https://www.headspace.com/web-marketing-ssr/_next/static/chunks/acef2f75a2e09886.js urlProvider:network]] map[reflowTime:10.235 source:map[column:20125 line:1 type:source-location url:https://www.headspace.com/web-marketing-ssr/_next/static/chunks/7a12eba59d0173f8.js urlProvider:network]]]

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
desktop hero 1 june5 2x 1 copy div.css-37k3ha > div.css-12auco2 > picture > img.css-uwwqev
/2pcwdm6O0Kt0rq19lLLCDC/624cec6f5e77f9d7e0d5de6f02c437b5/...49.0 KiB40.0 KiB
desktop hero 2 june5 2x 1 copy div.css-37k3ha > div.css-12auco2 > picture > img.css-uwwqev
/2KFGacky3sZXtt8KLYJgN6/109838d936853779a57a116f0ff2b4ca/...27.7 KiB22.2 KiB
Jan '25 Campaign Explore Screen Mock div.css-1q921eg > div.css-1dmsota > div.css-9fi4om > img.css-cnin99
/1PZPNpQTJTlXQGGTCoSwpJ/8d7354aa03d2bada6b93b5c326edfb2c/...25.7 KiB20.2 KiB
3 XR (featured tab) div.css-hsndhj > div.css-uk4blr > div.css-1ghcia1 > img
/7eroL3xuLOcFmA8syXUURf/8a96742ca71fc4a30df92bc99033860c/...36.3 KiB17.3 KiB
d-deepdive div.css-1q921eg > div.css-1er1l76 > div.css-bsd05i > img.css-cnin99
/7mX035RsbYG48uXqLpbPE2/8a9b19a53d4fb1346ead0bc94fc86ec7/...23.6 KiB17.3 KiB
homepagenav a.css-rlwou3 > div.css-bm4lwm > div.css-1gr7t27 > img
/5Mvq9tLGfNllvbLYAvpxW3/7e50e746e34d6fbfcdffb15caa86b126/...15.4 KiB13.3 KiB

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:767.371 label:Time to first byte subpart:timeToFirstByte] map[duration:2028.725 label:Element render delay subpart:elementRenderDelay]]
lhId: page-6-image
nodeLabel: g#__lottie_element_381 > g > image
path: 1,HTML,1,BODY,2,DIV,0,MAIN,0,DIV,0,DIV,0,DIV,0,DIV,4,DIV,2,DIV,0,DIV,0,DIV,3,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,svg,0,defs,11,mask,0,use,a,#document-fragment,0,g,0,g,0,image
selector: g#__lottie_element_381 > g > image
snippet: <image width="953px" height="2052px" preserveAspectRatio="xMidYMid slice" xlink:href="data:image/webp;base64,UklGRlIUAABXRUJQVlA4WAoAAAAQAAAAuAMAAwgAQUxQSMQFAAA…">

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

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.

RequestCache TTLTransfer Size
cdn.cookielaw.org/scripttemplates/202405.1.0/otBannerSdk.js86400.0 s109.4 KiB
cdn.cookielaw.org/logos/static/ot_company_logo.png86400.0 s19.1 KiB
cdn.cookielaw.org/scripttemplates/otSDKStub.js86400.0 s9.1 KiB
cdn.cookielaw.org/logos/static/powered_by_logo.svg86400.0 s2.5 KiB
cdn.cookielaw.org/logos/static/ot_close.svg86400.0 s636 B

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

Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 623 ms
URLTime Spent
www.headspace.com/723 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.

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

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

Estimated savings: 80 ms 339.3 KiB
URLTransfer SizeEst Savings
cdn.amplitude.com/libs/plugin-session-replay-browser-1.25.0-min.js.gz130.3 KiB102.3 KiB
/gtm.js?id=GTM-M92JXMV&gtm_auth=16iCHRn1z7748mckvKDXyw&gt...142.0 KiB66.5 KiB
cdn.cookielaw.org/scripttemplates/202405.1.0/otBannerSdk.js109.1 KiB58.7 KiB
www.headspace.com/web-marketing-ssr/_next/static/chunks/c00d49f0c10b04ae.js69.7 KiB34.4 KiB
www.headspace.com/web-marketing-ssr/_next/static/chunks/92df9b1810b1aa1b.js77.8 KiB26.6 KiB
cdn.amplitude.com/libs/analytics-browser-2.25.1-min.js.gz49.4 KiB26.0 KiB
www.headspace.com/web-marketing-ssr/_next/static/chunks/3d2826b45ab622f0.js62.4 KiB24.8 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.

URLTotal CPU TimeScript EvaluationScript Parse
www.headspace.com/web-marketing-ssr/_next/static/chunks/1a0bb58acbf0b64b.js742 ms650 ms4.4 ms
www.headspace.com/web-marketing-ssr/_next/static/chunks/c15c7cf7199d6fd1.js686 ms256 ms1.3 ms
www.headspace.com/web-marketing-ssr/_next/static/chunks/d775b5b016d581e0.js394 ms65 ms2.7 ms
Unattributable260 ms34 ms0.0 ms
www.headspace.com/254 ms4.2 ms0.3 ms
www.headspace.com/web-marketing-ssr/_next/static/chunks/e9bc471870d3795c.js115 ms103 ms0.9 ms
www.headspace.com/web-marketing-ssr/_next/static/chunks/3d2826b45ab622f0.js104 ms94 ms5.1 ms
/web-marketing-ssr/_next/static/chunks/turbopack-4e420115...83 ms83 ms0.2 ms
/web-marketing-ssr/_next/static/chunks/turbopack-40d0ce1d...78 ms77 ms0.2 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 Evaluation1.6 s
Other967 ms
Style & Layout222 ms
Rendering124 ms
Script Parsing & Compilation92 ms
Parse HTML & CSS31 ms
Garbage Collection26 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

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 17.8 KiB
URLTransfer SizeEst Savings
#onetrust-banner-sdk{-ms-text-size-adjust:100%;-webkit-text-size-adjust:100%} …20.5 KiB17.8 KiB

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.

URLTransfer Size
/5m9VJCmN6BVAY3lB1Uv7Qm/c4f37868139210511b607491c7e0f559/...896.5 KiB
/70khQJJM7mYfOOUbCqHRzl/4001cd1b0a2028de86f2ba0776404c35/...345.5 KiB
/gtm.js?id=GTM-M92JXMV&gtm_auth=16iCHRn1z7748mckvKDXyw&gt...142.4 KiB
cdn.amplitude.com/libs/plugin-session-replay-browser-1.25.0-min.js.gz130.8 KiB
cdn.cookielaw.org/scripttemplates/202405.1.0/otBannerSdk.js109.4 KiB
www.headspace.com/web-marketing-ssr/_next/static/chunks/92df9b1810b1aa1b.js81.3 KiB
/v3n26e09qg2r/5LLXVejkCFopJVRCZMSwdK/08b6c6d83292f679954d...79.3 KiB
www.headspace.com/web-marketing-ssr/_next/static/chunks/c00d49f0c10b04ae.js70.2 KiB
www.headspace.com/64.4 KiB
www.headspace.com/web-marketing-ssr/_next/static/chunks/3d2826b45ab622f0.js62.9 KiB

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
●Render blocking requests
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●User Timing marks and measures 6 user timings
●Avoid long main-thread tasks 4 long tasks found
●Avoid non-composited animations 2 animated elements found
●Image elements have explicit `width` and `height`
●Network Requests
●Network Round Trip Times 20 ms
●Server Backend Latencies 30 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Avoid large layout shifts 2 layout shifts found
○INP breakdown
○LCP request discovery
78

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 a `progressbar` element 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 how to label `progressbar` elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.css-dymk12 > div.css-2ohn2g > div.css-13ndvf0 > div.css-1z038j1 div.css-dymk12 > div.css-2ohn2g > div.css-13ndvf0 > div.css-1z038j1
div.css-dymk12 > div.css-2ohn2g > div.css-13ndvf0 > div.css-1z038j1 div.css-dymk12 > div.css-2ohn2g > div.css-13ndvf0 > div.css-1z038j1
div.css-dymk12 > div.css-2ohn2g > div.css-13ndvf0 > div.css-1z038j1 div.css-dymk12 > div.css-2ohn2g > div.css-13ndvf0 > div.css-1z038j1

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Ebb div.css-fpmqj3 > svg > g > g
You div.css-fpmqj3 > svg > g > g

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.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-12nesms div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-12nesms
div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-1hati0i div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-1hati0i
div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-1hati0i div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-1hati0i
div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-1hati0i div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-1hati0i
div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-1hati0i div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-1hati0i
div.css-hfwumi > div.css-13unig > div > button.css-1qi2pw5 div.css-hfwumi > div.css-13unig > div > button.css-1qi2pw5
div.css-hfwumi > div.css-13unig > div > button.css-1qi2pw5 div.css-hfwumi > div.css-13unig > div > button.css-1qi2pw5

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.

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
0.0k div.css-15vu3re > div.css-12uavp7 > div.css-10xddwb > p.css-1vuavp0
meditating div.css-15vu3re > div.css-12uavp7 > div.css-10xddwb > p.css-1xr9gj
Join the millions who use Headspace every day div.css-1m771rd > div.css-15vu3re > div.css-12uavp7 > h2.css-161yfi3
App Store Rating div.css-12uavp7 > div.css-ulqck6 > div.css-3io4e8 > p.css-1vw7yqm
0M+ div.css-12uavp7 > div.css-ulqck6 > div.css-3io4e8 > p.css-3kok21
Downloads div.css-12uavp7 > div.css-ulqck6 > div.css-3io4e8 > p.css-1vw7yqm
0M+ div.css-12uavp7 > div.css-ulqck6 > div.css-3io4e8 > p.css-3kok21
Minutes Meditated div.css-12uavp7 > div.css-ulqck6 > div.css-3io4e8 > p.css-1vw7yqm
Selected Awards div.css-12uavp7 > div.css-ulqck6 > div.css-3io4e8 > p.css-1vw7yqm

These are opportunities to improve the legibility of your content.

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
Meet Ebb div.css-hsndhj > div.css-15vu3re > div.css-1kp8ita > h5.css-hblk6z
My Headspace div.css-1hg1vm1 > div.css-yh8ihz > div.css-1clntmr > h4.css-1j454q2

These are opportunities to improve keyboard navigation in your application.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
For You For Business For Providers Our Plans Resources About header#navbar-header-header > div.css-1euzfgj > nav > ul.css-1gg327v

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-12nesms div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-12nesms
div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-1hati0i div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-1hati0i
div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-1hati0i div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-1hati0i
div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-1hati0i div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-1hati0i
div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-1hati0i div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-1hati0i

These items highlight common accessibility best practices.

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
Learn more div.ot-sdk-eight > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link
○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
●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
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●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
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●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
○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
○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.
○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.
96

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.

SourceDescription
www.headspace.com/web-marketing-ssr/_next/static/chunks/1a0bb58acbf0b64b.js line 1, col 40310
Error: Minified React error #418; visit https://react.dev/errors/418?args[]=HTML&args[]= for the full message or use the non-minified dev environment for full errors and additional helpful warnings. at rR (https://www.headspace.com/web-marketing-ssr/_next/static/chunks/1a0bb58acbf0b64b.js:2:40311) at oW (https://www.headspace.com/web-marketing-ssr/_next/static/chunks/1a0bb58acbf0b64b.js:2:90177) at ub (https://www.headspace.com/web-marketing-ssr/_next/static/chunks/1a0bb58acbf0b64b.js:2:121264) at https://www.headspace.com/web-marketing-ssr/_next/static/chunks/1a0bb58acbf0b64b.js:2:121109 at uv (https://www.headspace.com/web-marketing-ssr/_next/static/chunks/1a0bb58acbf0b64b.js:2:121117) at ui (https://www.headspace.com/web-marketing-ssr/_next/static/chunks/1a0bb58acbf0b64b.js:2:116492) at uX (https://www.headspace.com/web-marketing-ssr/_next/static/chunks/1a0bb58acbf0b64b.js:2:139624) at MessagePort.R (https://www.headspace.com/web-marketing-ssr/_next/static/chunks/1a0bb58acbf0b64b.js:2:3461)
www.headspace.com/auth/profile
Failed to load resource: the server responded with a status of 401 ()
www.headspace.com/auth/profile
Failed to load resource: the server responded with a status of 401 ()
static.headspace.com/fonts/apercu/apercu_mono_pro_medium.woff2
Failed to load resource: the server responded with a status of 404 ()
static.headspace.com/fonts/apercu/apercu_mono_pro_bold.woff2
Failed to load resource: the server responded with a status of 404 ()
static.headspace.com/fonts/apercu/apercu_mono_pro_light.woff2
Failed to load resource: the server responded with a status of 404 ()
static.headspace.com/fonts/apercu/apercu_mono_pro_regular.woff2
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
●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
92

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.

Content Best Practices

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destinationLink Text
www.headspace.com/meditationLearn more
www.headspace.com/mental-healthLearn more
organizations.headspace.com/?origin=homepageLearn more
www.headspace.com/cookie-policyLearn more
www.headspace.com/cookie-policyLearn more

Format your HTML in a way that enables crawlers to better understand your app’s content.

○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 are crawlable
●robots.txt is valid
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Send Feedback