Skip to content
https://webkit.org

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.

85

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/v1/sf-pro-text_light.woff2376.0 s152.8 KiB
www.apple.com/wss/fonts/SF-Pro-Text/v1/sf-pro-text_regular.woff2590.0 s152.7 KiB
www.apple.com/wss/fonts/SF-Pro-Text/v1/sf-pro-text_medium.woff22958.0 s165.2 KiB
www.apple.com/wss/fonts/SF-Pro-Display/v1/sf-pro-display_medium.woff23391.0 s150.9 KiB
webkit.org/wp-content/themes/webkit/style.css?20221005010.0 ms15.5 KiB
webkit.org/wp-content/themes/webkit/images/compass.svg0.0 ms5.6 KiB
webkit.org/wp-content/themes/webkit/images/webkit.svg0.0 ms4.6 KiB
webkit.org/wp-content/themes/webkit/images/template.svg0.0 ms2.4 KiB
shynet.webkit.org/ingress/561b9e53-fb8c-4297-ae4d-bde05e8daa59/script.js0.0 ms2.2 KiB
webkit.org/wp-content/themes/webkit/scripts/global.js?ver=1.00.0 ms1.7 KiB
www.apple.com/wss/fonts?families=SF+Pro,v13086.0 s1.6 KiB
webkit.org/wp-content/themes/webkit/images/search.svg#light0.0 ms1.2 KiB
www.apple.com/wss/fonts?families=SF+Mono,v22029.0 s1.2 KiB
webkit.org/wp-content/themes/webkit/images/chevron.svg0.0 ms587 B
webkit.org/wp-content/themes/webkit/images/menu-down.svg0.0 ms540 B

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-DIV
nodeLabel: body.home > div.hero > div#compass
path: 1,HTML,1,BODY,4,DIV,1,DIV
selector: body.home > div.hero > div#compass
snippet: <div id="compass">

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

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.

URLTransfer SizeDuration
webkit.org/wp-content/themes/webkit/style.css?202210050115.5 KiB
www.apple.com/wss/fonts?families=SF+Pro,v11.6 KiB207 ms
www.apple.com/wss/fonts?families=SF+Mono,v21.2 KiB

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/v1/sf-pro-text_medium.woff215 ms
www.apple.com/wss/fonts/SF-Pro-Text/v1/sf-pro-text_light.woff210 ms
www.apple.com/wss/fonts/SF-Pro-Text/v1/sf-pro-text_regular.woff210 ms
www.apple.com/wss/fonts/SF-Pro-Display/v1/sf-pro-display_medium.woff25.0 ms

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

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 11.4 KiB
URLTransfer SizeEst Savings
webkit.org/wp-content/themes/webkit/style.css?202210050115.2 KiB11.4 KiB

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 3.7 KiB
URLTransfer SizeEst Savings
webkit.org/wp-content/themes/webkit/style.css?202210050115.5 KiB3.7 KiB

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

