Skip to content
Audit Complete

Results for https://w3.org

Visit site
Spain Spain · Madrid Completed: Apr 16, 2026 17:10 UTC
Download JSON Download Markdown Report

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
B80

Site Health

Score: 80 / 100

Based on 8 categories, 0 sections

Fast site — your users get a smooth experience.

Several missing protections leave your users and data exposed.

Mostly accessible, but some users still face barriers.

Well-optimized for search — your content is discoverable.

Solid infrastructure — fast server responses across the board.

Mostly compliant — a few items need attention.

Rich content metadata — your pages look great everywhere.

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 sites average 74
+6 above average
Better than 87% of WordPress sites See full WordPress benchmark →
Cloudflare Bot Management sites average 74
+6 above average
Better than 92% of Cloudflare Bot Management sites See full Cloudflare Bot Management benchmark →

Top Priorities (5)

1

Content-Security-Policy header is missing

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

Security › Security Headers
2

HSTS header is missing

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

Security › Security Headers
3

No Content-Security-Policy header found

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

Security › Content Security Policy
4

1 link(s) with no accessible text

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

Accessibility › Link & Button Quality
5

4 image-only link(s) without alt text

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

Accessibility › Link & Button Quality
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

3

High impact, low effort — start here.

Strategic

2

High impact, requires investment.

Easy Improvements

0

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

0

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fw3.org)](https://beavercheck.com/results/6a64d8e9-1a9e-4ddb-841b-275b40d5fc1b)
<a href="https://beavercheck.com/results/6a64d8e9-1a9e-4ddb-841b-275b40d5fc1b"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fw3.org" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fw3.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. Addressing the critical issues below would have the most immediate impact on your user trust.

3 security gaps detected — browsers may warn visitors about your site.
2 accessibility issues exclude users who rely on assistive technology.

Conversion Barriers

3 warning

3 barrier(s) likely increasing bounce by ~6%.

Trust (2)

No HSTS header

+1% bounce

Returning visitors are briefly exposed to downgrade attacks on first request

Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains

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

Content (1)

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, …)

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

Return on Investment

€383 investment → €0.15/month returns + EUR 120,500,000 risk avoided

Payback period: > 2 years First-year ROI: -100%

Investment

€383

4h · 5 findings

Monthly returns

€0.15 /mo

~€1.79 / year

  • Bandwidth savings €0.15

Regulatory risk avoided

EUR 120,500,000

if kept compliant

  • ePrivacy Directive EUR 100,000,000
  • GDPR EUR 20,000,000
  • EAA EUR 500,000

€128 — 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

€383

4.5 developer hours at €85/hr

Based on European Union rates (€85/hr)

Quick wins
€128 3 fixes in ~90 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions
/hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

€10,041,667 / month at risk

~€120,500,002 / year if left unfixed

Compliance Risk

€120,500,000

ePrivacy DirectiveGDPREAA
  • No privacy policy link detected
    GDPR: EUR 10,000 – EUR 20,000,000
  • Trackers detected but no cookie policy found
    GDPR: EUR 5,000 – EUR 10,000,000
  • Trackers detected but no cookie policy found
    GDPR: EUR 10,000 – EUR 20,000,000

+3 more

Bandwidth Waste

€0.15 /mo

2017.5 MB/mo × 0.074 EUR/GB

  • Optimize transfer: save ~202 KB per page load
    Saves €0.15/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

Unique monthly visitors from your analytics

Purchases, signups, or key actions

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

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

96
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
100
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
100
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
100
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

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

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

2.50 s

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

4 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.05 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.

2.54 s

Detailed Report

Audit breakdown by category with detailed findings.

96

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.

