B — https://wordpress.org | BeaverCheck Audit

Site Health

Score: 82 / 100 +2

Based on 8 categories, 0 sections

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.

Top Priorities (5)

Content-Security-Policy header is missing

Security › Security Headers

No Content-Security-Policy header found

Security › Content Security Policy

1 link(s) with no accessible text

Accessibility › Link & Button Quality

Cross-Origin-Embedder-Policy header is missing

Security › Security Headers

Cross-Origin-Opener-Policy header is missing

Security › Security Headers

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwordpress.org)](https://beavercheck.com/results/4cf5d04e-fd80-48c5-8bf8-c9132fe6a67b)

HTML

<a href="https://beavercheck.com/results/4cf5d04e-fd80-48c5-8bf8-c9132fe6a67b"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwordpress.org" alt="BeaverCheck Score"></a>

Image URL

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

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Recent Trends

Performance stable →

TTFB stable →

63ms

FCP stable →

2.0s

LCP stable →

8.0s

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

67 -5

Performance

96 +4

Accessibility

96 -4

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.

1.63 s

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

7.78 s

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

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

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

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

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

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

	URL	Resource Size	Est Savings
div.wp-block-columns > div.wp-block-column > figure.wp-block-image > img.wp-image-48980 `div.wp-block-columns > div.wp-block-column > figure.wp-block-image > img.wp-image-48980`	i0.wp.com/wordpress.org/files/2025/12/wporg-69-new.png?resize=768%2C540&ssl=1	182.1 KiB	174.9 KiB
A black and white photograph of excited, applauding attendees in the audience a… `div.wp-block-columns > div.wp-block-column > figure.wp-block-image > img.wp-image-39810`	/wordpress.org/files/2024/04/photo-community-1.png?resize...	154.5 KiB	149.5 KiB
div.wp-block-group > figure.wp-block-image > a > img.wp-image-50259 `div.wp-block-group > figure.wp-block-image > a > img.wp-image-50259`	i0.wp.com/wordpress.org/files/2026/03/WCA26-Icon-Purple-White.png?w=705&ssl=1	95.1 KiB	94.8 KiB
div.wp-block-columns > div.wp-block-column > figure.wp-block-image > img.wp-image-48981 `div.wp-block-columns > div.wp-block-column > figure.wp-block-image > img.wp-image-48981`	i0.wp.com/wordpress.org/files/2025/12/wporg-69-publish.png?w=720&ssl=1	96.0 KiB	89.4 KiB
div.wp-block-group > div.wp-block-group > figure.wp-block-image > img.wp-image-22641 `div.wp-block-group > div.wp-block-group > figure.wp-block-image > img.wp-image-22641`	/wordpress.org/files/2023/10/showcase-middle-row.png?resi...	92.4 KiB	87.4 KiB
div.wp-block-group > div.wp-block-group > figure.wp-block-image > img.wp-image-22644 `div.wp-block-group > div.wp-block-group > figure.wp-block-image > img.wp-image-22644`	/wordpress.org/files/2023/10/showcase-top-row-full.png?re...	87.2 KiB	82.2 KiB
div.wp-block-columns > div.wp-block-column > figure.wp-block-image > img.wp-image-39758 `div.wp-block-columns > div.wp-block-column > figure.wp-block-image > img.wp-image-39758`	i0.wp.com/wordpress.org/files/2024/04/brush.png?resize=768%2C207&ssl=1	58.5 KiB	55.7 KiB
div.wp-block-columns > div.wp-block-column > figure.wp-block-image > img.wp-image-48978 `div.wp-block-columns > div.wp-block-column > figure.wp-block-image > img.wp-image-48978`	i0.wp.com/wordpress.org/files/2025/12/wporg-69-build.png?w=720&ssl=1	49.9 KiB	43.8 KiB
div.wp-block-group > div.wp-block-group > figure.wp-block-image > img.wp-image-22642 `div.wp-block-group > div.wp-block-group > figure.wp-block-image > img.wp-image-22642`	/wordpress.org/files/2023/10/showcase-bottom-row.png?resi...	44.1 KiB	40.0 KiB

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

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]

items: [map[duration:368.697 label:Time to first byte subpart:timeToFirstByte] map[duration:2165.109 label:Element render delay subpart:elementRenderDelay]]

lhId: page-9-H1

nodeLabel: Meet WordPress

path: 1,HTML,1,BODY,2,DIV,1,MAIN,1,DIV,0,DIV,0,DIV,0,H1

