https://git.sr.ht/~sircmpwn/linux/blame/master/MAINTAINERS
?
Performance
?
Accessibility
?
Performance
?
Accessibility
0–49 50–89 90–100

There were issues affecting this run of Lighthouse:

  • The page provided is not HTML (served as MIME type ).
?
Performance
Metrics
First Contentful Paint
Error!
Required traces gatherer did not run.
Speed Index
Error!
Required traces gatherer did not run.
Largest Contentful Paint
Error!
Required traces gatherer did not run.
Time to Interactive
Error!
Required traces gatherer did not run.
Total Blocking Time
Error!
Required traces gatherer did not run.
Cumulative Layout Shift
Error!
Required traces gatherer did not run.
Values are estimated and may vary. The performance score is calculated directly from these metrics.See calculator.
OpportunitiesThese suggestions can help your page load faster. They don't directly affect the Performance score.
Opportunity
Estimated Savings
Eliminate render-blocking resources
Error!
Required TagsBlockingFirstPaint gatherer did not run.
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.
Properly size images
Error!
Required ImageElements gatherer did not run.
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.
Defer offscreen images
Error!
Required ImageElements gatherer did not run.
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.
Minify CSS
Error!
Required CSSUsage gatherer did not run.
Minifying CSS files can reduce network payload sizes. Learn more.
Minify JavaScript
Error!
Required ScriptElements gatherer did not run.
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.
Remove unused CSS
Error!
Required CSSUsage gatherer did not run.
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.
Remove unused JavaScript
Error!
Required JsUsage gatherer did not run.
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Efficiently encode images
Error!
Required OptimizedImages gatherer did not run.
Optimized images load faster and consume less cellular data. Learn more.
Serve images in next-gen formats
Error!
Required OptimizedImages gatherer did not run.
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.
Enable text compression
Error!
Required ResponseCompression gatherer did not run.
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.
Preconnect to required origins
Error!
Required devtoolsLogs gatherer did not run.
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.
Initial server response time was short
Error!
Required devtoolsLogs gatherer did not run.
Keep the server response time for the main document short because all other requests depend on it. Learn more.
Avoid multiple page redirects
Error!
Required devtoolsLogs gatherer did not run.
Redirects introduce additional delays before the page can be loaded. Learn more.
Preload key requests
Error!
Required devtoolsLogs gatherer did not run.
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load. Learn more.
Use HTTP/2
Error!
Required devtoolsLogs gatherer did not run.
HTTP/2 offers many benefits over HTTP/1.1, including binary headers, multiplexing, and server push. Learn more.
Use video formats for animated content
Error!
Required devtoolsLogs gatherer did not run.
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more
Remove duplicate modules in JavaScript bundles
Error!
Required devtoolsLogs gatherer did not run.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Error!
Required devtoolsLogs gatherer did not run.
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn More
DiagnosticsMore information about the performance of your application. These numbers don't directly affect the Performance score.
Avoids enormous network payloads Error!
Required devtoolsLogs gatherer did not run.
Large network payloads cost users real money and are highly correlated with long load times. Learn more.
Uses efficient cache policy on static assets Error!
Required devtoolsLogs gatherer did not run.
A long cache lifetime can speed up repeat visits to your page. Learn more.
Avoids an excessive DOM size Error!
Required DOMStats gatherer did not run.
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.
Avoid chaining critical requests Error!
Required devtoolsLogs gatherer did not run.
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.
User Timing marks and measures Error!
Required traces gatherer did not run.
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.
JavaScript execution time Error!
Required traces gatherer did not run.
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.
Minimizes main-thread work Error!
Required traces gatherer did not run.
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more
All text remains visible during webfont loads Error!
Required devtoolsLogs gatherer did not run.
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.
Keep request counts low and transfer sizes small Error!
Required devtoolsLogs gatherer did not run.
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Minimize third-party usage Error!
Required traces gatherer did not run.
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.
Largest Contentful Paint element Error!
Required traces gatherer did not run.
This is the largest contentful element painted within the viewport. Learn More
Avoid large layout shifts Error!
Required TraceElements gatherer did not run.
These DOM elements contribute most to the CLS of the page.
Uses passive listeners to improve scrolling performance Error!
Required ConsoleMessages gatherer did not run.
Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn more.
Avoids document.write() Error!
Required ConsoleMessages gatherer did not run.
For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of seconds. Learn more.
Avoid long main-thread tasks Error!
Required traces gatherer did not run.
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more
Avoid non-composited animations Error!
Required TraceElements gatherer did not run.
Animations which are not composited can be janky and increase CLS. Learn more
Passed audits (1)
Avoids large JavaScript libraries with smaller alternatives 0 large libraries found
Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size. Learn more.
?
Accessibility
These checks highlight opportunities to improve the accessibility of your web app. Only a subset of accessibility issues can be automatically detected so manual testing is also encouraged.
NavigationThese are opportunities to improve keyboard navigation in your application.
[accesskey] values are unique Error!
Required Accessibility gatherer did not run.
Access keys let users quickly focus a part of the page. For proper navigation, each access key must be unique. Learn more.
The page contains a heading, skip link, or landmark region Error!
Required Accessibility gatherer did not run.
Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more.
[id] attributes on active, focusable elements are unique Error!
Required Accessibility gatherer did not run.
All focusable elements must have a unique `id` to ensure that they're visible to assistive technologies. Learn more.
Heading elements appear in a sequentially-descending order Error!
Required Accessibility gatherer did not run.
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more.
No element has a [tabindex] value greater than 0 Error!
Required Accessibility gatherer did not run.
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more.
ARIAThese are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
[aria-*] attributes match their roles Error!
Required Accessibility gatherer did not run.
Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn more.
[aria-hidden="true"] is not present on the document <body> Error!
Required Accessibility gatherer did not run.
Assistive technologies, like screen readers, work inconsistently when `aria-hidden="true"` is set on the document `<body>`. Learn more.
[aria-hidden="true"] elements do not contain focusable descendents Error!
Required Accessibility gatherer did not run.
Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn more.
ARIA input fields have accessible names Error!
Required Accessibility gatherer did not run.
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more.
[role]s have all required [aria-*] attributes Error!
Required Accessibility gatherer did not run.
Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more.
Elements with an ARIA [role] that require children to contain a specific [role] have all required children. Error!
Required Accessibility gatherer did not run.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more.
[role]s are contained by their required parent element Error!
Required Accessibility gatherer did not run.
Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more.
[role] values are valid Error!
Required Accessibility gatherer did not run.
ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more.
ARIA toggle fields have accessible names Error!
Required Accessibility gatherer did not run.
When a toggle field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more.
[aria-*] attributes have valid values Error!
Required Accessibility gatherer did not run.
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more.
[aria-*] attributes are valid and not misspelled Error!
Required Accessibility gatherer did not run.
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more.
ARIA IDs are unique Error!
Required Accessibility gatherer did not run.
The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn more.
Names and labelsThese 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.
Buttons have an accessible name Error!
Required Accessibility gatherer did not run.
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn more.
Document has a <title> element Error!
Required Accessibility gatherer did not run.
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more.
No form fields have multiple labels Error!
Required Accessibility gatherer did not run.
Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either the first, the last, or all of the labels. Learn more.
<frame> or <iframe> elements have a title Error!
Required Accessibility gatherer did not run.
Screen reader users rely on frame titles to describe the contents of frames. Learn more.
Image elements have [alt] attributes Error!
Required Accessibility gatherer did not run.
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.
<input type="image"> elements have [alt] text Error!
Required Accessibility gatherer did not run.
When an image is being used as an `<input>` button, providing alternative text can help screen reader users understand the purpose of the button. Learn more.
Form elements have associated labels Error!
Required Accessibility gatherer did not run.
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more.
Links have a discernible name Error!
Required Accessibility gatherer did not run.
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 more.
<object> elements have [alt] text Error!
Required Accessibility gatherer did not run.
Screen readers cannot translate non-text content. Adding alt text to `<object>` elements helps screen readers convey meaning to users. Learn more.
ContrastThese are opportunities to improve the legibility of your content.
Background and foreground colors have a sufficient contrast ratio Error!
Required Accessibility gatherer did not run.
Low-contrast text is difficult or impossible for many users to read. Learn more.
Tables and listsThese are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
<dl>'s contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements. Error!
Required Accessibility gatherer did not run.
When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn more.
Definition list items are wrapped in <dl> elements Error!
Required Accessibility gatherer did not run.
Definition list items (`<dt>` and `<dd>`) must be wrapped in a parent `<dl>` element to ensure that screen readers can properly announce them. Learn more.
Presentational <table> elements avoid using <th>, <caption> or the [summary] attribute. Error!
Required Accessibility gatherer did not run.
A table being used for layout purposes should not include data elements, such as the th or caption elements or the summary attribute, because this can create a confusing experience for screen reader users. Learn more.
Lists contain only <li> elements and script supporting elements (<script> and <template>). Error!
Required Accessibility gatherer did not run.
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more.
List items (<li>) are contained within <ul> or <ol> parent elements Error!
Required Accessibility gatherer did not run.
Screen readers require list items (`<li>`) to be contained within a parent `<ul>` or `<ol>` to be announced properly. Learn more.
Cells in a <table> element that use the [headers] attribute refer to table cells within the same table. Error!
Required Accessibility gatherer did not run.
Screen readers have features to make navigating tables easier. Ensuring `<td>` cells using the `[headers]` attribute only refer to other cells in the same table may improve the experience for screen reader users. Learn more.
<th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe. Error!
Required Accessibility gatherer did not run.
Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells may improve the experience for screen reader users. Learn more.
Internationalization and localizationThese are opportunities to improve the interpretation of your content by users in different locales.
<html> element has a [lang] attribute Error!
Required Accessibility gatherer did not run.
If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more.
<html> element has a valid value for its [lang] attribute Error!
Required Accessibility gatherer did not run.
Specifying a valid BCP 47 language helps screen readers announce text properly. Learn more.
[lang] attributes have a valid value Error!
Required Accessibility gatherer did not run.
Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn more.
Best practicesThese items highlight common accessibility best practices.
The document does not use <meta http-equiv="refresh"> Error!
Required Accessibility gatherer did not run.
Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more.
[user-scalable="no"] is not used in the <meta name="viewport"> element and the [maximum-scale] attribute is not less than 5. Error!
Required Accessibility gatherer did not run.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more.
Audio and videoThese are opportunities to provide alternative content for audio and video. This may improve the experience for users with hearing or vision impairments.
<video> elements contain a <track> element with [kind="captions"] Error!
Required Accessibility gatherer did not run.
When a video provides a caption it is easier for deaf and hearing impaired users to access its information. Learn more.
<video> elements contain a <track> element with [kind="description"] Error!
Required Accessibility gatherer did not run.
Audio descriptions provide relevant information for videos that dialogue cannot, such as facial expressions and scenes. Learn more.
Additional items to manually check (10) These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
The page has a logical tab order
Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more.
Interactive controls are keyboard focusable
Custom interactive controls are keyboard focusable and display a focus indicator. Learn more.
Interactive elements indicate their purpose and state
Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive elements. Learn more.
The user's focus is directed to new content added to the page
If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn more.
User focus is not accidentally trapped in a region
A user can tab into and out of any control or region without accidentally trapping their focus. Learn more.
Custom controls have associated labels
Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more.
Custom controls have ARIA roles
Custom interactive controls have appropriate ARIA roles. Learn more.
Visual order on the page follows DOM order
DOM order matches the visual order, improving navigation for assistive technology. Learn more.
Offscreen content is hidden from assistive technology
Offscreen content is hidden with display: none or aria-hidden=true. Learn more.
HTML5 landmark elements are used to improve navigation
Landmark elements (<main>, <nav>, etc.) are used to improve the keyboard navigation of the page for assistive technology. Learn more.