C — https://www.eclipse.org | BeaverCheck Audit

Site Health

Score: 79 / 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)

1 button(s) with no accessible text

Accessibility › Link & Button Quality

2 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

External link from fonts.googleapis.com lacks integrity attribute

Security › Subresource Integrity

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.eclipse.org)](https://beavercheck.com/results/623e4091-a183-8080-6580-ea854b18ba25)

HTML

<a href="https://beavercheck.com/results/623e4091-a183-8080-6580-ea854b18ba25"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.eclipse.org" alt="BeaverCheck Score"></a>

Image URL

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

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

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.

6.40 s

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

11.38 s

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

368 ms

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

0.172

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

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

11.41 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.171595] map[node:map[boundingRect:map[bottom:1199 height:960 left:0 right:412 top:240 width:412] lhId:page-4-SECTION nodeLabel:Global community, European foundation The Eclipse Foundation empowers our glob… path:1,HTML,1,BODY,6,MAIN,0,SECTION selector:body.landing-page > main#main > section.featured-jumbotron snippet:<section class="featured-jumbotron fade-group bg bg-home"> type:node] score:0.171595]]

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
/public/fonts/vendor/@fortawesome/fontawesome-free/webfa-...	160 ms
/public/fonts/vendor/@fortawesome/fontawesome-free/webfa-...	130 ms

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

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:72.339 source:map[column:244319 line:1 type:source-location url:https://www.eclipse.org/public/js/main.js?v1.0?v=1775577514 urlProvider:network]] map[reflowTime:0.26 source:map[column:224969 line:1 type:source-location url:https://www.eclipse.org/public/js/main.js?v1.0?v=1775577514 urlProvider:network]] map[reflowTime:0.137 source:map[column:224005 line:1 type:source-location url:https://www.eclipse.org/public/js/main.js?v1.0?v=1775577514 urlProvider:network]] map[reflowTime:0.403 source:map[column:221362 line:1 type:source-location url:https://www.eclipse.org/public/js/main.js?v1.0?v=1775577514 urlProvider:network]] map[reflowTime:1.225 source:map[column:194403 line:1 type:source-location url:https://www.eclipse.org/public/js/main.js?v1.0?v=1775577514 urlProvider:network]]]

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
body.landing-page > main#main > section.featured-jumbotron > ::before `body.landing-page > main#main > section.featured-jumbotron > ::before`	www.eclipse.org/public/images/bg-home.webp?5c318d416c98e612849efeb88a71e8da	453.1 KiB	260.3 KiB
div.showcase > div.showcase-item > div.showcase-item-img-wrapper > img `div.showcase > div.showcase-item > div.showcase-item-img-wrapper > img`	newsroom.eclipse.org/sites/default/files/Eclipse%20GLSP%E2%84%A2.jpg	270.0 KiB	225.6 KiB
div.showcase > div.showcase-item > div.showcase-item-img-wrapper > img `div.showcase > div.showcase-item > div.showcase-item-img-wrapper > img`	www.eclipse.org/home/images/community-newsletter.webp	229.6 KiB	198.9 KiB
div#collaboration-models > div.row > div.col-sm-13 > img.img-responsive `div#collaboration-models > div.row > div.col-sm-13 > img.img-responsive`	www.eclipse.org/home/images/collaboration-models.webp	40.6 KiB	28.8 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:393.0539990234375 label:Time to first byte subpart:timeToFirstByte] map[duration:825.1740009765625 label:Resource load delay subpart:resourceLoadDelay] map[duration:143.894 label:Resource load duration subpart:resourceLoadDuration] map[duration:1201.04 label:Element render delay subpart:elementRenderDelay]]

lhId: page-4-SECTION

nodeLabel: Global community, European foundation The Eclipse Foundation empowers our glob…

path: 1,HTML,1,BODY,6,MAIN,0,SECTION

selector: body.landing-page > main#main > section.featured-jumbotron

snippet: <section class="featured-jumbotron fade-group bg bg-home">

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

lhId: page-4-SECTION

nodeLabel: Global community, European foundation The Eclipse Foundation empowers our glob…

path: 1,HTML,1,BODY,6,MAIN,0,SECTION

selector: body.landing-page > main#main > section.featured-jumbotron

snippet: <section class="featured-jumbotron fade-group bg bg-home">

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

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.eclipse.org/public/css/styles.css?v=1775577514	74.3 KiB	831 ms
/css2?family=Roboto:ital,wght@0,100;0,300;0,400;0,500;0,7...	2.9 KiB	838 ms
fonts.googleapis.com/css2?family=Inter:wght@200..900&display=swap	728 B
fonts.googleapis.com/css2?family=Inconsolata:wght@200..900&display=swap	606 B	175 ms

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

Request	Cache TTL	Transfer Size
/eclipse.org-common/themes/solstice/public/images/logo/ec...	604800.0 s	48.2 KiB
/eclipse.org-common/themes/solstice/public/images/logo/ec...	604800.0 s	1.7 KiB

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
Global community, European foundation The Eclipse Foundation empowers our glob… `body.landing-page > main#main > section.featured-jumbotron`	0.172

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: 280 ms 63.8 KiB

URL	Transfer Size	Est Savings
www.eclipse.org/public/css/styles.css?v=1775577514	73.9 KiB	63.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: 1.1 s 211.3 KiB

URL	Transfer Size	Est Savings
www.eclipse.org/public/js/main.js?v1.0?v=1775577514	293.1 KiB	144.1 KiB
www.googletagmanager.com/gtm.js?id=GTM-5WLCZXC	126.0 KiB	67.2 KiB

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Category	Time Spent
Script Evaluation	976 ms
Style & Layout	652 ms
Other	645 ms
Rendering	230 ms
Script Parsing & Compilation	132 ms
Parse HTML & CSS	114 ms

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

	URL
Eclipse Foundation `div.navigation-bar-inner > div.navigation-bar-left > a.focus-highlight > img.navigation-bar-brand`	/eclipse.org-common/themes/solstice/public/images/logo/ec...
Eclipse Foundation `div.container > div.footer-inner > section.footer-bottom-section > img.img-responsive`	/eclipse.org-common/themes/solstice/public/images/logo/ec...

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

●Document request latency

●Optimize DOM size

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

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

●JavaScript execution time 1.1 s

●Avoid long main-thread tasks 4 long tasks found

●Avoid non-composited animations 1 animated element found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 130 ms

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

○INP breakdown

○User Timing marks and measures

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.

ARIA

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Failing Elements
div.container > div.navigation-bar-inner > div.navigation-bar-right > a.mobile-menu-toggle `div.container > div.navigation-bar-inner > div.navigation-bar-right > a.mobile-menu-toggle`

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Failing Elements
Collaboration models `div.col-xs-24 > div.eclipsefdn-collapsible-tabs > div.tab-content > a`
Community events `div.col-xs-24 > div.eclipsefdn-collapsible-tabs > div.tab-content > a`
Resources and services `div.col-xs-24 > div.eclipsefdn-collapsible-tabs > div.tab-content > a`

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

Contrast

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

Failing Elements
23 March 2026 `li.margin-bottom-30 > a.link-unstyled > div.simplified-news-header > p.simplified-news-date`
5 March 2026 `li.margin-bottom-30 > a.link-unstyled > div.simplified-news-header > p.simplified-news-date`
3 March 2026 `li.margin-bottom-30 > a.link-unstyled > div.simplified-news-header > p.simplified-news-date`
7 April 2026 `li.margin-bottom-30 > a.link-unstyled > div.simplified-news-header > p.simplified-news-date`
30 March 2026 `li.margin-bottom-30 > a.link-unstyled > div.simplified-news-header > p.simplified-news-date`
30 March 2026 `li.margin-bottom-30 > a.link-unstyled > div.simplified-news-header > p.simplified-news-date`

These are opportunities to improve the legibility of your content.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Failing Elements
About `li > ul > li > a`
Projects `li > ul > li > a`
Collaborations `li > ul > li > a`
Membership `li > ul > li > a`
Sponsor `li > ul > li > a`
Privacy Policy `li > ul > li > a`
Terms of Use `li > ul > li > a`
Compliance `li > ul > li > a`
Code of Conduct `li > ul > li > a`
Legal Resources `li > ul > li > a`
Report a Vulnerability `li > ul > li > a`
Service Status `li > ul > li > a`
Contact Us `li > ul > li > a`
Support `li > ul > li > a`
Submit `section.newsletter-section > form#mc-embedded-subscribe-form > div.text-field-outlined > button#mc-embedded-subscribe`
Terms of use `div.legal-information > ul.legal-links > li > a`
Legal `div.legal-information > ul.legal-links > li > a`

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Failing Elements
click here. `body.landing-page > div.cc-window > span#cookieconsent:desc > a.cc-link`

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

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

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

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

●Elements use only permitted ARIA attributes

●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

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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●All heading elements contain content.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements 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.

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

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

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

○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
www.eclipse.org/public/js/main.js?v1.0?v=1775577514 line 1, col 268106	`ReferenceError: eclipsefdnWorkingGroupsList is not defined at HTMLDocument.<anonymous> (https://www.eclipse.org/public/js/main.js?v1.0?v=1775577514:2:268107)`

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

URL
www.eclipse.org/public/js/main.js?v1.0?v=1775577514

●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

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

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

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Uncrawlable Link
div.container > div.navigation-bar-inner > div.navigation-bar-right > a.mobile-menu-toggle `div.container > div.navigation-bar-inner > div.navigation-bar-right > a.mobile-menu-toggle`

To appear in search results, crawlers need access to your app.

○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

●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

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.

1.04 s

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

2.59 s

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

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

1.82 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.59 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.

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
/public/fonts/vendor/@fortawesome/fontawesome-free/webfa-...	380 ms
/public/fonts/vendor/@fortawesome/fontawesome-free/webfa-...	380 ms
/public/fonts/vendor/@fortawesome/fontawesome-free/webfa-...	185 ms

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
body.landing-page > main#main > section.featured-jumbotron > ::before `body.landing-page > main#main > section.featured-jumbotron > ::before`	www.eclipse.org/public/images/bg-home.webp?5c318d416c98e612849efeb88a71e8da	453.1 KiB	260.3 KiB
div.showcase > div.showcase-item > div.showcase-item-img-wrapper > img `div.showcase > div.showcase-item > div.showcase-item-img-wrapper > img`	newsroom.eclipse.org/sites/default/files/Eclipse%20GLSP%E2%84%A2.jpg	270.0 KiB	243.2 KiB
div.showcase > div.showcase-item > div.showcase-item-img-wrapper > img `div.showcase > div.showcase-item > div.showcase-item-img-wrapper > img`	www.eclipse.org/home/images/community-newsletter.webp	229.6 KiB	200.2 KiB
div.row > div.col-md-10 > div.gallery-stack > img `div.row > div.col-md-10 > div.gallery-stack > img`	www.eclipse.org/home/images/jumbotron-stack-1.webp	38.5 KiB	14.0 KiB
div#collaboration-models > div.row > div.col-sm-13 > img.img-responsive `div#collaboration-models > div.row > div.col-sm-13 > img.img-responsive`	www.eclipse.org/home/images/collaboration-models.webp	40.6 KiB	8.0 KiB
div.showcase > div.showcase-item > div.showcase-item-img-wrapper > img `div.showcase > div.showcase-item > div.showcase-item-img-wrapper > img`	/sites/default/files/newsletter/featured_committers/Alois...	18.6 KiB	7.4 KiB

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

lhId: page-6-SECTION

nodeLabel: Global community, European foundation The Eclipse Foundation empowers our glob…

path: 1,HTML,1,BODY,6,MAIN,0,SECTION

selector: body.landing-page > main#main > section.featured-jumbotron

snippet: <section class="featured-jumbotron fade-group bg bg-home">

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.eclipse.org/public/css/styles.css?v=1775577514	74.3 KiB	323 ms
/css2?family=Roboto:ital,wght@0,100;0,300;0,400;0,500;0,7...	2.9 KiB	290 ms
fonts.googleapis.com/css2?family=Inconsolata:wght@200..900&display=swap	583 B	65 ms
fonts.googleapis.com/css2?family=Inter:wght@200..900&display=swap	728 B

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

Request	Cache TTL	Transfer Size
/eclipse.org-common/themes/solstice/public/images/logo/ec...	604800.0 s	48.2 KiB
/eclipse.org-common/themes/solstice/public/images/logo/ec...	604800.0 s	1.7 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

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: 0.0 ms 62.3 KiB

URL	Transfer Size	Est Savings
www.eclipse.org/public/css/styles.css?v=1775577514	73.9 KiB	62.3 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: 320 ms 211.2 KiB

URL	Transfer Size	Est Savings
www.eclipse.org/public/js/main.js?v1.0?v=1775577514	293.1 KiB	144.0 KiB
www.googletagmanager.com/gtm.js?id=GTM-5WLCZXC	126.0 KiB	67.2 KiB

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

	URL
37911 `div.showcase > div.eclipsefdn-promo-content > a > img.img-responsive`	/sites/default/files/styles/large/public/ads/fokus_promo....
Eclipse Foundation `div.navigation-bar-inner > div.navigation-bar-left > a.focus-highlight > img.navigation-bar-brand`	/eclipse.org-common/themes/solstice/public/images/logo/ec...
Eclipse Foundation `div.container > div.footer-inner > section.footer-bottom-section > img.img-responsive`	/eclipse.org-common/themes/solstice/public/images/logo/ec...

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

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Max Potential First Input Delay 40 ms

●Minify CSS

●Minify JavaScript

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

●JavaScript execution time 0.3 s

●Minimizes main-thread work 0.8 s

●Avoid non-composited animations 1 animated element found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 130 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

●Avoid large layout shifts 15 layout shifts found

○INP breakdown

○User Timing marks and measures

○Avoid long main-thread tasks

Accessibility

Contrast

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

Failing Elements
Sponsored Ad `div.eclipsefdn-edition-showcase > div.showcase > div.eclipsefdn-promo-content > p.featured-story-description`
Advertise here `div.showcase > div.eclipsefdn-promo-content > p.featured-story-description > a`
23 March 2026 `li.margin-bottom-30 > a.link-unstyled > div.simplified-news-header > p.simplified-news-date`
5 March 2026 `li.margin-bottom-30 > a.link-unstyled > div.simplified-news-header > p.simplified-news-date`
3 March 2026 `li.margin-bottom-30 > a.link-unstyled > div.simplified-news-header > p.simplified-news-date`
7 April 2026 `li.margin-bottom-30 > a.link-unstyled > div.simplified-news-header > p.simplified-news-date`
30 March 2026 `li.margin-bottom-30 > a.link-unstyled > div.simplified-news-header > p.simplified-news-date`
30 March 2026 `li.margin-bottom-30 > a.link-unstyled > div.simplified-news-header > p.simplified-news-date`

These are opportunities to improve the legibility of your content.

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.navigation-bar-controls > ul > li.dropdown > a#user-menu `div.navigation-bar-controls > ul > li.dropdown > a#user-menu`

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

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Failing Elements
Privacy Policy `li > ul > li > a`
Terms of Use `li > ul > li > a`
Code of Conduct `li > ul > li > a`
Legal Resources `li > ul > li > a`
Submit `section.newsletter-section > form#mc-embedded-subscribe-form > div.text-field-outlined > button#mc-embedded-subscribe`

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Failing Elements
click here. `body.landing-page > div.cc-window > span#cookieconsent:desc > a.cc-link`

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

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

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

●`[role]`s are contained by their required parent element

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

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

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

●Elements use only permitted ARIA attributes

●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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●All heading elements contain content.

○`[accesskey]` values are unique

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

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

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

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

○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
www.eclipse.org/public/js/main.js?v1.0?v=1775577514 line 1, col 268106	`ReferenceError: eclipsefdnWorkingGroupsList is not defined at HTMLDocument.<anonymous> (https://www.eclipse.org/public/js/main.js?v1.0?v=1775577514:2:268107)`

URL
www.eclipse.org/public/js/main.js?v1.0?v=1775577514

●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

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Mitigate clickjacking with XFO or CSP

SEO

Crawling and Indexing

Uncrawlable Link
div.container > div.navigation-bar-inner > div.navigation-bar-right > a.mobile-menu-toggle `div.container > div.navigation-bar-inner > div.navigation-bar-right > a.mobile-menu-toggle`

To appear in search results, crawlers need access to your app.

○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

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

Site Health

Top Priorities (5)

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

ARIA

Contrast

Best practices

Best Practices

General

SEO

Crawling and Indexing

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Contrast

Names and labels

Best practices

Best Practices

General

SEO

Crawling and Indexing

Keyboard Shortcuts