selector: div#intro > div.wp-block-columns > div.wp-block-column > h1.wp-block-heading

snippet: <h1 class="wp-block-heading" style="font-size:70px">

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.

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

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.

URL	Transfer Size	Duration
/wp-content/mu-plugins/pub-sync/global-fonts/NotoSerif/No...	42.3 KiB	150 ms
/wp-content/mu-plugins/pub-sync/global-fonts/NotoSerif/No...	32.7 KiB	150 ms
/wp-content/mu-plugins/pub-sync/global-fonts/NotoSerif/No...	33.6 KiB	300 ms
/wp-content/themes/wporg-parent-2021/build/block-styles.c...	3.7 KiB
/wp-content/mu-plugins/pub-sync/global-fonts/style.css?ve...	1.9 KiB
/wp-content/mu-plugins/pub-sync/blocks/global-header-foot...	0 B
/wp-content/themes/wporg-main-2022/build/style/style-inde...	0 B
wordpress.org/wp-includes/css/dashicons.min.css?ver=7.1-alpha-62213	0 B
wordpress.org/wp-content/themes/wporg-parent-2021/build/style.css?ver=1748271785	0 B
/wp-content/plugins/gutenberg/build/styles/block-library/...	2.8 KiB

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.

TTI

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

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.

Estimated savings: 530 ms 107.9 KiB

URL	Transfer Size	Est Savings
/wp-content/mu-plugins/pub-sync/global-fonts/NotoSerif/No...	42.0 KiB	42.0 KiB
/wp-content/mu-plugins/pub-sync/global-fonts/NotoSerif/No...	33.4 KiB	33.4 KiB
/wp-content/mu-plugins/pub-sync/global-fonts/NotoSerif/No...	32.4 KiB	32.4 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Estimated savings: 1.3 s 130.9 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-CG6GJ50G8J&cx=c&gtm=4e6431	170.9 KiB	67.3 KiB
www.googletagmanager.com/gtm.js?id=GTM-P24PF4B	130.4 KiB	63.6 KiB

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

●Use efficient cache lifetimes

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●Forced reflow

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

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

●User Timing marks and measures 5 user timings

●JavaScript execution time 0.4 s

●Minimizes main-thread work 1.0 s

●Avoid long main-thread tasks 3 long tasks found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 30 ms

●Server Backend Latencies 130 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 120 ms

○INP breakdown

○LCP request discovery

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

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Failing Elements
div.wp-block-group > div.wp-block-group > figure.wp-block-image > a `div.wp-block-group > div.wp-block-group > figure.wp-block-image > a`

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.

○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

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

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

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●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 input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○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

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

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

Best Practices

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Source	Description
wordpress.org/wp-content/themes/wporg-parent-2021/build/style.css?ver=1748271785	`Failed to load resource: the server responded with a status of 429 ()`
wordpress.org/wp-includes/css/dashicons.min.css?ver=7.1-alpha-62213	`Failed to load resource: the server responded with a status of 429 ()`
/wp-content/themes/wporg-main-2022/build/style/style-inde...	`Failed to load resource: the server responded with a status of 429 ()`
/wp-content/mu-plugins/pub-sync/blocks/global-header-foot...	`Failed to load resource: the server responded with a status of 429 ()`
/wp-content/mu-plugins/pub-sync/blocks/global-header-foot...	`Failed to load resource: the server responded with a status of 429 ()`
wordpress.org/files/2023/10/NASA-1.png	`Failed to load resource: the server responded with a status of 429 ()`
wordpress.org/files/2023/10/tech-crunch.png	`Failed to load resource: the server responded with a status of 429 ()`
/wp-content/plugins/gutenberg/build/modules/block-library...	`Failed to load resource: the server responded with a status of 429 ()`
wordpress.org/wp-content/themes/wporg-parent-2021/build/print.css?ver=1748271785	`Failed to load resource: the server responded with a status of 429 ()`
/wp-content/mu-plugins/pub-sync/blocks/time/build/view.js...	`Failed to load resource: the server responded with a status of 429 ()`
wordpress.org/wp-content/themes/wporg-parent-2021/images/dots-banner.svg	`Failed to load resource: the server responded with a status of 429 ()`
/wp-content/mu-plugins/pub-sync/global-fonts/Inter/Inter-...	`Failed to load resource: the server responded with a status of 429 ()`
wordpress.org/lang-guess/lang-guess-ajax.php?uri=%252F&locale=en_US	`Failed to load resource: the server responded with a status of 429 ()`
wordpress.org/wp-includes/js/wp-emoji-release.min.js?ver=7.1-alpha-62213	`Failed to load resource: the server responded with a status of 429 ()`

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

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

