Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
assets.adobedtm.com/ba6d3e7c167e/6bf3c6b5f665/launch-55e2612a4c37.min.js	3600.0 s	84.1 KiB
i.ytimg.com/vi_webp/21FE7_9DsBM/sddefault.webp	7200.0 s	17.7 KiB
static.doubleclick.net/instream/ad_status.js	900.0 s	494 B
www.gstatic.com/recaptcha/api2/logo_48.png	604800.0 s	2.3 KiB

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.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Est Savings
www.docker.com/app/themes/Ponyo/dist/fonts/ABCRepro-Medium.2e19b89f.woff2	95 ms
www.docker.com/app/themes/Ponyo/dist/fonts/Inter-SemiBold.4d56bb21.ttf	90 ms
www.docker.com/app/themes/Ponyo/dist/fonts/Inter-Regular.e89cb199.ttf	85 ms
www.docker.com/app/themes/Ponyo/dist/fonts/Inter-Bold.88fa7ae3.ttf	75 ms
www.docker.com/app/themes/Ponyo/dist/fonts/Inter-Medium.6dcbc9be.ttf	75 ms
www.docker.com/app/themes/Ponyo/dist/fonts/ABCRepro-Bold.fe39dde5.woff2	60 ms
fonts.gstatic.com/s/roboto/v48/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff2	35 ms
fonts.gstatic.com/s/roboto/v48/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff2	30 ms

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:95.129 source:map[type:text value:[unattributed]]] map[reflowTime:3.242 source:map[column:332 line:412 type:source-location url:https://www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js urlProvider:network]]]

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: article.wp-block-group > div.entry-content > div.text-align__left > video.background-video

path: 1,HTML,1,BODY,4,DIV,0,DIV,1,MAIN,0,ARTICLE,0,DIV,0,DIV,0,VIDEO

selector: article.wp-block-group > div.entry-content > div.text-align__left > video.background-video

snippet: <video class="background-video" src="/app/uploads/brand/background/DOCKER_hero_loop_opacity-reduction-25percent…" autoplay="" muted="" loop="" playsinline="">

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

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
cdn.cookielaw.org/scripttemplates/otSDKStub.js	0 B	780 ms
www.docker.com/wp/wp-includes/js/jquery/jquery-migrate.min.js?ver=3.4.1	5.8 KiB
www.docker.com/wp/wp-includes/js/jquery/jquery.min.js?ver=3.7.1	34.9 KiB	150 ms
/app/themes/Ponyo/dist/blocks/atoms/button/button-style.c...	1.8 KiB
www.docker.com/app/themes/Ponyo/dist/css/screen.css?ver=095f5c1f2a2197d8b78e	17.5 KiB	451 ms
/app/themes/Ponyo/dist/blocks/atoms/pill/pill-style.css?v...	638 B	150 ms

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.

	URL	Resource Size	Est Savings
gray `article.wp-block-group > div.entry-content > div.organism > img.background-image`	www.docker.com/app/uploads/brand/background/gray-1536x793.png	28.6 KiB	17.4 KiB

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

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

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.0 s

URL	Time Spent
docker.io/	1.0 s
www.docker.com/	0.0 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.

Diagnostics

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 3.1 s 441.8 KiB

URL	Transfer Size	Est Savings
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	361.8 KiB	177.0 KiB
www.docker.com/app/themes/Ponyo/dist/js/index.js?ver=c6fa09706ca007368240	235.2 KiB	124.1 KiB
www.googletagmanager.com/gtm.js?id=GTM-WL2QLG5	169.0 KiB	81.3 KiB
assets.adobedtm.com/ba6d3e7c167e/6bf3c6b5f665/launch-55e2612a4c37.min.js	67.9 KiB	36.0 KiB
www.docker.com/wp/wp-includes/js/jquery/jquery.min.js?ver=3.7.1	34.6 KiB	23.4 KiB

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
www.docker.com/	2.5 s	712 ms	27 ms
Unattributable	1.6 s	50 ms	0.0 ms
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	544 ms	367 ms	97 ms
www.docker.com/app/themes/Ponyo/dist/js/index.js?ver=c6fa09706ca007368240	537 ms	382 ms	77 ms
www.googletagmanager.com/gtm.js?id=GTM-WL2QLG5	302 ms	234 ms	45 ms
assets.adobedtm.com/ba6d3e7c167e/6bf3c6b5f665/launch-55e2612a4c37.min.js	234 ms	193 ms	23 ms
js-agent.newrelic.com/nr-spa-1.313.1.min.js	211 ms	181 ms	7.7 ms
www.docker.com/app/themes/Ponyo/dist/js/ponyo.js?ver=308081ab31238164a132	80 ms	30 ms	0.3 ms
www.youtube.com/s/player/218d9d92/www-widgetapi.vflset/www-widgetapi.js	65 ms	56 ms	4.4 ms
www.docker.com/wp/wp-includes/js/jquery/jquery.min.js?ver=3.7.1	50 ms	38 ms	9.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.

Category	Time Spent
Script Evaluation	2.3 s
Other	2.1 s
Style & Layout	1.0 s
Script Parsing & Compilation	316 ms
Rendering	281 ms
Parse HTML & CSS	140 ms
Garbage Collection	72 ms

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 12.4 KiB

URL	Transfer Size	Est Savings
www.docker.com/app/themes/Ponyo/dist/css/screen.css?ver=095f5c1f2a2197d8b78e	16.9 KiB	12.4 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.

URL	Transfer Size
www.docker.com/app/uploads/2025/11/homepage-mcp-connect-condensed-1.gif	26.5 MiB
/app/uploads/brand/background/DOCKER_hero_loop_opacity-re...	11.6 MiB
www.docker.com/app/uploads/2024/12/Promo-box-image_White-paper_FA.svg	2.0 MiB
www.docker.com/app/uploads/2025/11/dev-prod-flow.svg	487.2 KiB
www.youtube.com/s/player/218d9d92/player_embed_es6.vflset/en_US/base.js	435.8 KiB
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	362.4 KiB
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	361.9 KiB
www.docker.com/app/uploads/2025/11/desktop-containers-application.svg	296.0 KiB
www.docker.com/app/themes/Ponyo/dist/js/index.js?ver=c6fa09706ca007368240	235.7 KiB
www.docker.com/app/themes/Ponyo/dist/fonts/ABCRepro-Bold.fe39dde5.woff2	199.1 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL
header.site-header > div#docker-announcement-bar > div > img `header.site-header > div#docker-announcement-bar > div > img`	www.docker.com/app/uploads/2024/01/icon-new.svg

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

●Layout shift culprits

●Optimize DOM size

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoid long main-thread tasks 20 long tasks found

●Avoid non-composited animations 38 animated elements found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 90 ms

●Server Backend Latencies 240 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

○INP breakdown

○User Timing marks and measures

○Avoid large layout shifts

Accessibility

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

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
MCP `div.wp-block-ponyo-boone > div.wp-block-ponyo-tatiana > a.wp-block-ponyo-tab > div.tab-text`
Agents `div.wp-block-ponyo-boone > div.wp-block-ponyo-tatiana > a.wp-block-ponyo-tab > div.tab-text`
Containers `div.wp-block-ponyo-boone > div.wp-block-ponyo-tatiana > a.wp-block-ponyo-tab > div.tab-text`

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
Apache 2.0 freedom `div.wp-block-ponyo-erika > div.container > div.copy-container > h4.wp-block-ponyo-heading`
Five pillars of supply chain security `div.wp-block-ponyo-erika > div.container > div.copy-container > h4.wp-block-ponyo-heading`
Build once, run anywhere `div.wp-block-ponyo-erika > div.container > div.copy-container > h4.wp-block-ponyo-heading`

These are opportunities to improve keyboard navigation in your application.

Names and labels

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.wp-block-group > header.site-header > div.wp-block-group > a.logo `div.wp-block-group > header.site-header > div.wp-block-group > a.logo`
div.wp-block-ponyo-newsletter-social > ul.social-wrap > li > a `div.wp-block-ponyo-newsletter-social > ul.social-wrap > li > a`
div.wp-block-ponyo-newsletter-social > ul.social-wrap > li > a `div.wp-block-ponyo-newsletter-social > ul.social-wrap > li > a`
div.wp-block-ponyo-newsletter-social > ul.social-wrap > li > a `div.wp-block-ponyo-newsletter-social > ul.social-wrap > li > a`
div.wp-block-ponyo-newsletter-social > ul.social-wrap > li > a `div.wp-block-ponyo-newsletter-social > ul.social-wrap > li > a`
div.wp-block-ponyo-newsletter-social > ul.social-wrap > li > a `div.wp-block-ponyo-newsletter-social > ul.social-wrap > li > a`
div.wp-block-ponyo-newsletter-social > ul.social-wrap > li > a `div.wp-block-ponyo-newsletter-social > ul.social-wrap > li > 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.

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
Products Products Overview Docker Desktop Docker Hub Docker Scout Docker Build … `div.wp-block-ponyo-freddie > div.menu-container > div.wp-block-ponyo-faith > ul`
Features Command Line Interface IDE Extensions Container Runtime Docker Extensi… `div.wp-block-ponyo-freddie > div.menu-container > div.wp-block-ponyo-faith > ul`
Developers Documentation Getting Started Trainings Extensions SDK Community Ope… `div.wp-block-ponyo-freddie > div.menu-container > div.wp-block-ponyo-faith > ul`
Pricing Personal Pro Team Business Premium Support and TAM Pricing FAQ Contact … `div.wp-block-ponyo-freddie > div.menu-container > div.wp-block-ponyo-faith > ul`
Company About Us What is a Container Blog Why Docker Trust Customer Success Par… `div.wp-block-ponyo-freddie > div.menu-container > div.wp-block-ponyo-faith > ul`
Languages English 日本語 `div.wp-block-ponyo-freddie > div.menu-container > div.wp-block-ponyo-faith > ul`

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

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●ARIA attributes are used as specified for the element's role

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

●`<frame>` or `<iframe>` elements have a title

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

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

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

●`[lang]` attributes have a valid value

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

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

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

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

100

Best Practices

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
www.docker.com/app/themes/Ponyo/dist/js/index.js?ver=c6fa09706ca007368240

●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 browser errors logged to the console

●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

○Redirects HTTP traffic to HTTPS

○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

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`