RequestCache TTLTransfer Size
www.w3.org/cms-uploads/_920xAUTO_crop_center-center_none/w30c-pattern.jpeg120.0 s170.6 KiB
/cms-uploads/_920xAUTO_crop_center-center_none/ryan-quint...120.0 s108.1 KiB
/cms-uploads/_920xAUTO_crop_center-center_none/marvin-mey...120.0 s98.4 KiB
www.w3.org/cms-uploads/animation.mp4120.0 s48.5 KiB
www.w3.org/assets/website-2021/styles/core.css?ver=1.50.0 ms39.0 KiB
www.w3.org/assets/logos/w3c-2025/svg/w3c.svg0.0 ms31.0 KiB
www.w3.org/thumbnails/250/logos/organizations/86485.png?x-version=30.0 ms18.6 KiB
www.w3.org/assets/website-2021/js/main.js?ver=1.40.0 ms17.5 KiB
www.w3.org/thumbnails/250/logos/organizations/127220.png?x-version=10.0 ms17.4 KiB
www.w3.org/assets/website-2021/fonts/notosans/notosans-regular.woff20.0 ms17.2 KiB
www.w3.org/assets/website-2021/fonts/notosans/notosans-bold.woff20.0 ms17.1 KiB
www.w3.org/thumbnails/250/logos/organizations/33823.png?x-version=30.0 ms12.6 KiB
www.w3.org/thumbnails/250/logos/organizations/160564.png?x-version=10.0 ms11.2 KiB
www.w3.org/thumbnails/250/logos/organizations/10894.png?x-version=30.0 ms11.1 KiB
www.w3.org/assets/website-2021/styles/advanced.css?ver=1.50.0 ms10.0 KiB
www.w3.org/assets/website-2021/styles/print.css0.0 ms6.0 KiB
www.w3.org/thumbnails/250/logos/organizations/28169.png?x-version=40.0 ms3.5 KiB
www.w3.org/assets/website-2021/js/libraries/fontfaceobserver.js0.0 ms3.1 KiB
www.w3.org/assets/website-2021/js/members.js0.0 ms1.3 KiB
www.w3.org/assets/website-2021/svg/avatar.svg0.0 ms1.0 KiB
www.w3.org/assets/website-2021/svg/search.svg0.0 ms984 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.

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:33.807 source:map[type:text value:[unattributed]]]]

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
value: no origins were preconnected
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates
value: No additional origins are good candidates for preconnecting

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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
main#main > section.component > div.image > img main#main > section.component > div.image > img
www.w3.org/cms-uploads/_920xAUTO_crop_center-center_none/w30c-pattern.jpeg169.9 KiB155.0 KiB
main#main > section.component > div.image > img main#main > section.component > div.image > img
/cms-uploads/_920xAUTO_crop_center-center_none/ryan-quint...107.4 KiB92.5 KiB
main#main > section.component > div.image > img main#main > section.component > div.image > img
/cms-uploads/_920xAUTO_crop_center-center_none/marvin-mey...97.8 KiB82.8 KiB
Yubico div.component--members__grid > figure > div.l-box > img
www.w3.org/thumbnails/250/logos/organizations/86485.png?x-version=318.0 KiB15.6 KiB
Datadog div.component--members__grid > figure > div.l-box > img
www.w3.org/thumbnails/250/logos/organizations/127220.png?x-version=116.8 KiB14.2 KiB
Fundacion CTIC div.component--members__grid > figure > div.l-box > img
www.w3.org/thumbnails/250/logos/organizations/33823.png?x-version=312.0 KiB11.4 KiB
Institut National de Recherche en Informatique et en Automatique (Inria) div.component--members__grid > figure > div.l-box > img
www.w3.org/thumbnails/250/logos/organizations/10894.png?x-version=310.4 KiB9.6 KiB
Accessible by Design div.component--members__grid > figure > div.l-box > img
www.w3.org/thumbnails/250/logos/organizations/160564.png?x-version=110.6 KiB8.1 KiB

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

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: 150 ms 18.2 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: 150 ms 34.5 KiB
URLTransfer SizeEst Savings
www.w3.org/assets/website-2021/styles/core.css?ver=1.538.8 KiB34.5 KiB

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 6.0 KiB
URLTransfer SizeEst Savings
www.w3.org/assets/website-2021/js/main.js?ver=1.416.8 KiB6.0 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
W3C div.global-nav__inner > a.logo-link > span.logo > img
www.w3.org/assets/logos/w3c-2025/svg/w3c.svg
main#main > section.component > div.image > img main#main > section.component > div.image > img
www.w3.org/cms-uploads/_920xAUTO_crop_center-center_none/w30c-pattern.jpeg
main#main > section.component > div.image > img main#main > section.component > div.image > img
/cms-uploads/_920xAUTO_crop_center-center_none/ryan-quint...
main#main > section.component > div.image > img main#main > section.component > div.image > img
/cms-uploads/_920xAUTO_crop_center-center_none/marvin-mey...
Yubico div.component--members__grid > figure > div.l-box > img
www.w3.org/thumbnails/250/logos/organizations/86485.png?x-version=3
Accessible by Design div.component--members__grid > figure > div.l-box > img
www.w3.org/thumbnails/250/logos/organizations/160564.png?x-version=1
Datadog div.component--members__grid > figure > div.l-box > img
www.w3.org/thumbnails/250/logos/organizations/127220.png?x-version=1
Institut National de Recherche en Informatique et en Automatique (Inria) div.component--members__grid > figure > div.l-box > img
www.w3.org/thumbnails/250/logos/organizations/10894.png?x-version=3
Fundacion CTIC div.component--members__grid > figure > div.l-box > img
www.w3.org/thumbnails/250/logos/organizations/33823.png?x-version=3
Electronics and Telecommunications Research Institute (ETRI) div.component--members__grid > figure > div.l-box > img
www.w3.org/thumbnails/250/logos/organizations/28169.png?x-version=4

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

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 807 ms
URLTime Spent
w3.org/807 ms
www.w3.org/0.0 ms
Time to Interactive 2.5 s
Layout shift culprits
Optimize DOM size
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Max Potential First Input Delay 60 ms
Reduce unused JavaScript
Avoids enormous network payloads Total size was 657 KiB
JavaScript execution time 0.1 s
Minimizes main-thread work 0.8 s
Avoid long main-thread tasks 2 long tasks found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 20 ms
Server Backend Latencies 40 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 30 ms
INP breakdown
LCP request discovery
User Timing marks and measures
Avoid non-composited animations
Avoid large layout shifts
100

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.

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]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
Image elements have `[alt]` attributes
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
ARIA attributes are used as specified for the element's role
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
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
Touch targets have sufficient size and spacing.
`[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
`<video>` elements contain a `<track>` element with `[kind="captions"]`
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
`[role]`s are contained by their required parent element
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<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
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
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.
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
100

Best Practices

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
100

SEO

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

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Document has a meta description
Page has successful HTTP status code
Links have descriptive text
Links are crawlable
robots.txt is valid
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

99
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
100
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
100
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
100
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

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.

783 ms

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

866 ms

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.

783 ms

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

866 ms

Detailed Report

Audit breakdown by category with detailed findings.

99

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.

RequestCache TTLTransfer Size
www.w3.org/cms-uploads/_920xAUTO_crop_center-center_none/w30c-pattern.jpeg120.0 s170.6 KiB
/cms-uploads/_920xAUTO_crop_center-center_none/ryan-quint...120.0 s108.1 KiB
/cms-uploads/_920xAUTO_crop_center-center_none/marvin-mey...120.0 s98.4 KiB
www.w3.org/cms-uploads/animation.mp4120.0 s48.5 KiB
www.w3.org/assets/website-2021/styles/core.css?ver=1.50.0 ms39.3 KiB
www.w3.org/thumbnails/250/logos/organizations/131682.png?x-version=10.0 ms35.1 KiB
www.w3.org/assets/logos/w3c-2025/svg/w3c.svg0.0 ms31.1 KiB
www.w3.org/assets/website-2021/js/main.js?ver=1.40.0 ms17.5 KiB
www.w3.org/assets/website-2021/fonts/notosans/notosans-regular.woff20.0 ms17.2 KiB
www.w3.org/assets/website-2021/fonts/notosans/notosans-bold.woff20.0 ms17.1 KiB
www.w3.org/thumbnails/250/logos/organizations/7211.png?x-version=10.0 ms12.7 KiB
www.w3.org/assets/website-2021/styles/advanced.css?ver=1.50.0 ms10.4 KiB
www.w3.org/thumbnails/250/logos/organizations/98428.png?x-version=10.0 ms9.3 KiB
www.w3.org/thumbnails/250/logos/organizations/110285.png?x-version=10.0 ms7.5 KiB
www.w3.org/thumbnails/250/logos/organizations/116845.png?x-version=40.0 ms7.2 KiB
www.w3.org/assets/website-2021/styles/print.css0.0 ms6.0 KiB
www.w3.org/thumbnails/250/logos/organizations/154738.png?x-version=10.0 ms5.7 KiB
www.w3.org/assets/website-2021/js/libraries/fontfaceobserver.js0.0 ms3.5 KiB
www.w3.org/assets/website-2021/svg/github.svg0.0 ms1.6 KiB
www.w3.org/assets/website-2021/js/members.js0.0 ms1.3 KiB
www.w3.org/assets/website-2021/svg/mastodon.svg0.0 ms1.2 KiB
www.w3.org/assets/website-2021/svg/avatar.svg0.0 ms1.0 KiB
www.w3.org/assets/website-2021/svg/search.svg0.0 ms984 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.

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-VIDEO
nodeLabel: div.sidebar > div.sidebar__video > div.l-frame > video
path: 1,HTML,1,BODY,1,DIV,0,DIV,1,MAIN,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,0,DIV,0,VIDEO
selector: div.sidebar > div.sidebar__video > div.l-frame > video
snippet: <video loop="" muted="" playsinline="" preload="metadata" data-video="hero">

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
value: no origins were preconnected
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates
value: No additional origins are good candidates for preconnecting

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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
main#main > section.component > div.image > img main#main > section.component > div.image > img
www.w3.org/cms-uploads/_920xAUTO_crop_center-center_none/w30c-pattern.jpeg169.9 KiB142.4 KiB
main#main > section.component > div.image > img main#main > section.component > div.image > img
/cms-uploads/_920xAUTO_crop_center-center_none/ryan-quint...107.4 KiB79.9 KiB
main#main > section.component > div.image > img main#main > section.component > div.image > img
/cms-uploads/_920xAUTO_crop_center-center_none/marvin-mey...97.8 KiB70.2 KiB
1Password div.component--members__grid > figure > div.l-box > img
www.w3.org/thumbnails/250/logos/organizations/131682.png?x-version=134.4 KiB32.0 KiB
Web3D Consortium div.component--members__grid > figure > div.l-box > img
www.w3.org/thumbnails/250/logos/organizations/7211.png?x-version=112.0 KiB11.2 KiB
Capital One Financial div.component--members__grid > figure > div.l-box > img
www.w3.org/thumbnails/250/logos/organizations/98428.png?x-version=18.6 KiB7.7 KiB
Entersekt div.component--members__grid > figure > div.l-box > img
www.w3.org/thumbnails/250/logos/organizations/116845.png?x-version=46.5 KiB5.4 KiB
Taiwan Digital Publishing Forum div.component--members__grid > figure > div.l-box > img
www.w3.org/thumbnails/250/logos/organizations/110285.png?x-version=16.8 KiB5.2 KiB

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: 80 ms 32.5 KiB
URLTransfer SizeEst Savings
www.w3.org/assets/website-2021/styles/core.css?ver=1.538.7 KiB32.5 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: 10 ms 18.5 KiB

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 6.0 KiB
URLTransfer SizeEst Savings
www.w3.org/assets/website-2021/js/main.js?ver=1.416.8 KiB6.0 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
W3C div.global-nav__inner > a.logo-link > span.logo > img
www.w3.org/assets/logos/w3c-2025/svg/w3c.svg
main#main > section.component > div.image > img main#main > section.component > div.image > img
www.w3.org/cms-uploads/_920xAUTO_crop_center-center_none/w30c-pattern.jpeg
main#main > section.component > div.image > img main#main > section.component > div.image > img
/cms-uploads/_920xAUTO_crop_center-center_none/ryan-quint...
main#main > section.component > div.image > img main#main > section.component > div.image > img
/cms-uploads/_920xAUTO_crop_center-center_none/marvin-mey...
Taiwan Digital Publishing Forum div.component--members__grid > figure > div.l-box > img
www.w3.org/thumbnails/250/logos/organizations/110285.png?x-version=1
1Password div.component--members__grid > figure > div.l-box > img
www.w3.org/thumbnails/250/logos/organizations/131682.png?x-version=1
Entersekt div.component--members__grid > figure > div.l-box > img
www.w3.org/thumbnails/250/logos/organizations/116845.png?x-version=4
Capital One Financial div.component--members__grid > figure > div.l-box > img
www.w3.org/thumbnails/250/logos/organizations/98428.png?x-version=1
Web3D Consortium div.component--members__grid > figure > div.l-box > img
www.w3.org/thumbnails/250/logos/organizations/7211.png?x-version=1
Evinced Inc. div.component--members__grid > figure > div.l-box > img
www.w3.org/thumbnails/250/logos/organizations/154738.png?x-version=1

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

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 259 ms
URLTime Spent
w3.org/259 ms
www.w3.org/0.0 ms
Layout shift culprits
Optimize DOM size
Forced reflow
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Time to Interactive 0.9 s
Max Potential First Input Delay 20 ms
Reduce unused JavaScript
Avoids enormous network payloads Total size was 664 KiB
JavaScript execution time 0.0 s
Minimizes main-thread work 0.1 s
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 20 ms
Server Backend Latencies 40 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 1 layout shift found
INP breakdown
User Timing marks and measures
Avoid long main-thread tasks
Avoid non-composited animations
100

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.

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]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
Image elements have `[alt]` attributes
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
ARIA attributes are used as specified for the element's role
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
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
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
Touch targets have sufficient size and spacing.
`[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
`<video>` elements contain a `<track>` element with `[kind="captions"]`
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
`[role]`s are contained by their required parent element
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<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.
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.
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
100

Best Practices

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
100

SEO

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

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Document has a meta description
Page has successful HTTP status code
Links have descriptive text
Links are crawlable
robots.txt is valid
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback