C — https://www.spacex.com | BeaverCheck Audit

Site Health

Score: 75 / 100

Based on 8 categories, 0 sections

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.

Top Priorities (5)

'unsafe-eval' found in script source

Security › Content Security Policy

'unsafe-inline' found in script source

Security › Content Security Policy

Page weighs 11.6 MB (10.7 MB transferred)

Performance › Page Weight Budget

1 button(s) with no accessible text

Accessibility › Link & Button Quality

1 link(s) with no accessible text

Accessibility › Link & Button Quality

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.spacex.com)](https://beavercheck.com/results/cdb94421-0ad2-761f-055e-09408467a404)

HTML

<a href="https://beavercheck.com/results/cdb94421-0ad2-761f-055e-09408467a404"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.spacex.com" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fwww.spacex.com

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

Best Practices

SEO

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.

2.11 s

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

4.61 s

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

279 ms

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

0.001

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

2.27 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

5.21 s

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.

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

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

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

Request	Cache TTL	Transfer Size
www.spacex.com/vendor.ca6bf32c26e75d4a.js	600.0 s	167.3 KiB
/cms-assets/assets/crew_12_MOBILE_template1_f0071d661e.jpg	43200.0 s	153.2 KiB
/cms-assets/assets/Leading_Launch_Service_Mobile_02_41fde...	43200.0 s	107.1 KiB
/cms-assets/assets/Revolutionizing_Space_Tech_Mobile_4509...	43200.0 s	102.9 KiB
/cms-assets/assets/Delivering_Highspeed_Mobile_86f0698604...	43200.0 s	93.2 KiB
sxcontent9668.azureedge.us/cms-assets/assets/Mobile_v4_HB_e1d2eda88f.mp4	43200.0 s	70.8 KiB
/cms-assets/assets/Advancing_Human_Spaceflight_Mobile_af2...	43200.0 s	57.1 KiB
sxcontent9668.azureedge.us/cms-assets/assets/SLC_4_E_600x600_24dd9e969c.jpg	43200.0 s	48.8 KiB
www.spacex.com/polyfills.08b6611321d68f0c.js	600.0 s	22.8 KiB
www.spacex.com/D-DIN-Bold.9a5ce67e997fd030.woff2	600.0 s	22.5 KiB
www.spacex.com/D-DIN.e58c68e58b09fc0e.woff2	600.0 s	20.4 KiB
sxcontent9668.azureedge.us/cms-assets/assets/Mars_Mobile_9924bba7c2.jpg	43200.0 s	33.1 KiB
www.spacex.com/main.f5e02a8ad9f09a96.js	600.0 s	17.8 KiB
/cms-assets/assets/Starlink_12_10_20250428_Deploy_website...	43200.0 s	30.6 KiB
/cms-assets/assets/Leading_Launch_Service_Mobile_02email_...	43200.0 s	22.8 KiB
www.spacex.com/common.9dc1d69e3201c9a1.js	600.0 s	8.0 KiB
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...	86400.0 s	10.7 KiB
www.spacex.com/2248.1c995e45edcf7105.js	600.0 s	3.7 KiB
www.spacex.com/8119.f4e5c33ecc356475.js	600.0 s	3.4 KiB
www.spacex.com/styles.ef5ce7a88eff8dae.css	600.0 s	3.0 KiB
www.spacex.com/runtime.2c0f56a135f2b763.js	600.0 s	2.6 KiB
www.spacex.com/7753.5efeb53f2f091644.js	600.0 s	597 B
www.spacex.com/environment.js	600.0 s	409 B
/cms-assets/assets/Leading_Launch_Service_Mobile_02email_...	43200.0 s	0 B
/cms-assets/assets/Starlink_12_10_20250428_Deploy_website...	43200.0 s	0 B
sxcontent9668.azureedge.us/cms-assets/assets/Mobile_v4_HB_e1d2eda88f.mp4	43200.0 s	0 B
/cms-assets/assets/Starlink_12_10_20250428_Deploy_website...	43200.0 s	0 B
/cms-assets/assets/Leading_Launch_Service_Mobile_02email_...	43200.0 s	0 B
sxcontent9668.azureedge.us/cms-assets/assets/Mobile_v4_HB_e1d2eda88f.mp4	43200.0 s	0 B

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

URL	Est Savings
www.spacex.com/D-DIN.e58c68e58b09fc0e.woff2	40 ms
www.spacex.com/D-DIN-Bold.9a5ce67e997fd030.woff2	25 ms

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]