SEO

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

Content Best Practices

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

Link destination	Link Text
asia.wordcamp.org/2026/	Learn more

Format your HTML in a way that enables crawlers to better understand your app’s content.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links are crawlable

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

○robots.txt is valid

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

Accessibility

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.

380 ms

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

905 ms

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

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

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

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

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

	URL	Resource Size	Est Savings
A black and white photograph of excited, applauding attendees in the audience a… `div.wp-block-columns > div.wp-block-column > figure.wp-block-image > img.wp-image-39810`	i0.wp.com/wordpress.org/files/2024/04/photo-community-1.png?w=1216&ssl=1	356.0 KiB	333.7 KiB
div.wp-block-group > div.wp-block-group > figure.wp-block-image > img.wp-image-22641 `div.wp-block-group > div.wp-block-group > figure.wp-block-image > img.wp-image-22641`	/wordpress.org/files/2023/10/showcase-middle-row.png?resi...	333.1 KiB	278.7 KiB
div.wp-block-group > div.wp-block-group > figure.wp-block-image > img.wp-image-22644 `div.wp-block-group > div.wp-block-group > figure.wp-block-image > img.wp-image-22644`	/wordpress.org/files/2023/10/showcase-top-row-full.png?re...	304.0 KiB	250.2 KiB
div.wp-block-columns > div.wp-block-column > figure.wp-block-image > img.wp-image-48980 `div.wp-block-columns > div.wp-block-column > figure.wp-block-image > img.wp-image-48980`	i0.wp.com/wordpress.org/files/2025/12/wporg-69-new.png?w=1080&ssl=1	158.7 KiB	124.1 KiB
div.wp-block-columns > div.wp-block-column > figure.wp-block-image > img.wp-image-39758 `div.wp-block-columns > div.wp-block-column > figure.wp-block-image > img.wp-image-39758`	i0.wp.com/wordpress.org/files/2024/04/brush.png?w=1198&ssl=1	127.8 KiB	114.3 KiB
div.wp-block-group > div.wp-block-group > figure.wp-block-image > img.wp-image-22642 `div.wp-block-group > div.wp-block-group > figure.wp-block-image > img.wp-image-22642`	/wordpress.org/files/2023/10/showcase-bottom-row.png?resi...	148.9 KiB	105.8 KiB
div.wp-block-group > figure.wp-block-image > a > img.wp-image-50259 `div.wp-block-group > figure.wp-block-image > a > img.wp-image-50259`	i0.wp.com/wordpress.org/files/2026/03/WCA26-Icon-Purple-White.png?w=705&ssl=1	95.1 KiB	94.6 KiB
div.wp-block-columns > div.wp-block-column > figure.wp-block-image > img.wp-image-48981 `div.wp-block-columns > div.wp-block-column > figure.wp-block-image > img.wp-image-48981`	i0.wp.com/wordpress.org/files/2025/12/wporg-69-publish.png?w=720&ssl=1	96.0 KiB	82.5 KiB
div.wp-block-columns > div.wp-block-column > figure.wp-block-image > img.wp-image-48978 `div.wp-block-columns > div.wp-block-column > figure.wp-block-image > img.wp-image-48978`	i0.wp.com/wordpress.org/files/2025/12/wporg-69-build.png?w=720&ssl=1	49.9 KiB	37.4 KiB

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.

title: Preconnected origins

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.

URL	Transfer Size
/wp-content/plugins/gutenberg/build/styles/block-library/...	0 B
/wp-content/mu-plugins/pub-sync/blocks/global-header-foot...	0 B
/wp-content/themes/wporg-main-2022/build/style/style-inde...	0 B
wordpress.org/wp-includes/css/dashicons.min.css?ver=7.1-alpha-62213	0 B
wordpress.org/wp-content/themes/wporg-parent-2021/build/style.css?ver=1748271785	0 B
/wp-content/themes/wporg-parent-2021/build/block-styles.c...	0 B
/wp-content/mu-plugins/pub-sync/global-fonts/style.css?ve...	0 B

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

