Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Detailed Report

Audit breakdown by category with detailed findings.

100

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

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
xdebug.org/fonts/IBMPlexSans-MediumItalic-Latin1.woff2	0.0 ms	18.3 KiB
xdebug.org/fonts/IBMPlexSans-SemiBoldItalic-Latin1.woff2	0.0 ms	17.9 KiB
xdebug.org/images/logos/seidengroup.svg	0.0 ms	17.7 KiB
xdebug.org/core2.css	0.0 ms	17.7 KiB
xdebug.org/fonts/IBMPlexSans-SemiBold-Latin1.woff2	0.0 ms	17.2 KiB
xdebug.org/fonts/IBMPlexSans-Medium-Latin1.woff2	0.0 ms	16.9 KiB
xdebug.org/fonts/IBMPlexSans-Regular-Latin1.woff2	0.0 ms	16.4 KiB
xdebug.org/images/logos/weCreate.svg	0.0 ms	13.3 KiB
xdebug.org/fonts/IBMPlexMono-Regular-Latin1.woff2	0.0 ms	13.3 KiB
xdebug.cloud/assets/images/logo.svg	0.0 ms	8.0 KiB
xdebug.org/images/logos/xdebug-cloud.svg	0.0 ms	7.9 KiB
xdebug.org/images/logos/private-packagist.svg	0.0 ms	6.0 KiB
xdebug.org/images/logos/tideways.svg	0.0 ms	5.8 KiB
xdebug.org/images/logos/uconnect.svg	0.0 ms	2.6 KiB
xdebug.org/images/logos/11com7.svg	0.0 ms	2.4 KiB
xdebug.org/images/logos/typo3.svg	0.0 ms	1.9 KiB
xdebug.cloud/assets/images/gradient.svg	0.0 ms	1.6 KiB
xdebug.org/images/logos/vema.svg	0.0 ms	1.2 KiB
xdebug.org/images/logos/io.svg	0.0 ms	1004 B
xdebug.org/images/logos/b13.svg	0.0 ms	596 B

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-DIV

nodeLabel: Xdebug Cloud is a Proxy-as-a-Service, which can help you with complexities with…

path: 1,HTML,1,BODY,2,MAIN,3,DIV

selector: body > main.content_width > div.front_advertisement

snippet: <div class="front_advertisement">

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.

URL	Transfer Size	Duration
xdebug.org/core2.css	17.7 KiB	80 ms

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.

URL	Est Savings
xdebug.org/fonts/IBMPlexSans-Medium-Latin1.woff2	15 ms
xdebug.org/fonts/IBMPlexSans-Regular-Latin1.woff2	10 ms
xdebug.org/fonts/IBMPlexSans-SemiBold-Latin1.woff2	10 ms
xdebug.org/fonts/IBMPlexSans-MediumItalic-Latin1.woff2	10 ms
xdebug.org/fonts/IBMPlexSans-SemiBoldItalic-Latin1.woff2	10 ms
xdebug.org/fonts/IBMPlexMono-Regular-Latin1.woff2	5.0 ms

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

Diagnostics

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 30 ms 13.1 KiB

URL	Transfer Size	Est Savings
xdebug.org/core2.css	17.6 KiB	13.1 KiB

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 3.2 KiB

URL	Transfer Size	Est Savings
xdebug.org/core2.css	17.7 KiB	3.2 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
Xdebug Cloud `body > main.content_width > div.front_advertisement > img`	xdebug.cloud/assets/images/logo.svg
Xdebug Cloud `ul.supporters > li.logo > a > img`	xdebug.org/images/logos/xdebug-cloud.svg
TYPO3 GmbH `ul.supporters > li.logo > a > img`	xdebug.org/images/logos/typo3.svg
Tideways `ul.supporters > li.logo > a > img`	xdebug.org/images/logos/tideways.svg
Seiden Group `ul.supporters > li.logo > a > img`	xdebug.org/images/logos/seidengroup.svg
VEMA eG `ul.supporters > li.logo > a > img`	xdebug.org/images/logos/vema.svg
weCreate `ul.supporters > li.logo > a > img`	xdebug.org/images/logos/weCreate.svg
11com7 `ul.supporters > li.logo > a > img`	xdebug.org/images/logos/11com7.svg
b13 `div > div > a > img`	xdebug.org/images/logos/b13.svg
IO Belgium `div > div > a > img`	xdebug.org/images/logos/io.svg
Private Packagist `ul.supporters > li.logo > a > img`	xdebug.org/images/logos/private-packagist.svg
uConnect `ul.supporters > li.logo > a > img`	xdebug.org/images/logos/uconnect.svg

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

●Layout shift culprits

●Optimize DOM size

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Time to Interactive 0.5 s

●Max Potential First Input Delay 20 ms

●Minify JavaScript

●Reduce unused JavaScript

●Avoids enormous network payloads Total size was 199 KiB

●JavaScript execution time 0.0 s

●Minimizes main-thread work 0.2 s

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 10 ms

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

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

○User Timing marks and measures

○Avoid long main-thread tasks

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

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
b13 `li.both > div > div > a`
IO Belgium `li.both > div > div > a`
This site and all of its contents are Copyright © 2002-2026 by Derick Rethans. … `body > footer.content_width > p`

These are opportunities to improve the legibility of your content.

Navigation

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 about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Projects `body > main.content_width > div.front_announcements > h3`

These are opportunities to improve keyboard navigation in your application.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These are opportunities to improve the interpretation of your content by users in different locales.

Best practices

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 about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

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-hidden="true"]` is not present on the document `<body>`

●Image elements have `[alt]` attributes

●`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

●Definition list items are wrapped in `<dl>` elements

●Document has a `<title>` element

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

●Document has a main landmark.

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

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

○ARIA attributes are used as specified for the element's role

○Deprecated ARIA roles were not used

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted ARIA attributes

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

○`[aria-*]` attributes have valid values

○`[aria-*]` attributes are valid and not misspelled

○Buttons have an accessible name

○The page contains a heading, skip link, or landmark region

○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

●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

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

○robots.txt is valid

○Document has a valid `rel=canonical`