Lighthouse Desktop

· 0 checks — Desktop 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
/api-www/global-elements/global-header/v1/assets/globalhe...	247.0 s	161.1 KiB
/v/itunes/home/l/images/overview/screen_podcasts__di6468i...	953.0 s	132.8 KiB
/v/itunes/home/l/images/overview/screen_appletv__gd3vm2df...	953.0 s	129.1 KiB
www.apple.com/metrics/ac-analytics/2.29.1/scripts/ac-analytics.js	150.0 s	102.1 KiB
/v/itunes/home/l/images/overview/screen_new_mix__cb9y8qvs...	953.0 s	110.8 KiB
www.apple.com/wss/fonts/SF-Pro-Text/v2/sf-pro-text_semibold.woff2	689.0 s	107.9 KiB
www.apple.com/wss/fonts/SF-Pro-Display/v2/sf-pro-display_semibold.woff2	785.0 s	107.8 KiB
www.apple.com/wss/fonts/SF-Pro-Text/v2/sf-pro-text_bold.woff2	1345.0 s	106.8 KiB
www.apple.com/wss/fonts/SF-Pro-Text/v2/sf-pro-text_light.woff2	1642.0 s	107.1 KiB
www.apple.com/wss/fonts/SF-Pro-Text/v2/sf-pro-text_regular.woff2	745.0 s	97.6 KiB
www.apple.com/wss/fonts/SF-Pro-Display/v2/sf-pro-display_regular.woff2	1822.0 s	96.3 KiB
www.apple.com/wss/fonts/SF-Pro-Text/v2/sf-pro-text_semibold-italic.woff2	1327.0 s	72.9 KiB
www.apple.com/ac/localeswitcher/4/en_US/scripts/localeswitcher.built.js	50.0 s	55.6 KiB
/v/itunes/home/l/images/overview/mbair_itunes__bkf9ksiikx...	953.0 s	53.3 KiB
www.apple.com/api-www/global-elements/global-header/v1/assets/globalheader.css	99.0 s	15.5 KiB
www.apple.com/v/itunes/home/l/built/scripts/head.built.js	446.0 s	13.3 KiB
www.apple.com/wss/fonts/SF-Pro-Icons/v1/SFProIcons_regular.woff	2451.0 s	10.8 KiB
www.apple.com/wss/fonts/SF-Pro-Icons/v1/SFProIcons_light.woff	2711.0 s	10.9 KiB
www.apple.com/ac/localnav/9/styles/ac-localnav.built.css	46.0 s	8.2 KiB
www.apple.com/wss/fonts/SF-Pro-Icons/v1/SFProIcons_semibold.woff	1741.0 s	9.4 KiB
www.apple.com/v/itunes/home/l/built/styles/main.built.css	447.0 s	8.5 KiB
www.apple.com/ac/globalfooter/8/en_US/styles/ac-globalfooter.built.css	138.0 s	7.1 KiB
www.apple.com/v/itunes/home/l/built/scripts/main.built.js	120.0 s	6.1 KiB
www.apple.com/metrics/data-relay/1.2.0/scripts/data-relay.js	269.0 s	5.8 KiB
www.apple.com/ac/localeswitcher/4/es_ES/styles/localeswitcher.built.css	265.0 s	5.3 KiB
www.apple.com/v/itunes/home/l/built/styles/overview.built.css	446.0 s	4.1 KiB
www.apple.com/wss/fonts?families=SF+Pro,v2\|SF+Pro+Icons,v1	2888.0 s	1.8 KiB
/ac/globalfooter/8/en_US/assets/ac-footer/breadcrumbs/app...	343.0 s	1.4 KiB
/ac/globalfooter/8/en_US/assets/ac-footer/breadcrumbs/sep...	141.0 s	996 B
www.apple.com/metrics/data-relay/1.2.0/scripts/auto-relay.js	99.0 s	937 B
www.apple.com/metrics/ac-analytics/2.29.1/scripts/auto-init.js	244.0 s	850 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.

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.apple.com/wss/fonts/SF-Pro-Text/v2/sf-pro-text_regular.woff2	45 ms
www.apple.com/wss/fonts/SF-Pro-Icons/v1/SFProIcons_light.woff	40 ms
www.apple.com/wss/fonts/SF-Pro-Text/v2/sf-pro-text_light.woff2	40 ms
www.apple.com/wss/fonts/SF-Pro-Display/v2/sf-pro-display_regular.woff2	35 ms
www.apple.com/wss/fonts/SF-Pro-Text/v2/sf-pro-text_semibold-italic.woff2	35 ms
www.apple.com/wss/fonts/SF-Pro-Icons/v1/SFProIcons_semibold.woff	35 ms
www.apple.com/wss/fonts/SF-Pro-Text/v2/sf-pro-text_bold.woff2	25 ms
www.apple.com/wss/fonts/SF-Pro-Icons/v1/SFProIcons_regular.woff	20 ms
www.apple.com/wss/fonts/SF-Pro-Display/v2/sf-pro-display_semibold.woff2	10 ms
www.apple.com/wss/fonts/SF-Pro-Text/v2/sf-pro-text_semibold.woff2	5.0 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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:15.926 source:map[column:2090 line:16 type:source-location url:https://www.apple.com/api-www/global-elements/global-header/v1/assets/globalheader.umd.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:9.437 source:map[column:72432 line:0 type:source-location url:https://www.apple.com/api-www/global-elements/global-header/v1/assets/globalheader.umd.js urlProvider:network]] map[reflowTime:20.653 source:map[column:42696 line:0 type:source-location url:https://www.apple.com/api-www/global-elements/global-header/v1/assets/globalheader.umd.js urlProvider:network]]]

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.

title: Preconnected origins

value: no origins were preconnected

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

value: No additional origins are good candidates for preconnecting

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
www.apple.com/wss/fonts?families=SF+Pro,v2\|SF+Pro+Icons,v1	1.8 KiB
/api-www/global-elements/global-header/v1/assets/globalhe...	161.1 KiB	120 ms
www.apple.com/metrics/data-relay/1.2.0/scripts/auto-relay.js	937 B
www.apple.com/metrics/data-relay/1.2.0/scripts/data-relay.js	5.8 KiB
www.apple.com/ac/localnav/9/styles/ac-localnav.built.css	8.2 KiB
www.apple.com/v/itunes/home/l/built/scripts/head.built.js	13.3 KiB
www.apple.com/api-www/global-elements/global-header/v1/assets/globalheader.css	15.5 KiB
www.apple.com/v/itunes/home/l/built/scripts/main.built.js	6.1 KiB
www.apple.com/ac/globalfooter/8/en_US/scripts/ac-globalfooter.built.js	3.8 KiB
www.apple.com/v/itunes/home/l/built/styles/main.built.css	8.5 KiB
www.apple.com/metrics/ac-analytics/2.29.1/scripts/auto-init.js	850 B
www.apple.com/v/itunes/home/l/built/styles/overview.built.css	4.1 KiB
www.apple.com/ac/globalfooter/8/en_US/styles/ac-globalfooter.built.css	7.1 KiB

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
div.section-content > div.section-podcasts > div.hw-lockup > figure.screen `div.section-content > div.section-podcasts > div.hw-lockup > figure.screen`	/v/itunes/home/l/images/overview/screen_podcasts__di6468i...	131.9 KiB	70.8 KiB
div.section-content > div.section-tv > div.hw-lockup > figure.screen `div.section-content > div.section-tv > div.hw-lockup > figure.screen`	/v/itunes/home/l/images/overview/screen_appletv__gd3vm2df...	128.3 KiB	67.2 KiB
div.section-content > div.section-music > div.hw-lockup > figure.screen `div.section-content > div.section-music > div.hw-lockup > figure.screen`	/v/itunes/home/l/images/overview/screen_new_mix__cb9y8qvs...	110.0 KiB	48.9 KiB

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

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: 80 ms 97.8 KiB

URL	Transfer Size	Est Savings
/api-www/global-elements/global-header/v1/assets/globalhe...	160.2 KiB	56.7 KiB
www.apple.com/metrics/ac-analytics/2.29.1/scripts/ac-analytics.js	101.3 KiB	41.0 KiB

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

URL	Transfer Size	Est Savings
www.apple.com/api-www/global-elements/global-header/v1/assets/globalheader.css	14.8 KiB	13.1 KiB

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

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: 392 ms

URL	Time Spent
itunes.apple.com/	392 ms
www.apple.com/itunes/	0.0 ms

●Time to Interactive 1.8 s

●Layout shift culprits

●Optimize DOM size

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Max Potential First Input Delay 20 ms

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 1,654 KiB

●JavaScript execution time 0.1 s

●Minimizes main-thread work 0.5 s

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 30 ms

●Server Backend Latencies 190 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 3 layout shifts found

○INP breakdown

○LCP request discovery

○User Timing marks and measures

○Avoid long main-thread tasks

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

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
Watch Ted Lasso on the Apple TV app `div.section-tv > p.legal > a.icon-wrapper > span.icon-copy`
Ted Lasso `p.legal > a.icon-wrapper > span.icon-copy > em`

These are opportunities to improve the legibility of your content.

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
Store menu `div.globalnav-item > ul.globalnav-submenu-trigger-group > li.globalnav-submenu-trigger-item > button#globalnav-menubutton-link-store`
Mac menu `div.globalnav-item > ul.globalnav-submenu-trigger-group > li.globalnav-submenu-trigger-item > button#globalnav-menubutton-link-mac`
iPad menu `div.globalnav-item > ul.globalnav-submenu-trigger-group > li.globalnav-submenu-trigger-item > button#globalnav-menubutton-link-ipad`
iPhone menu `div.globalnav-item > ul.globalnav-submenu-trigger-group > li.globalnav-submenu-trigger-item > button#globalnav-menubutton-link-iphone`
Watch menu `div.globalnav-item > ul.globalnav-submenu-trigger-group > li.globalnav-submenu-trigger-item > button#globalnav-menubutton-link-watch`
Vision menu `div.globalnav-item > ul.globalnav-submenu-trigger-group > li.globalnav-submenu-trigger-item > button#globalnav-menubutton-link-vision`
AirPods menu `div.globalnav-item > ul.globalnav-submenu-trigger-group > li.globalnav-submenu-trigger-item > button#globalnav-menubutton-link-airpods`
TV and Home menu `div.globalnav-item > ul.globalnav-submenu-trigger-group > li.globalnav-submenu-trigger-item > button#globalnav-menubutton-link-tv-home`
Entertainment menu `div.globalnav-item > ul.globalnav-submenu-trigger-group > li.globalnav-submenu-trigger-item > button#globalnav-menubutton-link-entertainment`
Accessories menu `div.globalnav-item > ul.globalnav-submenu-trigger-group > li.globalnav-submenu-trigger-item > button#globalnav-menubutton-link-accessories`
Support menu `div.globalnav-item > ul.globalnav-submenu-trigger-group > li.globalnav-submenu-trigger-item > button#globalnav-menubutton-link-support`

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

●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

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

●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

●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

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

○Image elements have `[alt]` attributes

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

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

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

100

Best Practices

●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

●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

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 destination	Link Text
www.apple.com/apple-music/	Learn more
support.apple.com/itunes	Learn 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

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

○Image elements have `[alt]` attributes