Skip to content
https://mac.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.

47

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
www.apple.com/wss/fonts/SF-Pro-Text/v3/sf-pro-text_light.woff21106.0 s220.7 KiB
www.apple.com/wss/fonts/SF-Pro-Text/v3/sf-pro-text_semibold.woff22203.0 s229.6 KiB
www.apple.com/wss/fonts/SF-Pro-Text/v3/sf-pro-text_regular.woff2923.0 s216.2 KiB
/api-www/global-elements/global-header/v1/assets/globalhe...29.0 s161.1 KiB
www.apple.com/wss/fonts/SF-Pro-Display/v3/sf-pro-display_semibold.woff21789.0 s127.2 KiB
www.apple.com/metrics/ac-analytics/latest/scripts/ac-analytics.js256.0 s102.1 KiB
www.apple.com/wss/fonts/SF-Pro-Text/v3/sf-pro-text_regular-italic.woff2419.0 s87.1 KiB
www.apple.com/ac/localeswitcher/4/en_US/scripts/localeswitcher.built.js234.0 s55.6 KiB
www.apple.com/assets-www/en_WW/mac/04_product_tile/large/mba_13_15_e733a3435.jpg1624.0 s26.5 KiB
/assets-www/en_WW/mac/04_product_tile/large/studio_displa...420.0 s21.5 KiB
/assets-www/en_WW/mac/04_product_tile/large/studio_displa...1641.0 s23.2 KiB
www.apple.com/api-www/global-elements/global-header/v1/assets/globalheader.css165.0 s15.5 KiB
www.apple.com/assets-www/en_WW/mac/04_product_tile/large/imac_24_7732743f3.jpg1623.0 s16.6 KiB
www.apple.com/wss/fonts/SF-Pro-Icons/v3/sf-pro-icons_regular.woff2728.0 s14.5 KiB
www.apple.com/wss/fonts/SF-Pro-Icons/v3/sf-pro-icons_light.woff22644.0 s14.6 KiB
www.apple.com/assets-www/en_WW/mac/04_product_tile/large/mbn_37b3fdaaf.jpg1641.0 s13.7 KiB
www.apple.com/assets-www/en_WW/mac/04_product_tile/large/mbp_14_16_fa5e3a2b2.jpg1641.0 s10.6 KiB
www.apple.com/assets-www/en_WW/mac/04_chapternav/small/nav_mba_ea12e0d5b.png328.0 s9.1 KiB
/assets-www/en_WW/mac/04_chapternav/small/nav_shop_mac_0f...1644.0 s9.9 KiB
/api-www/global-elements/global-footer/v1/en_US/styles/ac...35.0 s7.2 KiB
/assets-www/en_WW/mac/04_chapternav/small/nav_displays_7c...2733.0 s8.1 KiB
www.apple.com/metrics/data-relay/latest/scripts/data-relay.js108.0 s6.0 KiB
www.apple.com/assets-www/en_WW/mac/04_chapternav/small/nav_imac_24_832584093.png1437.0 s6.1 KiB
www.apple.com/assets-www/en_WW/mac/04_chapternav/small/nav_macos_02e825e85.png1437.0 s6.0 KiB
/assets-www/en_WW/mac/04_chapternav/small/nav_accessories...77.0 s4.5 KiB
www.apple.com/assets-www/en_WW/mac/04_chapternav/small/nav_mbn_1fa302e95.png2733.0 s5.2 KiB
www.apple.com/assets-www/en_WW/mac/04_chapternav/small/nav_mbp_bfa749034.png1644.0 s4.9 KiB
www.apple.com/assets-www/en_WW/mac/04_chapternav/small/nav_hmc_4be20094c.png2515.0 s4.7 KiB
/assets-www/en_WW/mac/04_product_tile/large/mac_studio_e9...1211.0 s4.1 KiB
www.apple.com/assets-www/en_WW/mac/04_chapternav/small/nav_compare_cacd858a8.png1644.0 s3.6 KiB
www.apple.com/assets-www/en_WW/mac/04_product_tile/large/mac_mini_d300dfe42.jpg1641.0 s3.0 KiB
www.apple.com/wss/fonts?families=SF+Pro,v3|SF+Pro+Icons,v32707.0 s1.9 KiB
/api-www/global-elements/global-footer/v1/en_US/assets/ac...567.0 s1.4 KiB
/assets-www/en_WW/mac/04_chapternav/small/nav_mac_studio_...1644.0 s1.5 KiB
/api-www/global-elements/global-footer/v1/en_US/assets/ac...106.0 s1.0 KiB
/assets-www/en_WW/mac/04_chapternav/small/nav_mac_mini_bf...1644.0 s1.1 KiB
/assets-www/en_WW/common/color_indicator/fp_color_indicat...2429.0 s709 B
/assets-www/en_WW/common/color_indicator/fp_color_indicat...1995.0 s694 B
/assets-www/en_WW/common/color_indicator/fp_color_indicat...2429.0 s703 B
/assets-www/en_WW/common/color_indicator/fp_color_indicat...2620.0 s695 B
/assets-www/en_WW/common/color_indicator/fp_color_indicat...3516.0 s704 B
/assets-www/en_WW/common/color_indicator/fp_color_indicat...3555.0 s696 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.

