C — https://webkit.org | BeaverCheck Audit

Site Health

Score: 79 / 100

Based on 8 categories, 0 sections

Fast site — your users get a smooth experience.

Several missing protections leave your users and data exposed.

Several issues make your site difficult for assistive technology users.

Well-optimized for search — your content is discoverable.

Solid infrastructure — fast server responses across the board.

Mostly compliant — a few items need attention.

Good content signals with minor gaps.

Lean and efficient — low environmental impact per visit.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

WordPress · 712 peers

You 79

Avg 74

At average

0 50 100

Better than 87% of WordPress sites See full WordPress benchmark →

Amazon Route 53 · 975 peers

You 79

Avg 72

+7 above average

0 50 100

Better than 95% of Amazon Route 53 sites See full Amazon Route 53 benchmark →

Top Priorities (5)

Content-Security-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers

No Content-Security-Policy header found

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy

1 link(s) with no accessible text

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Link & Button Quality

2 control(s) without accessible label

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Form Accessibility

9 third-party resources (88% of weight)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Inventory

View fix priority matrix

Fix Priority Matrix

5 findings

Impact

Quick Wins

High impact, low effort — start here.

Strategic

High impact, requires investment.

Easy Improvements

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwebkit.org)](https://beavercheck.com/results/c8b6a61b-8930-4663-86fd-802648b673c8)

HTML

<a href="https://beavercheck.com/results/c8b6a61b-8930-4663-86fd-802648b673c8"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwebkit.org" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fwebkit.org

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 5.5s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. Addressing the critical issues below would have the most immediate impact on your user trust.

2 security gaps detected — browsers may warn visitors about your site.

2 accessibility issues exclude users who rely on assistive technology.

Your LCP is 5.5s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.

Could reach Estimate based on resolving critical issues

Conversion Barriers

2 critical 6 warning

8 barrier(s) likely increasing bounce by ~30%.

Speed (1)

Page takes 5.5s to load

+12% bounce

Users abandon at ~3s — you're 3.0s over the 2.5s threshold

Fix: Optimize render-blocking resources, preload the hero image, and compress images

Trust (1)

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Usability (1)

2 form field(s) without a label

+4% bounce

Screen readers skip unlabeled fields; autofill can't identify them; checkout abandonment spikes

Fix: Associate every input with a visible <label for="…">; add autocomplete attributes

Content (2)

No structured data

+2% bounce

No rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices

Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)

Content is hard to read

+2% bounce

Graduate-level reading difficulty — limits the addressable audience for product or blog pages

Fix: Shorten sentences; replace jargon with plain language; target Flesch ease ≥60

Navigation (3)

6 link(s) with generic text ("click here", "read more")

+1% bounce

Screen-reader users navigating by link list see no context — and search engines can't infer relevance

Fix: Rewrite with descriptive phrases that identify the destination

No skip-to-content link

+1% bounce

Keyboard and screen-reader users must tab through the entire header on every page

Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

6 broken link(s) on the page

+5% bounce

Clicks land on 404s — trust drops and the session often ends

Fix: Fix or remove the broken destinations surfaced on the Content tab

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

$600 investment → $4,161/month returns + USD 150,000 risk avoided

Payback period: < 1 month First-year ROI: +8223%

Investment

$600

6h · 5 findings

Monthly returns

$4,161 /mo

~$49,935 / year

Conversions recovered $4,161
Bandwidth savings $0.17

Regulatory risk avoided

USD 150,000

if kept compliant

ADA Title III USD 150,000

Payback period

0 12mo 24mo

$100 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

$600

6.0 developer hours at $100/hr

Based on United States rates ($100/hr)

Quick wins

$100 2 fixes in ~60 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions

Custom rate

$ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

$12,500 / month at risk

~$150,002 / year if left unfixed

Compliance Risk

$150,000

ADA Title III