items: [map[duration:97.743 label:Time to first byte subpart:timeToFirstByte] map[duration:1153.699 label:Resource load delay subpart:resourceLoadDelay] map[duration:1251.22 label:Resource load duration subpart:resourceLoadDuration] map[duration:13.199 label:Element render delay subpart:elementRenderDelay]]

lhId: page-0-VIDEO

nodeLabel: spx-section > div#section-0 > span.video-wrapper > video

path: 1,HTML,1,BODY,0,APP-ROOT,0,DIV,0,DIV,0,DIV,2,HOME-PAGE,0,DIV,2,DIV,0,SPX-SECTION,0,DIV,2,SPAN,0,VIDEO

selector: spx-section > div#section-0 > span.video-wrapper > video

snippet: <video _ngcontent-tpl-c52="" aria-describedby="video-description" aria-labelledby="video-description" aria-hidden="true" autoplay="" loop="" playsinline="" preload="auto" poster="https://sxcontent9668.azureedge.us/cms-assets/assets/Mars_Mobile_9924bba7c…">

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

lhId: page-0-VIDEO

nodeLabel: spx-section > div#section-0 > span.video-wrapper > video

path: 1,HTML,1,BODY,0,APP-ROOT,0,DIV,0,DIV,0,DIV,2,HOME-PAGE,0,DIV,2,DIV,0,SPX-SECTION,0,DIV,2,SPAN,0,VIDEO

selector: spx-section > div#section-0 > span.video-wrapper > video

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.

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

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

	URL	Resource Size	Est Savings
upcoming-launch-card > div.card > div.card-content > img `upcoming-launch-card > div.card > div.card-content > img`	/cms-assets/assets/crew_12_MOBILE_template1_f0071d661e.jpg	152.7 KiB	150.8 KiB
upcoming-launch-card > div.card > div.card-content > img `upcoming-launch-card > div.card > div.card-content > img`	sxcontent9668.azureedge.us/cms-assets/assets/SLC_4_E_600x600_24dd9e969c.jpg	48.4 KiB	46.7 KiB
spx-section > div#section-2 > span.video-wrapper > video `spx-section > div#section-2 > span.video-wrapper > video`	/cms-assets/assets/Leading_Launch_Service_Mobile_02_41fde...	106.6 KiB	9.5 KiB
spx-section > div#section-1 > span.image-wrapper > img#background-img `spx-section > div#section-1 > span.image-wrapper > img#background-img`	/cms-assets/assets/Revolutionizing_Space_Tech_Mobile_4509...	102.4 KiB	9.1 KiB
spx-section > div#section-5 > span.video-wrapper > video `spx-section > div#section-5 > span.video-wrapper > video`	/cms-assets/assets/Delivering_Highspeed_Mobile_86f0698604...	92.8 KiB	8.3 KiB
spx-section > div#section-4 > span.image-wrapper > img#background-img `spx-section > div#section-4 > span.image-wrapper > img#background-img`	/cms-assets/assets/Advancing_Human_Spaceflight_Mobile_af2...	56.7 KiB	5.0 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.

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.

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.

Estimated savings: 450 ms 94.3 KiB

URL	Transfer Size	Est Savings
www.spacex.com/vendor.ca6bf32c26e75d4a.js	167.1 KiB	94.3 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