URLEst Savings
www.apple.com/wss/fonts/SF-Pro-Text/v3/sf-pro-text_regular.woff2100 ms
www.apple.com/wss/fonts/SF-Pro-Display/v3/sf-pro-display_semibold.woff2100 ms
www.apple.com/wss/fonts/SF-Pro-Icons/v3/sf-pro-icons_regular.woff290 ms
www.apple.com/wss/fonts/SF-Pro-Text/v3/sf-pro-text_semibold.woff275 ms
www.apple.com/wss/fonts/SF-Pro-Text/v3/sf-pro-text_regular-italic.woff265 ms
www.apple.com/wss/fonts/SF-Pro-Icons/v3/sf-pro-icons_light.woff220 ms
www.apple.com/wss/fonts/SF-Pro-Text/v3/sf-pro-text_light.woff215 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:200.074 source:map[column:1397 line:1 type:source-location url:https://www.apple.com/_apps/artisan/_next/static/chunks/framework-33b5afb7a08c1576.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:125.199 source:map[type:text value:[unattributed]]] map[reflowTime:1.566 source:map[column:20832 line:0 type:source-location url:https://www.apple.com/_apps/artisan/_next/static/chunks/105.6f75be5316350cac.js urlProvider:network]] map[reflowTime:62.092 source:map[column:16041 line:0 type:source-location url:https://www.apple.com/_apps/artisan/_next/static/chunks/7607.7a9b05402b7c00e8.js urlProvider:network]] map[reflowTime:2.694 source:map[column:141981 line:0 type:source-location url:https://www.apple.com/_apps/artisan/_next/static/chunks/8681.c0c493e72a8744bf.js urlProvider:network]] map[reflowTime:45.191 source:map[column:36100 line:0 type:source-location url:https://www.apple.com/_apps/artisan/_next/static/chunks/6707.0419197dfa842c6e.js urlProvider:network]] map[reflowTime:52.971 source:map[column:1986 line:0 type:source-location url:https://www.apple.com/_apps/artisan/_next/static/chunks/8373.faf80ee902ca62ce.js urlProvider:network]] map[reflowTime:74.868 source:map[column:13907 line:0 type:source-location url:https://www.apple.com/_apps/artisan/_next/static/chunks/6707.0419197dfa842c6e.js urlProvider:network]] map[reflowTime:12.647 source:map[column:25303 line:0 type:source-location url:https://www.apple.com/_apps/artisan/_next/static/chunks/6707.0419197dfa842c6e.js urlProvider:network]] map[reflowTime:18.322 source:map[column:74467 line:240 type:source-location url:https://www.apple.com/metrics/ac-analytics/latest/scripts/ac-analytics.js urlProvider:network]] map[reflowTime:18.737 source:map[column:29981 line:0 type:source-location url:https://www.apple.com/_apps/artisan/_next/static/chunks/6707.0419197dfa842c6e.js urlProvider:network]] map[reflowTime:5.34 source:map[column:79800 line:0 type:source-location url:https://www.apple.com/_apps/artisan/_next/static/chunks/8681.c0c493e72a8744bf.js urlProvider:network]] map[reflowTime:0.346 source:map[column:16725 line:0 type:source-location url:https://www.apple.com/_apps/artisan/_next/static/chunks/7607.7a9b05402b7c00e8.js urlProvider:network]] map[reflowTime:2.838 source:map[column:21993 line:240 type:source-location url:https://www.apple.com/metrics/ac-analytics/latest/scripts/ac-analytics.js urlProvider:network]] map[reflowTime:21.43 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:87.598 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]]]

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]
items: [map[duration:356.712 label:Time to first byte subpart:timeToFirstByte] map[duration:3125.547 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-H2
nodeLabel: Explore the lineup.
path: 1,HTML,1,BODY,3,DIV,0,DIV,1,MAIN,2,SECTION,0,DIV,0,DIV,0,H2
selector: section.MarcomSection_section__Hd6T8 > div.section-content > div.SectionHeader_container__OMsxL > h2#product-tile-section-3-header
snippet: <h2 id="product-tile-section-3-header" class="SectionHeader_headline__aqRKz MarcomSection_enhanced--active__QjigW animat…" style="transform: matrix(1, 0, 0, 1, 0, 0); opacity: 1;">

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

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.ProductTile_productImage__6tu_j > figure.ResponsivePicture_responsive-picture__VWL7l > picture.ResponsivePicture_responsive-picture__picture__jjeBP > img
www.apple.com/assets-www/en_WW/mac/04_product_tile/large/mba_13_15_e733a3435.jpg26.2 KiB10.9 KiB
figure.ChapterNav_chapternav-icon__6FVEi > span.ResponsivePicture_responsive-picture__VWL7l > picture.ResponsivePicture_responsive-picture__picture__jjeBP > img figure.ChapterNav_chapternav-icon__6FVEi > span.ResponsivePicture_responsive-picture__VWL7l > picture.ResponsivePicture_responsive-picture__picture__jjeBP > img
/assets-www/en_WW/mac/04_chapternav/small/nav_shop_mac_0f...9.5 KiB8.3 KiB
figure.ChapterNav_chapternav-icon__6FVEi > span.ResponsivePicture_responsive-picture__VWL7l > picture.ResponsivePicture_responsive-picture__picture__jjeBP > img figure.ChapterNav_chapternav-icon__6FVEi > span.ResponsivePicture_responsive-picture__VWL7l > picture.ResponsivePicture_responsive-picture__picture__jjeBP > img
www.apple.com/assets-www/en_WW/mac/04_chapternav/small/nav_mba_ea12e0d5b.png8.8 KiB7.9 KiB
div.ProductTile_productImage__6tu_j > figure.ResponsivePicture_responsive-picture__VWL7l > picture.ResponsivePicture_responsive-picture__picture__jjeBP > img
/assets-www/en_WW/mac/04_product_tile/large/studio_displa...22.9 KiB7.6 KiB
figure.ChapterNav_chapternav-icon__6FVEi > span.ResponsivePicture_responsive-picture__VWL7l > picture.ResponsivePicture_responsive-picture__picture__jjeBP > img figure.ChapterNav_chapternav-icon__6FVEi > span.ResponsivePicture_responsive-picture__VWL7l > picture.ResponsivePicture_responsive-picture__picture__jjeBP > img
/assets-www/en_WW/mac/04_chapternav/small/nav_displays_7c...7.7 KiB6.9 KiB
div.ProductTile_productImage__6tu_j > figure.ResponsivePicture_responsive-picture__VWL7l > picture.ResponsivePicture_responsive-picture__picture__jjeBP > img
/assets-www/en_WW/mac/04_product_tile/large/studio_displa...21.2 KiB5.9 KiB
figure.ChapterNav_chapternav-icon__6FVEi > span.ResponsivePicture_responsive-picture__VWL7l > picture.ResponsivePicture_responsive-picture__picture__jjeBP > img figure.ChapterNav_chapternav-icon__6FVEi > span.ResponsivePicture_responsive-picture__VWL7l > picture.ResponsivePicture_responsive-picture__picture__jjeBP > img
www.apple.com/assets-www/en_WW/mac/04_chapternav/small/nav_macos_02e825e85.png5.7 KiB5.1 KiB
figure.ChapterNav_chapternav-icon__6FVEi > span.ResponsivePicture_responsive-picture__VWL7l > picture.ResponsivePicture_responsive-picture__picture__jjeBP > img figure.ChapterNav_chapternav-icon__6FVEi > span.ResponsivePicture_responsive-picture__VWL7l > picture.ResponsivePicture_responsive-picture__picture__jjeBP > img
www.apple.com/assets-www/en_WW/mac/04_chapternav/small/nav_imac_24_832584093.png5.7 KiB5.0 KiB
figure.ChapterNav_chapternav-icon__6FVEi > span.ResponsivePicture_responsive-picture__VWL7l > picture.ResponsivePicture_responsive-picture__picture__jjeBP > img figure.ChapterNav_chapternav-icon__6FVEi > span.ResponsivePicture_responsive-picture__VWL7l > picture.ResponsivePicture_responsive-picture__picture__jjeBP > img
www.apple.com/assets-www/en_WW/mac/04_chapternav/small/nav_mbn_1fa302e95.png4.9 KiB4.2 KiB

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: 500 ms
URLTime Spent
mac.com/500 ms
www.apple.com/mac/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.

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

Reduce unused 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: 40 ms 28.4 KiB
URLTransfer SizeEst Savings
www.apple.com/_apps/artisan/_next/static/css/f23d69f76dd4e6da.css15.3 KiB15.3 KiB
www.apple.com/api-www/global-elements/global-header/v1/assets/globalheader.css14.8 KiB13.1 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.

Estimated savings: 40 ms 141.8 KiB
URLTransfer SizeEst Savings
/api-www/global-elements/global-header/v1/assets/globalhe...160.2 KiB56.7 KiB
www.apple.com/metrics/ac-analytics/latest/scripts/ac-analytics.js101.3 KiB40.0 KiB
www.apple.com/_apps/artisan/_next/static/chunks/4011.6f26d45a9009e19d.js79.5 KiB25.1 KiB
www.apple.com/_apps/artisan/_next/static/chunks/framework-33b5afb7a08c1576.js56.5 KiB20.0 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTotal CPU TimeScript EvaluationScript Parse
www.apple.com/_apps/artisan/_next/static/chunks/framework-33b5afb7a08c1576.js1.5 s1.0 s8.2 ms
www.apple.com/mac/750 ms7.0 ms0.5 ms
www.apple.com/_apps/artisan/_next/static/chunks/3218-096c15977036d74c.js638 ms515 ms3.0 ms
Unattributable268 ms5.6 ms0.0 ms
/api-www/global-elements/global-header/v1/assets/globalhe...247 ms104 ms7.4 ms
www.apple.com/_apps/artisan/_next/static/chunks/8681.c0c493e72a8744bf.js155 ms71 ms5.8 ms
/_apps/artisan/_next/static/chunks/pages/[[...uri]]-69f04...129 ms126 ms2.5 ms
www.apple.com/ac/localeswitcher/4/en_US/scripts/localeswitcher.built.js60 ms51 ms7.1 ms

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation2.0 s
Style & Layout1.0 s
Other603 ms
Rendering122 ms
Script Parsing & Compilation92 ms
Parse HTML & CSS91 ms
Garbage Collection74 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTransfer Size
www.apple.com/mac/1009.7 KiB
www.apple.com/mac/1009.7 KiB
www.apple.com/mac/1009.7 KiB
www.apple.com/wss/fonts/SF-Pro-Text/v3/sf-pro-text_semibold.woff2229.6 KiB
www.apple.com/wss/fonts/SF-Pro-Text/v3/sf-pro-text_light.woff2220.7 KiB
www.apple.com/wss/fonts/SF-Pro-Text/v3/sf-pro-text_regular.woff2216.2 KiB
www.apple.com/mac/179.6 KiB
/api-www/global-elements/global-header/v1/assets/globalhe...161.1 KiB
www.apple.com/wss/fonts/SF-Pro-Display/v3/sf-pro-display_semibold.woff2127.2 KiB
www.apple.com/metrics/ac-analytics/latest/scripts/ac-analytics.js102.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
dual-tone blue ul.ColorIndicator_colorindicator-items__0BgjI > li.ColorIndicator_colorindicator-item__wAung > picture > img
/assets-www/en_WW/common/color_indicator/fp_color_indicat...
dual-tone purple ul.ColorIndicator_colorindicator-items__0BgjI > li.ColorIndicator_colorindicator-item__wAung > picture > img
/assets-www/en_WW/common/color_indicator/fp_color_indicat...
dual-tone pink ul.ColorIndicator_colorindicator-items__0BgjI > li.ColorIndicator_colorindicator-item__wAung > picture > img
/assets-www/en_WW/common/color_indicator/fp_color_indicat...
dual-tone orange ul.ColorIndicator_colorindicator-items__0BgjI > li.ColorIndicator_colorindicator-item__wAung > picture > img
/assets-www/en_WW/common/color_indicator/fp_color_indicat...
dual-tone yellow ul.ColorIndicator_colorindicator-items__0BgjI > li.ColorIndicator_colorindicator-item__wAung > picture > img
/assets-www/en_WW/common/color_indicator/fp_color_indicat...
dual-tone green ul.ColorIndicator_colorindicator-items__0BgjI > li.ColorIndicator_colorindicator-item__wAung > picture > img
/assets-www/en_WW/common/color_indicator/fp_color_indicat...
dual-tone blue ul.ColorIndicator_colorindicator-items__0BgjI > li.ColorIndicator_colorindicator-item__wAung > picture > img
/assets-www/en_WW/common/color_indicator/fp_color_indicat...
dual-tone purple ul.ColorIndicator_colorindicator-items__0BgjI > li.ColorIndicator_colorindicator-item__wAung > picture > img
/assets-www/en_WW/common/color_indicator/fp_color_indicat...
dual-tone pink ul.ColorIndicator_colorindicator-items__0BgjI > li.ColorIndicator_colorindicator-item__wAung > picture > img
/assets-www/en_WW/common/color_indicator/fp_color_indicat...
dual-tone orange ul.ColorIndicator_colorindicator-items__0BgjI > li.ColorIndicator_colorindicator-item__wAung > picture > img
/assets-www/en_WW/common/color_indicator/fp_color_indicat...
dual-tone yellow ul.ColorIndicator_colorindicator-items__0BgjI > li.ColorIndicator_colorindicator-item__wAung > picture > img
/assets-www/en_WW/common/color_indicator/fp_color_indicat...
dual-tone green ul.ColorIndicator_colorindicator-items__0BgjI > li.ColorIndicator_colorindicator-item__wAung > picture > img
/assets-www/en_WW/common/color_indicator/fp_color_indicat...

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

●Layout shift culprits
●Optimize DOM size
●Modern HTTP
●Render blocking requests
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●User Timing marks and measures 4 user timings
●Avoid long main-thread tasks 10 long tasks found
●Avoid non-composited animations 2 animated elements found
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 100 ms
●Server Backend Latencies 50 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 30 ms
●Avoid large layout shifts 2 layout shifts found
○INP breakdown
○LCP request discovery
89

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

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.ProductTile_productImage__6tu_j > figure.ResponsivePicture_responsive-picture__VWL7l > picture.ResponsivePicture_responsive-picture__picture__jjeBP > img
div.ProductTile_productImage__6tu_j > figure.ResponsivePicture_responsive-picture__VWL7l > picture.ResponsivePicture_responsive-picture__picture__jjeBP > img
div.ProductTile_productImage__6tu_j > figure.ResponsivePicture_responsive-picture__VWL7l > picture.ResponsivePicture_responsive-picture__picture__jjeBP > img
div.ProductTile_productImage__6tu_j > figure.ResponsivePicture_responsive-picture__VWL7l > picture.ResponsivePicture_responsive-picture__picture__jjeBP > img
div.ProductTile_productImage__6tu_j > figure.ResponsivePicture_responsive-picture__VWL7l > picture.ResponsivePicture_responsive-picture__picture__jjeBP > img
div.ProductTile_productImage__6tu_j > figure.ResponsivePicture_responsive-picture__VWL7l > picture.ResponsivePicture_responsive-picture__picture__jjeBP > img
div.ProductTile_productImage__6tu_j > figure.ResponsivePicture_responsive-picture__VWL7l > picture.ResponsivePicture_responsive-picture__picture__jjeBP > img
div.ProductTile_productImage__6tu_j > figure.ResponsivePicture_responsive-picture__VWL7l > picture.ResponsivePicture_responsive-picture__picture__jjeBP > img

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
Apple Store Mac iPad iPhone Watch Vision AirPods TV & Home Entertainment Access… div#globalheader > nav#globalnav > div.globalnav-content > ul#globalnav-list

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

Best practices

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
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
●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
●Links are distinguishable without relying on color.
●Links have a discernible name
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
●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
○`<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
○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.
○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
85

SEO

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

Content Best Practices

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destinationLink Text
www.apple.com/macbook-neo/Learn more
www.apple.com/macbook-air/Learn more
www.apple.com/macbook-pro/Learn more
www.apple.com/imac/Learn more
www.apple.com/mac-mini/Learn more
www.apple.com/mac-studio/Learn more
www.apple.com/studio-display/Learn more
www.apple.com/studio-display-xdr/Learn more
www.apple.com/mac/mac-does-that/Learn more
www.apple.com/studio-display/Learn more
support.apple.com/102730here

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.ProductTile_productImage__6tu_j > figure.ResponsivePicture_responsive-picture__VWL7l > picture.ResponsivePicture_responsive-picture__picture__jjeBP > img
div.ProductTile_productImage__6tu_j > figure.ResponsivePicture_responsive-picture__VWL7l > picture.ResponsivePicture_responsive-picture__picture__jjeBP > img
div.ProductTile_productImage__6tu_j > figure.ResponsivePicture_responsive-picture__VWL7l > picture.ResponsivePicture_responsive-picture__picture__jjeBP > img
div.ProductTile_productImage__6tu_j > figure.ResponsivePicture_responsive-picture__VWL7l > picture.ResponsivePicture_responsive-picture__picture__jjeBP > img
div.ProductTile_productImage__6tu_j > figure.ResponsivePicture_responsive-picture__VWL7l > picture.ResponsivePicture_responsive-picture__picture__jjeBP > img
div.ProductTile_productImage__6tu_j > figure.ResponsivePicture_responsive-picture__VWL7l > picture.ResponsivePicture_responsive-picture__picture__jjeBP > img
div.ProductTile_productImage__6tu_j > figure.ResponsivePicture_responsive-picture__VWL7l > picture.ResponsivePicture_responsive-picture__picture__jjeBP > img
div.ProductTile_productImage__6tu_j > figure.ResponsivePicture_responsive-picture__VWL7l > picture.ResponsivePicture_responsive-picture__picture__jjeBP > 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
●robots.txt is valid
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Send Feedback