Diagnostics

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Estimated savings: 0.0 ms 131.5 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-CG6GJ50G8J&cx=c&gtm=4e6431	170.9 KiB	67.9 KiB
www.googletagmanager.com/gtm.js?id=GTM-P24PF4B	130.4 KiB	63.6 KiB

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

●Use efficient cache lifetimes

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Time to Interactive 1.2 s

●Max Potential First Input Delay 60 ms

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Avoids enormous network payloads Total size was 2,031 KiB

●User Timing marks and measures 5 user timings

●JavaScript execution time 0.1 s

●Minimizes main-thread work 0.2 s

●Avoid long main-thread tasks 1 long task found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 30 ms

●Server Backend Latencies 120 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 120 ms

○INP breakdown

○LCP request discovery

○Avoid non-composited animations

○Avoid large layout shifts

Accessibility

Contrast

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Failing Elements
EVENTS `ul.is-3-column > li > div.wp-block-wporg-latest-news__details > a.wp-block-wporg-latest-news__category`

These are opportunities to improve the legibility of your content.

Names and labels

Failing Elements
div.wp-block-group > div.wp-block-group > figure.wp-block-image > a `div.wp-block-group > div.wp-block-group > figure.wp-block-image > a`

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.

○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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Form elements have associated labels

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

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

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

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

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

○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

○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

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

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

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

Best Practices

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Source	Description
/wp-content/plugins/gutenberg/build/styles/block-library/...	`Failed to load resource: the server responded with a status of 429 ()`
/wp-content/mu-plugins/pub-sync/global-fonts/Inter/Inter-...	`Failed to load resource: the server responded with a status of 429 ()`
/wp-content/mu-plugins/pub-sync/global-fonts/EB-Garamond/...	`Failed to load resource: the server responded with a status of 429 ()`
/wp-content/mu-plugins/pub-sync/global-fonts/style.css?ve...	`Failed to load resource: the server responded with a status of 429 ()`
/wp-content/themes/wporg-parent-2021/build/block-styles.c...	`Failed to load resource: the server responded with a status of 429 ()`
wordpress.org/wp-content/themes/wporg-parent-2021/build/style.css?ver=1748271785	`Failed to load resource: the server responded with a status of 429 ()`
wordpress.org/wp-includes/css/dashicons.min.css?ver=7.1-alpha-62213	`Failed to load resource: the server responded with a status of 429 ()`
/wp-content/themes/wporg-main-2022/build/style/style-inde...	`Failed to load resource: the server responded with a status of 429 ()`
/wp-content/mu-plugins/pub-sync/blocks/global-header-foot...	`Failed to load resource: the server responded with a status of 429 ()`
/wp-content/mu-plugins/pub-sync/blocks/global-header-foot...	`Failed to load resource: the server responded with a status of 429 ()`
/wp-content/plugins/gutenberg/build/modules/interactivity...	`Failed to load resource: the server responded with a status of 429 ()`
wordpress.org/files/2022/08/Time-Magazine.png	`Failed to load resource: the server responded with a status of 429 ()`
wordpress.org/files/2023/10/NASA-1.png	`Failed to load resource: the server responded with a status of 429 ()`
wordpress.org/files/2023/10/tech-crunch.png	`Failed to load resource: the server responded with a status of 429 ()`
/wp-content/plugins/gutenberg/build/modules/block-library...	`Failed to load resource: the server responded with a status of 429 ()`
wordpress.org/wp-content/themes/wporg-parent-2021/build/print.css?ver=1748271785	`Failed to load resource: the server responded with a status of 429 ()`
/wp-content/mu-plugins/pub-sync/blocks/language-suggest/b...	`Failed to load resource: the server responded with a status of 429 ()`
/wp-content/mu-plugins/pub-sync/blocks/time/build/view.js...	`Failed to load resource: the server responded with a status of 429 ()`
wordpress.org/wp-includes/js/wp-emoji-release.min.js?ver=7.1-alpha-62213	`Failed to load resource: the server responded with a status of 429 ()`

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

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

SEO

Content Best Practices

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

Link destination	Link Text
asia.wordcamp.org/2026/	Learn more

Format your HTML in a way that enables crawlers to better understand your app’s content.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links are crawlable

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

○robots.txt is valid

Browse & Analyze

Learn

Results for https://wordpress.org

Site Health

Top Priorities (5)

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Names and labels

Best Practices

General

SEO

Content Best Practices

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Contrast

Names and labels

Best Practices

General

SEO

Content Best Practices

Keyboard Shortcuts