●Time to Interactive 1.7 s
●Layout shift culprits
●Document request latency
●Optimize DOM size
●Forced reflow
●Improve image delivery
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Max Potential First Input Delay 20 ms
●Minify JavaScript
●Reduce unused JavaScript
●Avoids enormous network payloads Total size was 712 KiB
●JavaScript execution time 0.0 s
●Minimizes main-thread work 0.2 s
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 170 ms
●Server Backend Latencies 30 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Avoid multiple page redirects
●Initial server response time was short Root document took 510 ms
●Avoid large layout shifts 1 layout shift found
○INP breakdown
○User Timing marks and measures
○Avoid long main-thread tasks
○Avoid non-composited animations
63

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

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Downloads Feature Status CSS Features Standards Positions Documentation Web In… div.page-width > nav#site-nav > div.menu-main-menu-container > ul#menu-main-menu
CSS Features Standards Positions div.menu-main-menu-container > ul#menu-main-menu > li#menu-item-4272 > ul#sub-menu-for-4272
Web Inspector Tracking Prevention div.menu-main-menu-container > ul#menu-main-menu > li#menu-item-9988 > ul#sub-menu-for-9988
Project Goals Bug Prioritization Bug Report Guidelines Code Style Guidelines Co… div.menu-main-menu-container > ul#menu-main-menu > li#menu-item-4282 > ul#sub-menu-for-4282
Getting Started Contributing Code Testing Contributions How to Report Bugs GitH… div.menu-main-menu-container > ul#menu-main-menu > li#menu-item-4274 > ul#sub-menu-for-4274
News Posts CSS Posts Contributing Posts Privacy Posts Performance Posts JavaScr… div.menu-main-menu-container > ul#menu-main-menu > li#menu-item-4270 > ul#sub-menu-for-4270

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Downloads div.menu-main-menu-container > ul#menu-main-menu > li#menu-item-6091 > a
Feature Status div.menu-main-menu-container > ul#menu-main-menu > li#menu-item-4272 > a
CSS Features li#menu-item-4272 > ul#sub-menu-for-4272 > li#menu-item-13052 > a
Standards Positions li#menu-item-4272 > ul#sub-menu-for-4272 > li#menu-item-14388 > a
Documentation div.menu-main-menu-container > ul#menu-main-menu > li#menu-item-9988 > a
Web Inspector li#menu-item-9988 > ul#sub-menu-for-9988 > li#menu-item-9989 > a
Tracking Prevention li#menu-item-9988 > ul#sub-menu-for-9988 > li#menu-item-10868 > a
Policies div.menu-main-menu-container > ul#menu-main-menu > li#menu-item-4282 > a
Project Goals li#menu-item-4282 > ul#sub-menu-for-4282 > li#menu-item-10037 > a
Bug Prioritization li#menu-item-4282 > ul#sub-menu-for-4282 > li#menu-item-13077 > a
Bug Report Guidelines li#menu-item-4282 > ul#sub-menu-for-4282 > li#menu-item-13076 > a
Code Style Guidelines li#menu-item-4282 > ul#sub-menu-for-4282 > li#menu-item-13075 > a
Commit and Review Policy li#menu-item-4282 > ul#sub-menu-for-4282 > li#menu-item-13074 > a
Feature Policy li#menu-item-4282 > ul#sub-menu-for-4282 > li#menu-item-13073 > a
Security Policy li#menu-item-4282 > ul#sub-menu-for-4282 > li#menu-item-13072 > a
Tracking Prevention Policy li#menu-item-4282 > ul#sub-menu-for-4282 > li#menu-item-13071 > a
Contribute div.menu-main-menu-container > ul#menu-main-menu > li#menu-item-4274 > a
Getting Started li#menu-item-4274 > ul#sub-menu-for-4274 > li#menu-item-4277 > a
Contributing Code li#menu-item-4274 > ul#sub-menu-for-4274 > li#menu-item-4284 > a
Testing Contributions li#menu-item-4274 > ul#sub-menu-for-4274 > li#menu-item-4281 > a
How to Report Bugs li#menu-item-4274 > ul#sub-menu-for-4274 > li#menu-item-4273 > a
GitHub Repository li#menu-item-4274 > ul#sub-menu-for-4274 > li#menu-item-4278 > a
Blog div.menu-main-menu-container > ul#menu-main-menu > li#menu-item-4270 > a
News Posts li#menu-item-4270 > ul#sub-menu-for-4270 > li#menu-item-13057 > a
CSS Posts li#menu-item-4270 > ul#sub-menu-for-4270 > li#menu-item-13058 > a
Contributing Posts li#menu-item-4270 > ul#sub-menu-for-4270 > li#menu-item-13063 > a
Privacy Posts li#menu-item-4270 > ul#sub-menu-for-4270 > li#menu-item-13062 > a
Performance Posts li#menu-item-4270 > ul#sub-menu-for-4270 > li#menu-item-13060 > a
JavaScript Posts li#menu-item-4270 > ul#sub-menu-for-4270 > li#menu-item-13061 > a
Standards Posts li#menu-item-4270 > ul#sub-menu-for-4270 > li#menu-item-13056 > a
Web Inspector Posts li#menu-item-4270 > ul#sub-menu-for-4270 > li#menu-item-13059 > a
Safari Technology Preview Posts li#menu-item-4270 > ul#sub-menu-for-4270 > li#menu-item-13055 > a

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
safari technology preview icon div.tile > div.background-image > svg > use
performance icon div.tile > div.background-image > svg > use
default icon div.tile > div.background-image > svg > use
default icon div.tile > div.background-image > svg > use
default icon div.tile > div.background-image > svg > use

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
More Blog Posts main#content > div.page-width > div.pagination > a.page-numbers

