B — https://www.php.net | BeaverCheck Audit

Site Health

Score: 80 / 100

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

HSTS header is missing

Security › Security Headers

No Content-Security-Policy header found

Security › Content Security Policy

1 button(s) with no accessible text

Accessibility › Link & Button Quality

1 image-only link(s) without alt text

Accessibility › Link & Button Quality

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.php.net)](https://beavercheck.com/results/8caf44a0-5db5-1873-1bc4-43b6f41d3ef9)

HTML

<a href="https://beavercheck.com/results/8caf44a0-5db5-1873-1bc4-43b6f41d3ef9"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.php.net" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fwww.php.net

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

100

Best Practices

100

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.

931 ms

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

1.15 s

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

198 ms

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

0.118

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

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

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.

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]

items: [map[node:map[type:text value:Total] score:0.118095] map[node:map[boundingRect:map[bottom:698 height:148 left:24 right:388 top:550 width:364] lhId:page-1-UL nodeLabel:8.5.4 · Changelog · Upgrading 8.4.19 · Changelog · Upgrading 8.3.30 · Changelog… path:1,HTML,1,BODY,4,DIV,0,DIV,0,DIV,3,UL selector:div#intro > div.container > div.hero > ul.hero__versions snippet:<ul class="hero__versions"> type:node] score:0.063542 subItems:map[items:[map[cause:Web font extra:map[type:url value:https://www.php.net/fonts/Fira/woff2/FiraSans-Medium.woff2]] map[cause:Web font extra:map[type:url value:https://www.php.net/fonts/Fira/woff2/FiraSans-BookItalic.woff2]]] type:subitems]] map[node:map[boundingRect:map[bottom:698 height:148 left:24 right:388 top:550 width:364] lhId:page-1-UL nodeLabel:8.5.4 · Changelog · Upgrading 8.4.19 · Changelog · Upgrading 8.3.30 · Changelog… path:1,HTML,1,BODY,4,DIV,0,DIV,0,DIV,3,UL selector:div#intro > div.container > div.hero > ul.hero__versions snippet:<ul class="hero__versions"> type:node] score:0.054553 subItems:map[items:[map[cause:Web font extra:map[type:url value:https://www.php.net/fonts/Fira/woff2/FiraSans-Book.woff2]]] type:subitems]]]

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.

URL	Est Savings
www.php.net/fonts/Font-Awesome/font/fontello.woff2?96103027	70 ms

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

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.

URL	Transfer Size	Duration
www.php.net/cached.php?t=1756715876&f=/styles/home.css	1.3 KiB
www.php.net/cached.php?t=1763575802&f=/styles/theme-medium.css	5.0 KiB
www.php.net/cached.php?t=1763585401&f=/styles/theme-base.css	6.6 KiB	175 ms
www.php.net/cached.php?t=1756715876&f=/fonts/Font-Awesome/css/fontello.css	1.1 KiB
www.php.net/cached.php?t=1756715876&f=/fonts/Fira/fira.css	700 B

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Request	Cache TTL	Transfer Size
www.php.net/fonts/Fira/woff2/FiraSans-BookItalic.woff2	86400.0 s	136.0 KiB
www.php.net/fonts/Fira/woff2/FiraSans-Medium.woff2	86400.0 s	130.0 KiB
www.php.net/fonts/Fira/woff2/FiraSans-Book.woff2	86400.0 s	129.0 KiB
www.php.net/fonts/Font-Awesome/font/fontello.woff2?96103027	86400.0 s	3.1 KiB
www.php.net/images/php8/logo_php8_5.svg	86400.0 s	1.7 KiB
www.php.net/images/to-top@2x.png	86400.0 s	1.2 KiB
www.php.net/images/logos/php-logo-white.svg	86400.0 s	752 B
www.php.net/images/bg-texture-00.svg	86400.0 s	363 B

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

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Element	Layout shift score
8.5.4 · Changelog · Upgrading 8.4.19 · Changelog · Upgrading 8.3.30 · Changelog… `div#intro > div.container > div.hero > ul.hero__versions`	0.064
8.5.4 · Changelog · Upgrading 8.4.19 · Changelog · Upgrading 8.3.30 · Changelog… `div#intro > div.container > div.hero > ul.hero__versions`	0.055

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

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

Estimated savings: 0.0 ms 2.8 KiB

URL	Transfer Size	Est Savings
www.php.net/cached.php?t=1768309801&f=/js/common.js	7.5 KiB	2.8 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: 0.0 ms 31.5 KiB

URL	Transfer Size	Est Savings
www.php.net/js/php-web.mjs	31.5 KiB	31.5 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

	URL
PHP 8.5 `ul.navbar__nav > li.navbar__item > a.navbar__link > img`	www.php.net/images/php8/logo_php8_5.svg

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

●Time to Interactive 2.7 s

●Document request latency

●Optimize DOM size

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Reduce unused CSS

●Avoids enormous network payloads Total size was 836 KiB

●JavaScript execution time 0.3 s

●Minimizes main-thread work 1.4 s

●Avoid long main-thread tasks 4 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 30 ms

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

○INP breakdown

○LCP request discovery

○User Timing marks and measures

○Avoid non-composited animations

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.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Failing Elements
html `html`

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

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

●Heading elements appear in a sequentially-descending order

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

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

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

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

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

Performance

Accessibility

100

Best Practices

100

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.

317 ms

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

580 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.187

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

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

580 ms

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.

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

items: [map[node:map[type:text value:Total] score:0.186908] map[node:map[boundingRect:map[bottom:9582 height:9040 left:90 right:1260 top:542 width:1170] lhId:page-1-DIV nodeLabel:12 Mar 2026 PHP 8.5.4 Released! The PHP development team announces the immedia… path:1,HTML,1,BODY,5,DIV selector:body.home > div#layout snippet:<div id="layout" class="clearfix"> type:node] score:0.186333 subItems:map[items:[map[cause:Web font extra:map[type:url value:https://www.php.net/fonts/Fira/woff2/FiraSans-Book.woff2]]] type:subitems]] map[node:map[boundingRect:map[bottom:292 height:22 left:315 right:677 top:270 width:362] lhId:page-5-STRONG nodeLabel:popular general-purpose scripting language path:1,HTML,1,BODY,4,DIV,0,DIV,0,DIV,1,P,1,STRONG selector:div.container > div.hero > p.hero__text > strong snippet:<strong> type:node] score:0.000575]]

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.

URL	Est Savings
www.php.net/fonts/Font-Awesome/font/fontello.woff2?96103027	75 ms

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

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.

URL	Transfer Size	Duration
www.php.net/cached.php?t=1756715876&f=/styles/home.css	1.3 KiB
www.php.net/cached.php?t=1763575802&f=/styles/theme-medium.css	5.0 KiB
www.php.net/cached.php?t=1763585401&f=/styles/theme-base.css	6.6 KiB	68 ms
www.php.net/cached.php?t=1756715876&f=/fonts/Font-Awesome/css/fontello.css	1.1 KiB
www.php.net/cached.php?t=1756715876&f=/fonts/Fira/fira.css	700 B

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Request	Cache TTL	Transfer Size
www.php.net/fonts/Fira/woff2/FiraSans-BookItalic.woff2	86400.0 s	136.0 KiB
www.php.net/fonts/Fira/woff2/FiraSans-Medium.woff2	86400.0 s	130.0 KiB
www.php.net/fonts/Fira/woff2/FiraSans-Book.woff2	86400.0 s	129.0 KiB
www.php.net/fonts/Font-Awesome/font/fontello.woff2?96103027	86400.0 s	3.1 KiB
www.php.net/images/php8/logo_php8_5.svg	86400.0 s	1.7 KiB
www.php.net/images/to-top@2x.png	86400.0 s	1.2 KiB
www.php.net/images/logos/php-logo-white.svg	86400.0 s	752 B
www.php.net/images/bg-texture-00.svg	86400.0 s	363 B

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

Diagnostics

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

Estimated savings: 0.0 ms 2.8 KiB

URL	Transfer Size	Est Savings
www.php.net/cached.php?t=1768309801&f=/js/common.js	7.5 KiB	2.8 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: 0.0 ms 31.5 KiB

URL	Transfer Size	Est Savings
www.php.net/js/php-web.mjs	31.5 KiB	31.5 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

	URL
PHP 8.5 `ul.navbar__nav > li.navbar__item > a.navbar__link > img`	www.php.net/images/php8/logo_php8_5.svg

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

Element	Layout shift score
12 Mar 2026 PHP 8.5.4 Released! The PHP development team announces the immedia… `body.home > div#layout`	0.186
popular general-purpose scripting language `div.container > div.hero > p.hero__text > strong`	0.001

●Document request latency

●Optimize DOM size

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Time to Interactive 0.6 s

●Max Potential First Input Delay 50 ms

●Minify CSS

●Reduce unused CSS

●Avoids enormous network payloads Total size was 885 KiB

●JavaScript execution time 0.0 s

●Minimizes main-thread work 0.3 s

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 30 ms

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

○INP breakdown

○LCP request discovery

○User Timing marks and measures

○Avoid long main-thread tasks

○Avoid non-composited animations

Accessibility

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
body.home > div.elephpants > div.images > a `body.home > div.elephpants > div.images > a`
body.home > div.elephpants > div.images > a `body.home > div.elephpants > div.images > 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.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Failing Elements
html `html`

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

●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

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

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

○Skip links are focusable.

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

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

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

100

SEO

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

Browse & Analyze

Learn

Results for https://www.php.net

Site Health

Top Priorities (5)

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Best practices

Best Practices

SEO

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Names and labels

Best practices

Best Practices

SEO

Keyboard Shortcuts