Skip navigation link is missing (WCAG 2.4.1)
ADA Title III: USD 25,000 – USD 150,000
Multiple H1 headings (6 found)
ADA Title III: USD 25,000 – USD 150,000
2 control(s) without accessible label
ADA Title III: USD 25,000 – USD 150,000

Bandwidth Waste

$0.17 /mo

2184.9 MB/mo × 0.080 USD/GB

Optimize transfer: save ~218 KB per page load
Saves $0.17/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Monthly visitors

Unique monthly visitors from your analytics

Conversion rate (%)

Purchases, signups, or key actions

Avg. order value

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue

Current bounce (est.)

After fixes (est.)

Estimated bounce reduction

Fix 4 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

100

Best Practices

SEO

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

2.52 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

5.52 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

0 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.000

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

2.72 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

5.52 s

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

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more ▾

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

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
www.apple.com/wss/fonts/SF-Pro-Text/v1/sf-pro-text_light.woff2	390.0 s	152.8 KiB
www.apple.com/wss/fonts/SF-Pro-Text/v1/sf-pro-text_regular.woff2	605.0 s	152.7 KiB
www.apple.com/wss/fonts/SF-Pro-Text/v1/sf-pro-text_medium.woff2	2972.0 s	165.2 KiB
www.apple.com/wss/fonts/SF-Pro-Display/v1/sf-pro-display_medium.woff2	3405.0 s	150.9 KiB
webkit.org/wp-content/themes/webkit/style.css?2022100501	0.0 ms	15.5 KiB
webkit.org/wp-content/themes/webkit/images/compass.svg	0.0 ms	5.6 KiB
webkit.org/wp-content/themes/webkit/images/webkit.svg	0.0 ms	4.6 KiB
webkit.org/wp-content/themes/webkit/images/template.svg	0.0 ms	2.4 KiB
shynet.webkit.org/ingress/561b9e53-fb8c-4297-ae4d-bde05e8daa59/script.js	0.0 ms	2.2 KiB
webkit.org/wp-content/themes/webkit/scripts/global.js?ver=1.0	0.0 ms	1.7 KiB
www.apple.com/wss/fonts?families=SF+Pro,v1	3100.0 s	1.6 KiB
www.apple.com/wss/fonts?families=SF+Mono,v2	2043.0 s	1.2 KiB
webkit.org/wp-content/themes/webkit/images/chevron.svg	0.0 ms	587 B
webkit.org/wp-content/themes/webkit/images/menu-down.svg	0.0 ms	540 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.

URL	Transfer Size	Duration
webkit.org/wp-content/themes/webkit/style.css?2022100501	15.5 KiB
www.apple.com/wss/fonts?families=SF+Mono,v2	1.2 KiB	150 ms
www.apple.com/wss/fonts?families=SF+Pro,v1	1.6 KiB	761 ms

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/v1/sf-pro-text_medium.woff2	20 ms
www.apple.com/wss/fonts/SF-Pro-Text/v1/sf-pro-text_light.woff2	10 ms
www.apple.com/wss/fonts/SF-Pro-Text/v1/sf-pro-text_regular.woff2	10 ms
www.apple.com/wss/fonts/SF-Pro-Display/v1/sf-pro-display_medium.woff2	5.0 ms

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

Diagnostics

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

URL	Transfer Size	Est Savings
webkit.org/wp-content/themes/webkit/style.css?2022100501	15.5 KiB	3.7 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 11.5 KiB

URL	Transfer Size	Est Savings
webkit.org/wp-content/themes/webkit/style.css?2022100501	15.2 KiB	11.5 KiB

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

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

●JavaScript execution time 0.0 s

●Minimizes main-thread work 0.8 s

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 180 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 500 ms

○INP breakdown

○User Timing marks and measures

○Avoid long main-thread tasks

○Avoid non-composited animations

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

ARIA

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.

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

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

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Deprecated ARIA roles were not used

○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

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

○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

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

○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

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 destination	Link 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

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

Accessibility