URL	Transfer Size
/cms-assets/assets/Starlink_12_10_20250428_Deploy_website...	5.5 MiB
sxcontent9668.azureedge.us/cms-assets/assets/Mobile_v4_HB_e1d2eda88f.mp4	3.1 MiB
/cms-assets/assets/Leading_Launch_Service_Mobile_02email_...	1.0 MiB
www.spacex.com/vendor.ca6bf32c26e75d4a.js	167.3 KiB
/cms-assets/assets/crew_12_MOBILE_template1_f0071d661e.jpg	153.2 KiB
/cms-assets/assets/Leading_Launch_Service_Mobile_02_41fde...	107.1 KiB
/cms-assets/assets/Revolutionizing_Space_Tech_Mobile_4509...	102.9 KiB
/cms-assets/assets/Leading_Launch_Service_Mobile_02email_...	94.9 KiB
/cms-assets/assets/Delivering_Highspeed_Mobile_86f0698604...	93.2 KiB
sxcontent9668.azureedge.us/cms-assets/assets/Mobile_v4_HB_e1d2eda88f.mp4	70.8 KiB

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

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Forced reflow

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●User Timing marks and measures 42 user timings

●JavaScript execution time 0.7 s

●Minimizes main-thread work 1.5 s

●Avoid long main-thread tasks 5 long tasks found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 150 ms

●Server Backend Latencies 130 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

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

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○Avoid non-composited animations

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

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.

Failing Elements
footer > div.footer > a.social > button `footer > div.footer > a.social > button`

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Failing Elements
upcoming-launch-card > div.card > div.card-content > img `upcoming-launch-card > div.card > div.card-content > img`
upcoming-launch-card > div.card > div.card-content > img `upcoming-launch-card > div.card > div.card-content > img`
spx-section > div#section-1 > span.image-wrapper > img#background-img `spx-section > div#section-1 > span.image-wrapper > img#background-img`
spx-section > div#section-4 > span.image-wrapper > img#background-img `spx-section > div#section-4 > span.image-wrapper > img#background-img`

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.

Failing Elements
nav > div.top-bar > div.spacex-logo > a `nav > div.top-bar > div.spacex-logo > a`

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.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Failing Elements
html `html`

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

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

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

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

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

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Deprecated ARIA roles were not used

●ARIA IDs are unique

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

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

○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

○Form elements have associated labels

○Links are distinguishable without relying on color.

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

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

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

○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

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

	URL	Aspect Ratio (Displayed)	Aspect Ratio (Actual)
upcoming-launch-card > div.card > div.card-content > img `upcoming-launch-card > div.card > div.card-content > img`	/cms-assets/assets/crew_12_MOBILE_template1_f0071d661e.jpg	64 x 64 (1.00)	840 x 1200 (0.70)

General

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

URL
www.spacex.com/vendor.ca6bf32c26e75d4a.js

●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

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Mitigate clickjacking with XFO or CSP

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.

Link destination	Link Text
www.spacex.com/vehicles/starship	LEARN MORE

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Failing Elements
upcoming-launch-card > div.card > div.card-content > img `upcoming-launch-card > div.card > div.card-content > img`
upcoming-launch-card > div.card > div.card-content > img `upcoming-launch-card > div.card > div.card-content > img`
spx-section > div#section-1 > span.image-wrapper > img#background-img `spx-section > div#section-1 > span.image-wrapper > img#background-img`
spx-section > div#section-4 > span.image-wrapper > img#background-img `spx-section > div#section-4 > span.image-wrapper > img#background-img`

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

●Document has a valid `hreflang`

○robots.txt is valid

○Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

Accessibility

Best Practices

SEO

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.

487 ms

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

1.36 s

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

594 ms

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

0.001

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

672 ms

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

1.36 s

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.

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

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