These are opportunities to improve the legibility of your content.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These are opportunities to improve the interpretation of your content by users in different locales.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ul#menu-main-menu > li > form > input.search-input ul#menu-main-menu > li > form > input.search-input

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 require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Downloads nav#site-nav > div.menu-main-menu-container > ul#menu-main-menu > li#menu-item-6091
Feature Status CSS Features Standards Positions nav#site-nav > div.menu-main-menu-container > ul#menu-main-menu > li#menu-item-4272
CSS Features ul#menu-main-menu > li#menu-item-4272 > ul#sub-menu-for-4272 > li#menu-item-13052
Standards Positions ul#menu-main-menu > li#menu-item-4272 > ul#sub-menu-for-4272 > li#menu-item-14388
Documentation Web Inspector Tracking Prevention nav#site-nav > div.menu-main-menu-container > ul#menu-main-menu > li#menu-item-9988
Web Inspector ul#menu-main-menu > li#menu-item-9988 > ul#sub-menu-for-9988 > li#menu-item-9989
Tracking Prevention ul#menu-main-menu > li#menu-item-9988 > ul#sub-menu-for-9988 > li#menu-item-10868
Policies Project Goals Bug Prioritization Bug Report Guidelines Code Style Guid… nav#site-nav > div.menu-main-menu-container > ul#menu-main-menu > li#menu-item-4282
Project Goals ul#menu-main-menu > li#menu-item-4282 > ul#sub-menu-for-4282 > li#menu-item-10037
Bug Prioritization ul#menu-main-menu > li#menu-item-4282 > ul#sub-menu-for-4282 > li#menu-item-13077
Bug Report Guidelines ul#menu-main-menu > li#menu-item-4282 > ul#sub-menu-for-4282 > li#menu-item-13076
Code Style Guidelines ul#menu-main-menu > li#menu-item-4282 > ul#sub-menu-for-4282 > li#menu-item-13075
Commit and Review Policy ul#menu-main-menu > li#menu-item-4282 > ul#sub-menu-for-4282 > li#menu-item-13074
Feature Policy ul#menu-main-menu > li#menu-item-4282 > ul#sub-menu-for-4282 > li#menu-item-13073
Security Policy ul#menu-main-menu > li#menu-item-4282 > ul#sub-menu-for-4282 > li#menu-item-13072
Tracking Prevention Policy ul#menu-main-menu > li#menu-item-4282 > ul#sub-menu-for-4282 > li#menu-item-13071
Contribute Getting Started Contributing Code Testing Contributions How to Repor… nav#site-nav > div.menu-main-menu-container > ul#menu-main-menu > li#menu-item-4274
Getting Started ul#menu-main-menu > li#menu-item-4274 > ul#sub-menu-for-4274 > li#menu-item-4277
Contributing Code ul#menu-main-menu > li#menu-item-4274 > ul#sub-menu-for-4274 > li#menu-item-4284
Testing Contributions ul#menu-main-menu > li#menu-item-4274 > ul#sub-menu-for-4274 > li#menu-item-4281
How to Report Bugs ul#menu-main-menu > li#menu-item-4274 > ul#sub-menu-for-4274 > li#menu-item-4273
GitHub Repository ul#menu-main-menu > li#menu-item-4274 > ul#sub-menu-for-4274 > li#menu-item-4278
Blog News Posts CSS Posts Contributing Posts Privacy Posts Performance Posts Ja… nav#site-nav > div.menu-main-menu-container > ul#menu-main-menu > li#menu-item-4270
News Posts ul#menu-main-menu > li#menu-item-4270 > ul#sub-menu-for-4270 > li#menu-item-13057
CSS Posts ul#menu-main-menu > li#menu-item-4270 > ul#sub-menu-for-4270 > li#menu-item-13058
Contributing Posts ul#menu-main-menu > li#menu-item-4270 > ul#sub-menu-for-4270 > li#menu-item-13063
Privacy Posts ul#menu-main-menu > li#menu-item-4270 > ul#sub-menu-for-4270 > li#menu-item-13062
Performance Posts ul#menu-main-menu > li#menu-item-4270 > ul#sub-menu-for-4270 > li#menu-item-13060
JavaScript Posts ul#menu-main-menu > li#menu-item-4270 > ul#sub-menu-for-4270 > li#menu-item-13061
Standards Posts ul#menu-main-menu > li#menu-item-4270 > ul#sub-menu-for-4270 > li#menu-item-13056
Web Inspector Posts ul#menu-main-menu > li#menu-item-4270 > ul#sub-menu-for-4270 > li#menu-item-13059
Safari Technology Preview Posts ul#menu-main-menu > li#menu-item-4270 > ul#sub-menu-for-4270 > li#menu-item-13055
nav#site-nav > div.menu-main-menu-container > ul#menu-main-menu > li nav#site-nav > div.menu-main-menu-container > ul#menu-main-menu > li

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
Read more div.tile > div.tile-content > p > a.readmore
Read more div.tile > div.tile-content > p > a.readmore
Read more div.tile > div.tile-content > p > a.readmore
Read more div.tile > div.tile-content > p > a.readmore
Read more div.tile > div.tile-content > p > a.readmore

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●ARIA attributes are used as specified for the element's role
●Document has a `<title>` element
●Links are distinguishable without relying on color.
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●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.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○`[aria-hidden="true"]` elements do not contain focusable descendents
○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
○Buttons have an accessible name
○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 a valid value for its `[lang]` attribute
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Image elements have `[alt]` attributes
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○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

●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
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Mitigate clickjacking with XFO or CSP
○Detected JavaScript libraries
83

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

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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
webkit.org/blog/17917/release-notes-for-safari-technology-preview-241/Read more
webkit.org/blog/17899/introducing-the-jetstream-3-benchmark-suite/Read more
webkit.org/blog/17862/webkit-features-for-safari-26-4/Read more
webkit.org/blog/17818/announcing-interop-2026/Read more
webkit.org/blog/17798/webkit-features-for-safari-26-3/Read 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
●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

Send Feedback