Skip to content
https://www.waymo.com

Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

56

Performance

Insights

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

RequestCache TTLTransfer Size
/waymo-uploads/files/site-animations/homepage/waymo-one/i...3600.0 s153.9 KiB
connect.facebook.net/en_US/fbevents.js1200.0 s95.0 KiB
/PcUKcguPOVa4R918VZVNqw285bg6_v0Ehrkdq8C0_IbIbC9GQy8iWxp0...86400.0 s153.5 KiB
/waymo-uploads/files/site-animations/homepage/waymo-one/i...3600.0 s51.9 KiB
/waymo-uploads/files/site-animations/homepage/waymo-one/i...3600.0 s51.9 KiB
/waymo-uploads/files/site-animations/homepage/waymo-one/i...3600.0 s50.7 KiB
/waymo-uploads/files/site-animations/homepage/waymo-one/i...3600.0 s50.3 KiB
/waymo-uploads/files/site-animations/homepage/waymo-one/i...3600.0 s49.0 KiB
/waymo-uploads/files/site-animations/homepage/waymo-one/i...3600.0 s47.8 KiB
/waymo-uploads/files/site-animations/homepage/waymo-one/i...3600.0 s45.7 KiB
/waymo-uploads/files/site-animations/homepage/waymo-one/i...3600.0 s43.5 KiB
/signals/config/1244331133132125?v=2.9.291&r=stable&domai...1200.0 s37.1 KiB
/waymo-uploads/files/site-animations/homepage/waymo-one/i...3600.0 s40.5 KiB
/waymo-uploads/files/site-animations/homepage/waymo-one/i...3600.0 s38.4 KiB
/waymo-uploads/files/site-animations/homepage/waymo-one/i...3600.0 s35.0 KiB
/waymo-uploads/files/site-animations/homepage/waymo-one/i...3600.0 s33.0 KiB
/waymo-uploads/files/site-animations/homepage/waymo-one/i...3600.0 s27.3 KiB
/waymo-uploads/files/site-animations/homepage/waymo-one/i...3600.0 s27.0 KiB
www.redditstatic.com/ads/pixel.js60.0 s19.0 KiB
/waymo-uploads/files/site-animations/homepage/waymo-one/i...3600.0 s21.9 KiB
www.google-analytics.com/analytics.js7200.0 s20.9 KiB
/waymo-uploads/files/site-animations/homepage/waymo-one/i...3600.0 s18.9 KiB
/waymo-uploads/files/site-animations/homepage/waymo-one/i...3600.0 s18.2 KiB
/waymo-uploads/files/site-animations/homepage/waymo-one/i...3600.0 s16.9 KiB
/signals/config/1148687776906865?v=2.9.291&r=stable&domai...1200.0 s14.3 KiB
/signals/config/1120830352611280?v=2.9.291&r=stable&domai...1200.0 s14.2 KiB
/waymo-uploads/files/site-animations/homepage/waymo-one/i...3600.0 s15.4 KiB
js.adsrvr.org/up_loader.1.1.0.js0.0 ms11.2 KiB
c.amazon-adsystem.com/aat/amzn.js0.0 ms8.9 KiB
/waymo-uploads/files/site-animations/homepage/waymo-one/i...3600.0 s10.3 KiB
snap.licdn.com/li.lms-analytics/insight.min.js86400.0 s18.7 KiB
s.yimg.com/wi/ytc.js0.0 ms7.2 KiB
/waymo-uploads/files/site-animations/homepage/waymo-one/i...3600.0 s5.3 KiB
acdn.adnxs.com/dmp/up/pixie.js86402.0 s9.2 KiB
waymo.com/v2/static/images/footer/icon-personal-info.svg36.0 s1.6 KiB
js.adsrvr.org/universal_pixel.js0.0 ms958 B
/waymo-uploads/files/site-animations/homepage/waymo-one/i...3600.0 s1.1 KiB
/rp.gif?ts=1775593316271&id=a2_ghy9964q38pu&event=PageVis...0.0 ms637 B
js.adsrvr.org/universal_pixel.js0.0 ms465 B
js.adsrvr.org/universal_pixel.js0.0 ms465 B
/collect?v=2&fmt=js&pid=8241124&time=1775593316845&li_ads...0.0 ms451 B
/config/com/a9508252-c794-4ce0-814f-0467680b0049.js?v=3.5...0.0 ms449 B
waymo.com/v2/static/images/footer/icon-x.svg36.0 s309 B
match.adsrvr.org/track/cmb/rubicon?gdpr=00.0 ms254 B
/tr/?id=1244331133132125&ev=PageView&dl=https%3A%2F%2Fway...0.0 ms18 B
/tr/?id=1148687776906865&ev=PageView&dl=https%3A%2F%2Fway...0.0 ms16 B
/tr/?id=1120830352611280&ev=PageView&dl=https%3A%2F%2Fway...0.0 ms16 B

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:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:14.396 source:map[column:2819 line:0 type:source-location url:https://waymo.com/assets/CKET3U5t.min.js urlProvider:network]] map[reflowTime:0.051 source:map[column:248 line:0 type:source-location url:https://waymo.com/assets/719Lwyca.min.js urlProvider:network]] map[reflowTime:0.414 source:map[column:1403 line:0 type:source-location url:https://waymo.com/assets/719Lwyca.min.js urlProvider:network]] map[reflowTime:27.767 source:map[column:907 line:0 type:source-location url:https://waymo.com/assets/chunks/CiUjhGv7.min.js urlProvider:network]] map[reflowTime:2.766 source:map[column:1793 line:0 type:source-location url:https://waymo.com/assets/NLvoUazr.min.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
div._asset2_1ayun_406 > w-media.ready > w-autoplay-guard > video._video_154ol_2 div._asset2_1ayun_406 > w-media.ready > w-autoplay-guard > video._video_154ol_2
/PcUKcguPOVa4R918VZVNqw285bg6_v0Ehrkdq8C0_IbIbC9GQy8iWxp0...153.1 KiB136.1 KiB
div._background_1iyry_651 > div._image_1n6as_1 > picture > img div._background_1iyry_651 > div._image_1n6as_1 > picture > img
/D4FEZ8TQ1vOoI2-302a8B7ey0fZ1ZQZ4XR5s3XH9uwurJ1tU0tgdt0F-...153.0 KiB114.8 KiB
w-media > div._image_19ute_13 > picture._picture_1yfl2_2 > img._image_1yfl2_5 w-media > div._image_19ute_13 > picture._picture_1yfl2_2 > img._image_1yfl2_5
/oZFmHGmLpZeiiGyW7C-EiQCC_R3rqXtqPF7YtbYy1HzgJ-AC6DcUOYxs...103.7 KiB81.4 KiB
div._background_1iyry_651 > div._image_1n6as_1 > picture > img div._background_1iyry_651 > div._image_1n6as_1 > picture > img
/CF60prp1hlSerUju8maSJVuYG1wVvc0Kj99CLDBQVb75klEXJklqHXgc...75.9 KiB70.3 KiB
div._background_1iyry_651 > div._image_1n6as_1 > picture > img div._background_1iyry_651 > div._image_1n6as_1 > picture > img
/v-nEn2qP2bc7jpXSbAG2YRQdi8JCo8vax4HPO9qxkjxuITxPAKinVAXd...61.1 KiB52.3 KiB
div._background_1iyry_651 > div._image_1n6as_1 > picture > img div._background_1iyry_651 > div._image_1n6as_1 > picture > img
/zRvkZADe5BMf6S5Gqv27V2H7DSTTY5WR6CRZfMcplWDMoMcodOU-BOgT...39.6 KiB29.6 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-VIDEO
nodeLabel: div._asset2_1ayun_406 > w-media.ready > w-autoplay-guard > video._video_154ol_2
path: 1,HTML,1,BODY,0,DIV,1,MAIN,2,DIV,0,SECTION,0,W-INVIEW,0,SECTION,3,DIV,0,W-MEDIA,0,W-AUTOPLAY-GUARD,0,VIDEO
selector: div._asset2_1ayun_406 > w-media.ready > w-autoplay-guard > video._video_154ol_2
snippet: <video muted="" playsinline="" data-maybe-autoplay="" loop="" preload="auto" poster="//lh3.googleusercontent.com/PcUKcguPOVa4R918VZVNqw285bg6_v0Ehrkdq8C0_IbIbC…" class="_video_154ol_2 _videoDesktop_19ute_12" autoplay="true">

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates

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

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: 1.3 s
URLTime Spent
www.waymo.com/1.3 s
waymo.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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 80 ms 48.4 KiB
URLTransfer SizeEst Savings
waymo.com/assets/5Njq7nax.css48.4 KiB48.4 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

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.5 s
Other1.0 s
Script Parsing & Compilation275 ms
Style & Layout270 ms
Parse HTML & CSS69 ms
Rendering66 ms
Garbage Collection30 ms

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
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●User Timing marks and measures 11 user timings
●Avoid long main-thread tasks 10 long tasks found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 70 ms
●Server Backend Latencies 1,150 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 510 ms
○INP breakdown
○Avoid non-composited animations
○Avoid large layout shifts
90

Accessibility

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

ARIA

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

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
Search Waymo Quick links Get a ride Find a dream job Contact us div#P0-0-main-nav > ul._navLinks_1iyry_425 > li._navLinkContainer_1iyry_158 > div#P0-0-sub-nav-6

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
Be one of the first. Download Waymo today. figure._lottie_16rnb_3 > 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.

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
Eva, San Francisco div._tabpanels_1rli4_103 > div#P0-0-tabpanel-0 > blockquote._blockquote_1rli4_157 > cite._cite_1rli4_183

These are opportunities to improve the legibility of your content.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
●`[role]`s are contained by their required parent element
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●Select elements have associated label elements.
●ARIA attributes are used as specified for the element's role
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
○`[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 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
○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
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○Elements with visible text labels have matching accessible names.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
73

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.
Fledge
AttributionReporting

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
Failed to find a valid digest in the 'integrity' attribute for resource 'https://acdn.adnxs.com/dmp/up/pixie.js' with computed SHA-384 integrity 'CSc0h3j4hdCDJdoU/2/9g3GappKfz/jx3Uu5ZYgF+qOXX6tNHOELRbzrpOHwcoiL'. The resource has been blocked.
Failed to find a valid digest in the 'integrity' attribute for resource 'https://s.yimg.com/wi/ytc.js' with computed SHA-384 integrity 'oPe+NHgw5fktEtQzaS/6npkdcwZ5kLkTnXtN1bJlENz8+KH22CmafKwhJl0h0+/L'. The resource has been blocked.

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Issue type
Content security policy
●Uses HTTPS
●Avoids third-party cookies
●Allows users to paste into input fields
●Avoids requesting the geolocation permission on page load
●Avoids requesting the notification permission on page load
●Displays images with correct aspect ratio
●Serves images with appropriate resolution
●Page has the HTML doctype
●Properly defines charset
●Ensure CSP is effective against XSS attacks
●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
○Use a strong HSTS policy
○Mitigate clickjacking with XFO or CSP
100

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

○Structured data is valid
●Page isn’t blocked from indexing
●Document has a `<title>` element
●Document has a meta description
●Page has successful HTTP status code
●Links have descriptive text
●Links are crawlable
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`
○robots.txt is valid

Send Feedback