Request	Cache TTL	Transfer Size
/cms-assets/assets/Space_X_Falcon_Heavy_UAS_Landing_DESKT...	43200.0 s	2.6 MiB
/cms-assets/assets/Leading_Launch_Service_Desktop_06a98ac...	43200.0 s	450.9 KiB
/cms-assets/assets/Revolutionizing_Space_Tech_Desktop_ec6...	43200.0 s	344.3 KiB
www.spacex.com/vendor.ca6bf32c26e75d4a.js	600.0 s	167.3 KiB
/cms-assets/assets/Delivering_Highspeed_Desktop_d50314640...	43200.0 s	241.9 KiB
/cms-assets/assets/Advancing_Human_Spaceflight_Desktop_61...	43200.0 s	177.7 KiB
/cms-assets/assets/crew_12_MOBILE_template1_f0071d661e.jpg	43200.0 s	153.2 KiB
sxcontent9668.azureedge.us/cms-assets/assets/SLC_4_E_600x600_24dd9e969c.jpg	43200.0 s	48.8 KiB
www.spacex.com/polyfills.08b6611321d68f0c.js	600.0 s	22.8 KiB
www.spacex.com/D-DIN-Bold.9a5ce67e997fd030.woff2	600.0 s	22.5 KiB
www.spacex.com/D-DIN.e58c68e58b09fc0e.woff2	600.0 s	21.2 KiB
sxcontent9668.azureedge.us/cms-assets/assets/Mars_Web_8fafe15a48.jpg	43200.0 s	33.0 KiB
www.spacex.com/main.f5e02a8ad9f09a96.js	600.0 s	17.8 KiB
/cms-assets/assets/Starlink_12_10_20250428_Deploy_website...	43200.0 s	18.7 KiB
www.spacex.com/common.9dc1d69e3201c9a1.js	600.0 s	8.0 KiB
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...	86400.0 s	10.7 KiB
www.spacex.com/2248.1c995e45edcf7105.js	600.0 s	3.7 KiB
/cms-assets/assets/Space_X_Falcon_Heavy_UAS_Landing_DESKT...	43200.0 s	6.8 KiB
www.spacex.com/8119.f4e5c33ecc356475.js	600.0 s	3.4 KiB
www.spacex.com/runtime.2c0f56a135f2b763.js	600.0 s	2.6 KiB
www.spacex.com/styles.ef5ce7a88eff8dae.css	600.0 s	2.3 KiB
www.spacex.com/7753.5efeb53f2f091644.js	600.0 s	632 B
www.spacex.com/environment.js	600.0 s	438 B
/cms-assets/assets/Space_X_Falcon_Heavy_UAS_Landing_DESKT...	43200.0 s	0 B
/cms-assets/assets/Starlink_12_10_20250428_Deploy_website...	43200.0 s	0 B
sxcontent9668.azureedge.us/cms-assets/assets/Mars_Rotation_Web_HB_d96299f9de.mp4	43200.0 s	0 B
/cms-assets/assets/Starlink_12_10_20250428_Deploy_website...	43200.0 s	0 B

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

URL	Est Savings
www.spacex.com/D-DIN.e58c68e58b09fc0e.woff2	30 ms
www.spacex.com/D-DIN-Bold.9a5ce67e997fd030.woff2	25 ms

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.

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

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

	URL	Resource Size	Est Savings
spx-section > div#section-2 > span.video-wrapper > video `spx-section > div#section-2 > span.video-wrapper > video`	/cms-assets/assets/Leading_Launch_Service_Desktop_06a98ac...	450.0 KiB	212.0 KiB
spx-section > div#section-1 > span.image-wrapper > img#background-img `spx-section > div#section-1 > span.image-wrapper > img#background-img`	/cms-assets/assets/Revolutionizing_Space_Tech_Desktop_ec6...	343.6 KiB	161.9 KiB
spx-section > div#section-5 > span.video-wrapper > video `spx-section > div#section-5 > span.video-wrapper > video`	/cms-assets/assets/Delivering_Highspeed_Desktop_d50314640...	241.2 KiB	113.7 KiB
spx-section > div#section-4 > span.image-wrapper > img#background-img `spx-section > div#section-4 > span.image-wrapper > img#background-img`	/cms-assets/assets/Advancing_Human_Spaceflight_Desktop_61...	177.1 KiB	83.4 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.

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.