100

Best Practices

SEO

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

1.69 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

1.73 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

0 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.001

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

1.69 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

1.73 s

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.

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more ▾

Source: Google web.dev / Lighthouse

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
www.apple.com/wss/fonts/SF-Pro-Text/v1/sf-pro-text_light.woff2	376.0 s	152.8 KiB
www.apple.com/wss/fonts/SF-Pro-Text/v1/sf-pro-text_regular.woff2	590.0 s	152.7 KiB
www.apple.com/wss/fonts/SF-Pro-Text/v1/sf-pro-text_medium.woff2	2958.0 s	165.2 KiB
www.apple.com/wss/fonts/SF-Pro-Display/v1/sf-pro-display_medium.woff2	3391.0 s	150.9 KiB
webkit.org/wp-content/themes/webkit/style.css?2022100501	0.0 ms	15.5 KiB
webkit.org/wp-content/themes/webkit/images/compass.svg	0.0 ms	5.6 KiB
webkit.org/wp-content/themes/webkit/images/webkit.svg	0.0 ms	4.6 KiB
webkit.org/wp-content/themes/webkit/images/template.svg	0.0 ms	2.4 KiB
shynet.webkit.org/ingress/561b9e53-fb8c-4297-ae4d-bde05e8daa59/script.js	0.0 ms	2.2 KiB
webkit.org/wp-content/themes/webkit/scripts/global.js?ver=1.0	0.0 ms	1.7 KiB
www.apple.com/wss/fonts?families=SF+Pro,v1	3086.0 s	1.6 KiB
webkit.org/wp-content/themes/webkit/images/search.svg#light	0.0 ms	1.2 KiB
www.apple.com/wss/fonts?families=SF+Mono,v2	2029.0 s	1.2 KiB
webkit.org/wp-content/themes/webkit/images/chevron.svg	0.0 ms	587 B
webkit.org/wp-content/themes/webkit/images/menu-down.svg	0.0 ms	540 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.

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.

URL	Transfer Size	Duration
webkit.org/wp-content/themes/webkit/style.css?2022100501	15.5 KiB
www.apple.com/wss/fonts?families=SF+Pro,v1	1.6 KiB	207 ms
www.apple.com/wss/fonts?families=SF+Mono,v2	1.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.

URL	Est Savings
www.apple.com/wss/fonts/SF-Pro-Text/v1/sf-pro-text_medium.woff2	15 ms
www.apple.com/wss/fonts/SF-Pro-Text/v1/sf-pro-text_light.woff2	10 ms
www.apple.com/wss/fonts/SF-Pro-Text/v1/sf-pro-text_regular.woff2	10 ms
www.apple.com/wss/fonts/SF-Pro-Display/v1/sf-pro-display_medium.woff2	5.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

URL	Transfer Size	Est Savings
webkit.org/wp-content/themes/webkit/style.css?2022100501	15.2 KiB	11.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

URL	Transfer Size	Est Savings
webkit.org/wp-content/themes/webkit/style.css?2022100501	15.5 KiB	3.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

Accessibility

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

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

SEO

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 destination	Link 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

Results for https://webkit.org

Site Health

How you compare

Top Priorities (5)

Fix Priority Matrix

Quick Wins

Strategic

Easy Improvements

Deprioritize

What fixing these means

Conversion Barriers

Speed (1)

Trust (1)

Usability (1)

Content (2)

Navigation (3)

Return on Investment

Investment

Monthly returns

Regulatory risk avoided

Payback period

Estimated Remediation Cost

Cost by category

Cost by effort level

What Inaction Is Costing You

Compliance Risk

Bandwidth Waste

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

ARIA

Contrast

Internationalization and localization

Best practices

Best Practices

SEO

Content Best Practices

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

ARIA

Contrast

Internationalization and localization

Names and labels

Tables and lists

Best practices

Best Practices

SEO

Content Best Practices

Keyboard Shortcuts