Estimated savings: 80 ms 94.3 KiB

URL	Transfer Size	Est Savings
www.spacex.com/vendor.ca6bf32c26e75d4a.js	167.2 KiB	94.3 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

URL	Transfer Size
/cms-assets/assets/Starlink_12_10_20250428_Deploy_website...	5.6 MiB
sxcontent9668.azureedge.us/cms-assets/assets/Mars_Rotation_Web_HB_d96299f9de.mp4	5.2 MiB
/cms-assets/assets/Space_X_Falcon_Heavy_UAS_Landing_DESKT...	2.6 MiB
/cms-assets/assets/Leading_Launch_Service_Desktop_06a98ac...	450.9 KiB
/cms-assets/assets/Revolutionizing_Space_Tech_Desktop_ec6...	344.3 KiB
/cms-assets/assets/Delivering_Highspeed_Desktop_d50314640...	241.9 KiB
/cms-assets/assets/Advancing_Human_Spaceflight_Desktop_61...	177.7 KiB
www.spacex.com/vendor.ca6bf32c26e75d4a.js	167.3 KiB
/cms-assets/assets/crew_12_MOBILE_template1_f0071d661e.jpg	153.2 KiB
sxcontent9668.azureedge.us/cms-assets/assets/SLC_4_E_600x600_24dd9e969c.jpg	48.8 KiB

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

●Time to Interactive 1.4 s

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Forced reflow

●LCP breakdown

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●User Timing marks and measures 42 user timings

●JavaScript execution time 0.2 s

●Minimizes main-thread work 1.3 s

●Avoid long main-thread tasks 2 long tasks found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 130 ms

●Server Backend Latencies 170 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

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

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

○Avoid non-composited animations

Accessibility

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.

Failing Elements
footer > div.footer > a.social > button `footer > div.footer > a.social > button`

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Failing Elements
spx-section > div#section-1 > span.image-wrapper > img#background-img `spx-section > div#section-1 > span.image-wrapper > img#background-img`
spx-section > div#section-4 > span.image-wrapper > img#background-img `spx-section > div#section-4 > span.image-wrapper > img#background-img`

Failing Elements
nav > div.top-bar > div.spacex-logo > a `nav > div.top-bar > div.spacex-logo > a`

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

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

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

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

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

●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

●ARIA IDs are unique

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

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

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

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

○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

○Form elements have associated labels

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

○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

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

	URL	Aspect Ratio (Displayed)	Aspect Ratio (Actual)
upcoming-launch-card > div.card > div.card-content > img `upcoming-launch-card > div.card > div.card-content > img`	/cms-assets/assets/crew_12_MOBILE_template1_f0071d661e.jpg	64 x 64 (1.00)	840 x 1200 (0.70)

General

URL
www.spacex.com/vendor.ca6bf32c26e75d4a.js

●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

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Mitigate clickjacking with XFO or CSP

SEO

Content Best Practices

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

Link destination	Link Text
www.spacex.com/vehicles/starship	LEARN MORE

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Failing Elements
spx-section > div#section-1 > span.image-wrapper > img#background-img `spx-section > div#section-1 > span.image-wrapper > img#background-img`
spx-section > div#section-4 > span.image-wrapper > img#background-img `spx-section > div#section-4 > span.image-wrapper > img#background-img`

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

●Document has a valid `hreflang`

○robots.txt is valid

○Document has a valid `rel=canonical`

Browse & Analyze

Learn

Results for https://www.spacex.com

Site Health

Top Priorities (5)

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Names and labels

Best practices

Best Practices

User Experience

General

SEO

Content Best Practices

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Names and labels

Best Practices

User Experience

General

SEO

Content Best Practices

Keyboard Shortcuts