Skip to content
Audit Complete

Results for https://jcp.org

Visit site
Spain Spain · Madrid Completed: Apr 22, 2026 21:01 UTC
Download JSON Download Markdown Report

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
C78

Site Health

Score: 78 / 100

Based on 8 categories, 0 sections

Fast site — your users get a smooth experience.

Good foundation, but a few gaps could be exploited.

Several issues make your site difficult for assistive technology users.

Well-optimized for search — your content is discoverable.

Solid infrastructure — fast server responses across the board.

Several regulatory requirements are not yet met.

Missing metadata means poor previews on social media and search.

Reasonable footprint with room for optimization.

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.

How the composite score is calculated

How you compare

Boomerang · 140 peers
You 78
·
Avg 71
+7 above average
0 50 100
Better than 98% of Boomerang sites See full Boomerang benchmark →
HSTS · 2029 peers
You 78
·
Avg 74
At average
0 50 100
Better than 81% of HSTS sites See full HSTS benchmark →

Top Priorities (5)

1

'unsafe-eval' found in script source

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy
2

'unsafe-inline' found in script source

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy
3

1 link(s) with no accessible text

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Link & Button Quality
4

3 control(s) without accessible label

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Form Accessibility
5

No <main> landmark found

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Landmark Structure
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

2

High impact, low effort — start here.

Strategic

3

High impact, requires investment.

Easy Improvements

0

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

0

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fjcp.org)](https://beavercheck.com/results/9b3efceb-7099-4e43-802e-fcd017dbfb04)
<a href="https://beavercheck.com/results/9b3efceb-7099-4e43-802e-fcd017dbfb04"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fjcp.org" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fjcp.org

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.

2 security gaps detected — browsers may warn visitors about your site.
3 accessibility issues exclude users who rely on assistive technology.
B
Could reach Estimate based on resolving critical issues

Conversion Barriers

2 critical 4 warning

6 barrier(s) likely increasing bounce by ~30%.

Trust (1)

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Usability (2)

3 form field(s) without a label

+6% bounce

Screen readers skip unlabeled fields; autofill can't identify them; checkout abandonment spikes

Fix: Associate every input with a visible <label for="…">; add autocomplete attributes

No viewport meta tag

+15% bounce

Mobile browsers render at desktop width and shrink — text unreadable, tap targets miniature

Fix: Add <meta name="viewport" content="width=device-width, initial-scale=1">

Content (2)

No Open Graph tags

+2% bounce

Links shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop

Fix: Add og:title, og:description, og:image, og:url to the page head

No structured data

+2% bounce

No rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices

Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)

Navigation (1)

No skip-to-content link

+1% bounce

Keyboard and screen-reader users must tab through the entire header on every page

Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

$550 investment → $0.06/month returns + USD 150,000 risk avoided

Payback period: > 2 years First-year ROI: -100%

Investment

$550

6h · 5 findings

Monthly returns

$0.06 /mo

~$0.77 / year

  • Bandwidth savings $0.06

Regulatory risk avoided

USD 150,000

if kept compliant

  • ADA Title III USD 150,000

$100 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

$550

5.5 developer hours at $100/hr

Based on United States rates ($100/hr)

Quick wins
$100 2 fixes in ~60 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions
$ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

$12,500 / month at risk

~$150,001 / year if left unfixed

Compliance Risk

$150,000

ADA Title III
  • No <main> landmark found
    ADA Title III: USD 25,000 – USD 150,000
  • No <nav> landmark found
    ADA Title III: USD 25,000 – USD 150,000
  • Skip navigation link is missing (WCAG 2.4.1)
    ADA Title III: USD 25,000 – USD 150,000

+1 more

Bandwidth Waste

$0.06 /mo

797.3 MB/mo × 0.080 USD/GB

  • Optimize transfer: save ~80 KB per page load
    Saves $0.06/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Unique monthly visitors from your analytics

Purchases, signups, or key actions

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue
Current bounce (est.)
After fixes (est.)
Estimated bounce reduction

Fix 5 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

94
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
56
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
73
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
91
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

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.

2.01 s

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

2.01 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.034

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

4.93 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.01 s

Detailed Report

Audit breakdown by category with detailed findings.

94

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

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

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.

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.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]
items: [map[duration:1771.529 label:Time to first byte subpart:timeToFirstByte] map[duration:1106.927 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-TD
nodeLabel: Welcome to the Java Community Process! Welcome to jcp.org, home of the Java Com…
path: 2,HTML,1,BODY,3,TABLE,0,TBODY,0,TR,7,TD,2,TABLE,0,TBODY,0,TR,0,TD,0,TABLE,0,TBODY,0,TR,0,TD
selector: table > tbody > tr > td#centercontent
snippet: <td id="centercontent" valign="top">

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.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
Follow us on X (formerly Twitter) td#centercontent > p > a > img
jcp.org/images/logo-black.png99.9 KiB99.9 KiB
Find us on Facebook td#centercontent > p > a > img
jcp.org/images/Facebook_Logo_Primary.png53.5 KiB53.5 KiB

Tap interactions may be delayed by up to 300 ms if the viewport is not optimized for mobile.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Diagnostics

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
The page has an unload handler in a sub frame.Actionable

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

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Estimated savings: 0.0 ms 26.6 KiB
URLTransfer SizeEst Savings
s.go-mpulse.net/boomerang/UE9G5-FVEGY-MA38N-LMMNY-SBQP256.6 KiB26.6 KiB

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

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.8 s
Time to Interactive 2.0 s
Layout shift culprits
Optimize DOM size
Font display
Forced reflow
Modern HTTP
Max Potential First Input Delay 50 ms
Minify CSS
Minify JavaScript
Reduce unused CSS
Avoids enormous network payloads Total size was 260 KiB
JavaScript execution time 0.2 s
Minimizes main-thread work 0.6 s
Image elements have explicit `width` and `height`
Network Requests
Network Round Trip Times 0 ms
Server Backend Latencies 740 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 320 ms
Avoid large layout shifts 3 layout shifts found
INP breakdown
LCP request discovery
User Timing marks and measures
Avoid long main-thread tasks
Avoid non-composited animations
56

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
Register for Site td#leftcontent > ul#p7PMnav > div.noNav > a
JCP Terms of Use td#leftcontent > ul#p7PMnav > div.noNav > a
Oracle Privacy Policy td#leftcontent > ul#p7PMnav > div.noNav > a
Welcome to the Java Community Process! tbody > tr > td#centercontent > div.header1
register now tbody > tr > td#centercontent > a
overview page tr > td#centercontent > p > a
Annual JCP Community Party at JavaOne 2026! tbody > tr > td#centercontent > div.header1
2025 JCP Award Winners! tbody > tr > td#centercontent > div.header1
2025 JCP Award winners tbody > tr > td#centercontent > a
December 2025 Newsletter is Released! tbody > tr > td#centercontent > div.header1
December 2025 edition of the JCP Newsletter tbody > tr > td#centercontent > a
December Public EC Meeting Agenda and Recording Published tbody > tr > td#centercontent > div.header1
The agenda and recording tr > td#centercontent > p > a
2025 JCP EC Elections Results Published! tbody > tr > td#centercontent > div.header1
results of the 2025 JCP EC elections tr > td#centercontent > p > a
25 Years of the JCP Program Celebration tbody > tr > td#centercontent > div.header1
Twenty-five years of the Java Community Process tr > td#centercontent > p > a
Celebrating 25 years of the JCP with JUGs around the world tr > td#centercontent > p > a
JCP Working Groups tbody > tr > td#centercontent > div.header1
Java in Education td#centercontent > ul > li > a
message from Heather VanCura ul > li > p > a
Java Ecosystem JCP Working Group td#centercontent > ul > li > a
Java and AI Working Group td#centercontent > ul > li > a
JSR Updates tbody > tr > td#centercontent > h1
New JSRs tr > td > b > a
JSR 402 tbody > tr > td > a
Public Reviews td > p > b > a
JSR 401 tr > td > p > a
Final Releases td > p > b > a
JSR 378 tr > td > p > a
JSR 381 tr > td > p > a
JSR 393 tr > td > p > a
JSR 394 tr > td > p > a
JSR 395 tr > td > p > a
JSR 396 tr > td > p > a
JSR 397 tr > td > p > a
JSR 398 tr > td > p > a
JSR 399 tr > td > p > a
JSR 400 tr > td > p > a
JSR 401 tr > td > p > a
Maintenance Reviews tr > td > b > a
Maintenance Releases td > p > b > a
JSR 384 tr > td > p > a
JSR 385 tr > td > p > a
JSR 387 tr > td > p > a
JSR 392 tr > td > p > a
JSR 907 tr > td > p > a
JSR 199 tr > td > p > a
JSR 221 tr > td > p > a
JSR 269 tr > td > p > a
Recent News and Announcements tbody > tr > td#centercontent > div.header1
Inside the JCP Executive Committee: Purpose, Structure, and Impact td#centercontent > ul > li > a
From Hokkaido to the World: How Hiroto Yamakawa Built a Java Community that Ins… td#centercontent > ul > li > a
Java in Education at the Dominican Republic Java User Group td#centercontent > ul > li > a
JCP's 25th Anniversary - Twenty-five years of the Java Community Process td#centercontent > ul > li > a
News and Announcements from the Program Management Office (PMO) tbody > tr > td#centercontent > a
Spec Lead Guide tr > td#rightcontent > span.rightcol > a
JCP 2 tr > td#rightcontent > span.rightcol > a
EC meeting summaries tr > td#rightcontent > span.rightcol > a
Calendar tr > td#rightcontent > span.rightcol > a
Multimedia page tr > td#rightcontent > span.rightcol > a
Submit a new JSR tr > td#rightcontent > span.rightcol > a
JCP Community Github tr > td#rightcontent > span.rightcol > a
JSR 221 JDBC 4.5 Maintenance Release td#rightcontent > span.rightcol > b > a
JSR 401 Java SE 26 Final Release td#rightcontent > span.rightcol > b > a
JSR 269 Pluggable Annotation Processing API Maintenance Release 12 td#rightcontent > span.rightcol > b > a
JSR 401 Java SE 26 Public Review td#rightcontent > span.rightcol > b > a
JSR 269 Pluggable Annotation Processing API Maintenance Review 20 td#rightcontent > span.rightcol > b > a
JSR 402 Java SE 27 iteration begins td#rightcontent > span.rightcol > b > a
JSR 221 JDBC 4 API Specification Maintenance Review 5 td#rightcontent > span.rightcol > b > a
JSR 400 Java SE 25 Final Release td#rightcontent > span.rightcol > b > a
JSR 269 Pluggable Annotation Processing API Maintenance Release 11 td#rightcontent > span.rightcol > b > a
JSR 400 Java SE 25 Public Review td#rightcontent > span.rightcol > b > a
JSR 269 Pluggable Annotation Processing API Maintenance Review 19 td#rightcontent > span.rightcol > b > a
JSR 401 Java SE 26 iteration begins td#rightcontent > span.rightcol > b > a
JSR 399 Java SE 24 Final Release td#rightcontent > span.rightcol > b > a
JSR 269 Pluggable Annotation Processing API Maintenance Release 10 td#rightcontent > span.rightcol > b > a
JSR 199 Java Compiler API Maintenance Release 5 td#rightcontent > span.rightcol > b > a
JSR 399 Java SE 24 Public Review td#rightcontent > span.rightcol > b > a
JSR 199 Java Compiler API Maintenance Review 8 td#rightcontent > span.rightcol > b > a
JSR 269 Pluggable Annotation Processing API Maintenance Review 18 td#rightcontent > span.rightcol > b > a
JSR 400 Java SE 25 iteration begins td#rightcontent > span.rightcol > b > a
JSR 398 Java SE 23 Final Release td#rightcontent > span.rightcol > b > a
JSR 199 Java Compiler API Maintenance Release 4 td#rightcontent > span.rightcol > b > a
JSR 269 Pluggable Annotation Processing API Maintenance Release 9 td#rightcontent > span.rightcol > b > a
JSR 398 Java SE 23 Public Review td#rightcontent > span.rightcol > b > a
JSR 199 Java Compiler API Maintenance Review 7 td#rightcontent > span.rightcol > b > a
JSR 282 Real-Time Specification for Java 2.0 Final Release td#rightcontent > span.rightcol > b > a
JSR 269 Pluggable Annotation Processing API Maintenance Review 17 td#rightcontent > span.rightcol > b > a
JSR 392 Java SE 17 Maintenance Release td#rightcontent > span.rightcol > b > a
JSR 384 Java SE 11 Maintenance Release 3 td#rightcontent > span.rightcol > b > a
JSR 337 Java SE 8 Release Contents Maintenance Release 6 td#rightcontent > span.rightcol > b > a
JSR 399 Java SE 24 iteration begins td#rightcontent > span.rightcol > b > a
JSR 392 Java SE 17 Maintenance Review td#rightcontent > span.rightcol > b > a
JSR 384 Java SE 11 Maintenance Review 3 td#rightcontent > span.rightcol > b > a
JSR 337 Java SE 8 Release Contents Maintenance Review 6 td#rightcontent > span.rightcol > b > a
JSR 269 Pluggable Annotation Processing Maintenance Release td#rightcontent > span.rightcol > b > a
JSR 397 Java SE 22 Final Release td#rightcontent > span.rightcol > b > a
JSR 385 Units of Measurement API 2 Maintenance Release 2 td#rightcontent > span.rightcol > b > a
JSR 398 Java SE 23 iteration begins td#rightcontent > span.rightcol > b > a
JSR 396 Java SE 21 Final Release td#rightcontent > span.rightcol > b > a
JSR 269 Pluggable Annotation Processing API Maintenance Release 7 td#rightcontent > span.rightcol > b > a
JSR 384 Java SE 11 Maintenance Release 2 td#rightcontent > span.rightcol > b > a
JSR 337 Java SE 8 Maintenance Release 5 td#rightcontent > span.rightcol > b > a
JSR 384 Java SE 11 Maintenance Review 2 td#rightcontent > span.rightcol > b > a
JSR 337 Java SE 8 Maintenance Review 5 td#rightcontent > span.rightcol > b > a
JSR 378 Portlet 3.0 Bridge for JavaServer Faces 2.2 Final Release td#rightcontent > span.rightcol > b > a
JSR 243 Java Data Objects Maintenance Release 4 td#rightcontent > span.rightcol > b > a
JSR 381 Visual Recognition Specification Final Release td#rightcontent > span.rightcol > b > a
JSR 392 Java SE 17 Final Release td#rightcontent > span.rightcol > b > a
Contact Us body > div#footer > div.footleft > a
© 2026, Oracle Corporation and/or its affiliates. Terms of Use. Privacy Policy.… body > div#footer > div.footleft2
Terms of Use body > div#footer > div.footleft2 > a
Privacy Policy body > div#footer > div.footleft2 > a
Trademarks body > div#footer > div.footleft2 > a

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
JCP Terms of Use td#leftcontent > ul#p7PMnav > div.noNav > a
Oracle Privacy Policy td#leftcontent > ul#p7PMnav > div.noNav > a
register now tbody > tr > td#centercontent > a
overview page tr > td#centercontent > p > a
2025 JCP Award winners tbody > tr > td#centercontent > a
December 2025 edition of the JCP Newsletter tbody > tr > td#centercontent > a
The agenda and recording tr > td#centercontent > p > a
Twenty-five years of the Java Community Process tr > td#centercontent > p > a
Celebrating 25 years of the JCP with JUGs around the world tr > td#centercontent > p > a
Java in Education td#centercontent > ul > li > a
message from Heather VanCura ul > li > p > a
Java Ecosystem JCP Working Group td#centercontent > ul > li > a
Java and AI Working Group td#centercontent > ul > li > a
JSR 402 tbody > tr > td > a
JSR 401 tr > td > p > a
JSR 378 tr > td > p > a
JSR 381 tr > td > p > a
JSR 393 tr > td > p > a
JSR 394 tr > td > p > a
JSR 395 tr > td > p > a
JSR 396 tr > td > p > a
JSR 397 tr > td > p > a
JSR 398 tr > td > p > a
JSR 399 tr > td > p > a
JSR 400 tr > td > p > a
JSR 401 tr > td > p > a
JSR 384 tr > td > p > a
JSR 385 tr > td > p > a
JSR 387 tr > td > p > a
JSR 392 tr > td > p > a
JSR 907 tr > td > p > a
JSR 199 tr > td > p > a
JSR 221 tr > td > p > a
JSR 269 tr > td > p > a
Terms of Use body > div#footer > div.footleft2 > a
Privacy Policy body > div#footer > div.footleft2 > a
Trademarks body > div#footer > div.footleft2 > a

These are opportunities to improve the legibility of your content.

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.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#tools > div.search > form#[object HTMLInputElement] > input.form div#tools > div.search > form#[object HTMLInputElement] > input.form
tr > td#leftcontent > form#[object HTMLInputElement] > input.form tr > td#leftcontent > form#[object HTMLInputElement] > input.form

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
JSRs by Platform JSRs by Technology JSRs by Stage JSRs by Committee List of All… tbody > tr > td#leftcontent > ul#p7PMnav

These are opportunities to improve the experience of reading tabular or list data using 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
JSRs by Platform td#leftcontent > ul#p7PMnav > li > a
JSRs by Technology td#leftcontent > ul#p7PMnav > li > a
JSRs by Stage td#leftcontent > ul#p7PMnav > li > a
JSRs by Committee td#leftcontent > ul#p7PMnav > li > a
List of All JSRs td#leftcontent > ul#p7PMnav > li > a
About JCP td#leftcontent > ul#p7PMnav > li > a.p7PMtrg
Get Involved td#leftcontent > ul#p7PMnav > li > a.p7PMtrg
Community Resources td#leftcontent > ul#p7PMnav > li > a.p7PMtrg
Community News td#leftcontent > ul#p7PMnav > li > a.p7PMtrg
FAQ td#leftcontent > ul#p7PMnav > li > a
Contact Us td#leftcontent > ul#p7PMnav > li > a
New JSRs tr > td > b > a
Public Reviews td > p > b > a
Final Releases td > p > b > a
Inside the JCP Executive Committee: Purpose, Structure, and Impact td#centercontent > ul > li > a
From Hokkaido to the World: How Hiroto Yamakawa Built a Java Community that Ins… td#centercontent > ul > li > a
Java in Education at the Dominican Republic Java User Group td#centercontent > ul > li > a
JCP's 25th Anniversary - Twenty-five years of the Java Community Process td#centercontent > ul > li > a
JCP 2 tr > td#rightcontent > span.rightcol > a
Calendar tr > td#rightcontent > span.rightcol > a
Multimedia page tr > td#rightcontent > span.rightcol > a
Submit a new JSR tr > td#rightcontent > span.rightcol > a
JCP Community Github tr > td#rightcontent > span.rightcol > a

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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-hidden="true"]` is not present on the document `<body>`
Image elements have `[alt]` attributes
Input buttons have discernible text.
Document has a `<title>` element
Links have a discernible name
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Heading elements appear in a sequentially-descending order
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
`<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 a valid value for its `[lang]` attribute
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
`<input type="image">` elements have `[alt]` text
The document does not use `<meta http-equiv="refresh">`
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
No element has a `[tabindex]` value greater than 0
`<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.
73

Best Practices

User Experience

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLDisplayed sizeActual sizeExpected size
Java Community Process div#header > div#logo > a > img
jcp.org/images/spacer.gif151 x 811 x 1227 x 122
Ad Banner td#leftcontent > div.ads > a > img
jcp.org/images/ad_banner2.gif150 x 70150 x 70225 x 105
News tbody > tr > td#rightcontent > img
jcp.org/images/global/hd_news.gif150 x 18150 x 18225 x 27
Quick Links tbody > tr > td#rightcontent > img
jcp.org/images/global/hd_quick-links.gif150 x 18150 x 18225 x 27
Find JSRs tbody > tr > td#leftcontent > img
jcp.org/images/hd_find-jsrs.gif150 x 18150 x 18225 x 27
JCP Info tr > td#leftcontent > ul#p7PMnav > img
jcp.org/images/hd_jcp-info.gif150 x 18150 x 18225 x 27
My JCP tr > td#leftcontent > ul#p7PMnav > img
jcp.org/images/hd_my-jcp.gif150 x 18150 x 18225 x 27
tbody > tr > td#rightcontent > img tbody > tr > td#rightcontent > img
jcp.org/images/global/spacer.gif150 x 51 x 1225 x 8
tr > td#leftcontent > div.bar > img tr > td#leftcontent > div.bar > img
jcp.org/images/hr_dots1.gif150 x 3150 x 3225 x 5
Submit this Search div.search > form#[object HTMLInputElement] > a > img
jcp.org/images/button_go.gif21 x 1621 x 1632 x 24
tr > td#centercontent > div.anybar > img tr > td#centercontent > div.anybar > img
jcp.org/images/global/bar_green.gif12 x 412 x 418 x 6

Browser Compatibility

Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.

Why this matters

Performance issues directly impact user engagement and conversion rates.

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
Unload event listeners are deprecated and will be removed.
Uses HTTPS
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
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
91

SEO

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

Content Best Practices

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
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`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

96
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
56
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
73
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
91
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

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.

378 ms

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

678 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.119

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

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

678 ms

Detailed Report

Audit breakdown by category with detailed findings.

96

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

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

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.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.118823] map[node:map[boundingRect:map[bottom:701 height:19 left:186 right:1174 top:682 width:988] lhId:page-1-DIV nodeLabel:2025 JCP EC Elections Results Published! path:2,HTML,1,BODY,3,TABLE,0,TBODY,0,TR,7,TD,2,TABLE,0,TBODY,0,TR,0,TD,0,TABLE,0,TBODY,0,TR,0,TD,43,DIV selector:tbody > tr > td#centercontent > div.header1 snippet:<div class="header1"> type:node] score:0.118674] map[node:map[boundingRect:map[bottom:295 height:24 left:186 right:1174 top:271 width:988] lhId:page-5-P nodeLabel:       path:2,HTML,1,BODY,3,TABLE,0,TBODY,0,TR,7,TD,2,TABLE,0,TBODY,0,TR,0,TD,0,TABLE,0,TBODY,0,TR,0,TD,13,P selector:tbody > tr > td#centercontent > p snippet:<p> type:node] score:0.000149]]

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.

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
Follow us on X (formerly Twitter) td#centercontent > p > a > img
jcp.org/images/logo-black.png99.9 KiB99.9 KiB
Find us on Facebook td#centercontent > p > a > img
jcp.org/images/Facebook_Logo_Primary.png53.5 KiB53.5 KiB

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.

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

Diagnostics

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
The page has an unload handler in a sub frame.Actionable

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

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Estimated savings: 20 ms 26.7 KiB
URLTransfer SizeEst Savings
s.go-mpulse.net/boomerang/UE9G5-FVEGY-MA38N-LMMNY-SBQP256.6 KiB26.7 KiB

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

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 338 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

ElementLayout shift score
2025 JCP EC Elections Results Published! tbody > tr > td#centercontent > div.header1
0.119
      tbody > tr > td#centercontent > p
0.000
Optimize DOM size
Font display
Forced reflow
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Time to Interactive 0.7 s
Max Potential First Input Delay 20 ms
Minify CSS
Minify JavaScript
Reduce unused CSS
Avoids enormous network payloads Total size was 259 KiB
JavaScript execution time 0.0 s
Minimizes main-thread work 0.2 s
Image elements have explicit `width` and `height`
Network Requests
Network Round Trip Times 0 ms
Server Backend Latencies 210 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 330 ms
INP breakdown
LCP request discovery
User Timing marks and measures
Avoid long main-thread tasks
Avoid non-composited animations
56

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
Register for Site td#leftcontent > ul#p7PMnav > div.noNav > a
JCP Terms of Use td#leftcontent > ul#p7PMnav > div.noNav > a
Oracle Privacy Policy td#leftcontent > ul#p7PMnav > div.noNav > a
Welcome to the Java Community Process! tbody > tr > td#centercontent > div.header1
register now tbody > tr > td#centercontent > a
overview page tr > td#centercontent > p > a
Annual JCP Community Party at JavaOne 2026! tbody > tr > td#centercontent > div.header1
2025 JCP Award Winners! tbody > tr > td#centercontent > div.header1
2025 JCP Award winners tbody > tr > td#centercontent > a
December 2025 Newsletter is Released! tbody > tr > td#centercontent > div.header1
December 2025 edition of the JCP Newsletter tbody > tr > td#centercontent > a
December Public EC Meeting Agenda and Recording Published tbody > tr > td#centercontent > div.header1
The agenda and recording tr > td#centercontent > p > a
2025 JCP EC Elections Results Published! tbody > tr > td#centercontent > div.header1
results of the 2025 JCP EC elections tr > td#centercontent > p > a
25 Years of the JCP Program Celebration tbody > tr > td#centercontent > div.header1
Twenty-five years of the Java Community Process tr > td#centercontent > p > a
Celebrating 25 years of the JCP with JUGs around the world tr > td#centercontent > p > a
JCP Working Groups tbody > tr > td#centercontent > div.header1
Java in Education td#centercontent > ul > li > a
message from Heather VanCura ul > li > p > a
Java Ecosystem JCP Working Group td#centercontent > ul > li > a
Java and AI Working Group td#centercontent > ul > li > a
JSR Updates tbody > tr > td#centercontent > h1
New JSRs tr > td > b > a
JSR 402 tbody > tr > td > a
Public Reviews td > p > b > a
JSR 401 tr > td > p > a
Final Releases td > p > b > a
JSR 378 tr > td > p > a
JSR 381 tr > td > p > a
JSR 393 tr > td > p > a
JSR 394 tr > td > p > a
JSR 395 tr > td > p > a
JSR 396 tr > td > p > a
JSR 397 tr > td > p > a
JSR 398 tr > td > p > a
JSR 399 tr > td > p > a
JSR 400 tr > td > p > a
JSR 401 tr > td > p > a
Maintenance Reviews tr > td > b > a
Maintenance Releases td > p > b > a
JSR 384 tr > td > p > a
JSR 385 tr > td > p > a
JSR 387 tr > td > p > a
JSR 392 tr > td > p > a
JSR 907 tr > td > p > a
JSR 199 tr > td > p > a
JSR 221 tr > td > p > a
JSR 269 tr > td > p > a
Recent News and Announcements tbody > tr > td#centercontent > div.header1
Inside the JCP Executive Committee: Purpose, Structure, and Impact td#centercontent > ul > li > a
From Hokkaido to the World: How Hiroto Yamakawa Built a Java Community that Ins… td#centercontent > ul > li > a
Java in Education at the Dominican Republic Java User Group td#centercontent > ul > li > a
JCP's 25th Anniversary - Twenty-five years of the Java Community Process td#centercontent > ul > li > a
News and Announcements from the Program Management Office (PMO) tbody > tr > td#centercontent > a
Spec Lead Guide tr > td#rightcontent > span.rightcol > a
JCP 2 tr > td#rightcontent > span.rightcol > a
EC meeting summaries tr > td#rightcontent > span.rightcol > a
Calendar tr > td#rightcontent > span.rightcol > a
Multimedia page tr > td#rightcontent > span.rightcol > a
Submit a new JSR tr > td#rightcontent > span.rightcol > a
JCP Community Github tr > td#rightcontent > span.rightcol > a
JSR 221 JDBC 4.5 Maintenance Release td#rightcontent > span.rightcol > b > a
JSR 401 Java SE 26 Final Release td#rightcontent > span.rightcol > b > a
JSR 269 Pluggable Annotation Processing API Maintenance Release 12 td#rightcontent > span.rightcol > b > a
JSR 401 Java SE 26 Public Review td#rightcontent > span.rightcol > b > a
JSR 269 Pluggable Annotation Processing API Maintenance Review 20 td#rightcontent > span.rightcol > b > a
JSR 402 Java SE 27 iteration begins td#rightcontent > span.rightcol > b > a
JSR 221 JDBC 4 API Specification Maintenance Review 5 td#rightcontent > span.rightcol > b > a
JSR 400 Java SE 25 Final Release td#rightcontent > span.rightcol > b > a
JSR 269 Pluggable Annotation Processing API Maintenance Release 11 td#rightcontent > span.rightcol > b > a
JSR 400 Java SE 25 Public Review td#rightcontent > span.rightcol > b > a
JSR 269 Pluggable Annotation Processing API Maintenance Review 19 td#rightcontent > span.rightcol > b > a
JSR 401 Java SE 26 iteration begins td#rightcontent > span.rightcol > b > a
JSR 399 Java SE 24 Final Release td#rightcontent > span.rightcol > b > a
JSR 269 Pluggable Annotation Processing API Maintenance Release 10 td#rightcontent > span.rightcol > b > a
JSR 199 Java Compiler API Maintenance Release 5 td#rightcontent > span.rightcol > b > a
JSR 399 Java SE 24 Public Review td#rightcontent > span.rightcol > b > a
JSR 199 Java Compiler API Maintenance Review 8 td#rightcontent > span.rightcol > b > a
JSR 269 Pluggable Annotation Processing API Maintenance Review 18 td#rightcontent > span.rightcol > b > a
JSR 400 Java SE 25 iteration begins td#rightcontent > span.rightcol > b > a
JSR 398 Java SE 23 Final Release td#rightcontent > span.rightcol > b > a
JSR 199 Java Compiler API Maintenance Release 4 td#rightcontent > span.rightcol > b > a
JSR 269 Pluggable Annotation Processing API Maintenance Release 9 td#rightcontent > span.rightcol > b > a
JSR 398 Java SE 23 Public Review td#rightcontent > span.rightcol > b > a
JSR 199 Java Compiler API Maintenance Review 7 td#rightcontent > span.rightcol > b > a
JSR 282 Real-Time Specification for Java 2.0 Final Release td#rightcontent > span.rightcol > b > a
JSR 269 Pluggable Annotation Processing API Maintenance Review 17 td#rightcontent > span.rightcol > b > a
JSR 392 Java SE 17 Maintenance Release td#rightcontent > span.rightcol > b > a
JSR 384 Java SE 11 Maintenance Release 3 td#rightcontent > span.rightcol > b > a
JSR 337 Java SE 8 Release Contents Maintenance Release 6 td#rightcontent > span.rightcol > b > a
JSR 399 Java SE 24 iteration begins td#rightcontent > span.rightcol > b > a
JSR 392 Java SE 17 Maintenance Review td#rightcontent > span.rightcol > b > a
JSR 384 Java SE 11 Maintenance Review 3 td#rightcontent > span.rightcol > b > a
JSR 337 Java SE 8 Release Contents Maintenance Review 6 td#rightcontent > span.rightcol > b > a
JSR 269 Pluggable Annotation Processing Maintenance Release td#rightcontent > span.rightcol > b > a
JSR 397 Java SE 22 Final Release td#rightcontent > span.rightcol > b > a
JSR 385 Units of Measurement API 2 Maintenance Release 2 td#rightcontent > span.rightcol > b > a
JSR 398 Java SE 23 iteration begins td#rightcontent > span.rightcol > b > a
JSR 396 Java SE 21 Final Release td#rightcontent > span.rightcol > b > a
JSR 269 Pluggable Annotation Processing API Maintenance Release 7 td#rightcontent > span.rightcol > b > a
JSR 384 Java SE 11 Maintenance Release 2 td#rightcontent > span.rightcol > b > a
JSR 337 Java SE 8 Maintenance Release 5 td#rightcontent > span.rightcol > b > a
JSR 384 Java SE 11 Maintenance Review 2 td#rightcontent > span.rightcol > b > a
JSR 337 Java SE 8 Maintenance Review 5 td#rightcontent > span.rightcol > b > a
JSR 378 Portlet 3.0 Bridge for JavaServer Faces 2.2 Final Release td#rightcontent > span.rightcol > b > a
JSR 243 Java Data Objects Maintenance Release 4 td#rightcontent > span.rightcol > b > a
JSR 381 Visual Recognition Specification Final Release td#rightcontent > span.rightcol > b > a
JSR 392 Java SE 17 Final Release td#rightcontent > span.rightcol > b > a
Contact Us body > div#footer > div.footleft > a
© 2026, Oracle Corporation and/or its affiliates. Terms of Use. Privacy Policy.… body > div#footer > div.footleft2
Terms of Use body > div#footer > div.footleft2 > a
Privacy Policy body > div#footer > div.footleft2 > a
Trademarks body > div#footer > div.footleft2 > a

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
JCP Terms of Use td#leftcontent > ul#p7PMnav > div.noNav > a
Oracle Privacy Policy td#leftcontent > ul#p7PMnav > div.noNav > a
register now tbody > tr > td#centercontent > a
overview page tr > td#centercontent > p > a
2025 JCP Award winners tbody > tr > td#centercontent > a
December 2025 edition of the JCP Newsletter tbody > tr > td#centercontent > a
The agenda and recording tr > td#centercontent > p > a
Twenty-five years of the Java Community Process tr > td#centercontent > p > a
Celebrating 25 years of the JCP with JUGs around the world tr > td#centercontent > p > a
Java in Education td#centercontent > ul > li > a
message from Heather VanCura ul > li > p > a
Java Ecosystem JCP Working Group td#centercontent > ul > li > a
Java and AI Working Group td#centercontent > ul > li > a
JSR 402 tbody > tr > td > a
JSR 401 tr > td > p > a
JSR 378 tr > td > p > a
JSR 381 tr > td > p > a
JSR 393 tr > td > p > a
JSR 394 tr > td > p > a
JSR 395 tr > td > p > a
JSR 396 tr > td > p > a
JSR 397 tr > td > p > a
JSR 398 tr > td > p > a
JSR 399 tr > td > p > a
JSR 400 tr > td > p > a
JSR 401 tr > td > p > a
JSR 384 tr > td > p > a
JSR 385 tr > td > p > a
JSR 387 tr > td > p > a
JSR 392 tr > td > p > a
JSR 907 tr > td > p > a
JSR 199 tr > td > p > a
JSR 221 tr > td > p > a
JSR 269 tr > td > p > a
Terms of Use body > div#footer > div.footleft2 > a
Privacy Policy body > div#footer > div.footleft2 > a
Trademarks body > div#footer > div.footleft2 > a

These are opportunities to improve the legibility of your content.

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.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#tools > div.search > form#[object HTMLInputElement] > input.form div#tools > div.search > form#[object HTMLInputElement] > input.form
tr > td#leftcontent > form#[object HTMLInputElement] > input.form tr > td#leftcontent > form#[object HTMLInputElement] > input.form

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
JSRs by Platform JSRs by Technology JSRs by Stage JSRs by Committee List of All… tbody > tr > td#leftcontent > ul#p7PMnav

These are opportunities to improve the experience of reading tabular or list data using 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
JSRs by Platform td#leftcontent > ul#p7PMnav > li > a
JSRs by Technology td#leftcontent > ul#p7PMnav > li > a
JSRs by Stage td#leftcontent > ul#p7PMnav > li > a
JSRs by Committee td#leftcontent > ul#p7PMnav > li > a
List of All JSRs td#leftcontent > ul#p7PMnav > li > a
About JCP td#leftcontent > ul#p7PMnav > li > a.p7PMtrg
Get Involved td#leftcontent > ul#p7PMnav > li > a.p7PMtrg
Community Resources td#leftcontent > ul#p7PMnav > li > a.p7PMtrg
Community News td#leftcontent > ul#p7PMnav > li > a.p7PMtrg
FAQ td#leftcontent > ul#p7PMnav > li > a
Contact Us td#leftcontent > ul#p7PMnav > li > a
New JSRs tr > td > b > a
Public Reviews td > p > b > a
Final Releases td > p > b > a
Inside the JCP Executive Committee: Purpose, Structure, and Impact td#centercontent > ul > li > a
From Hokkaido to the World: How Hiroto Yamakawa Built a Java Community that Ins… td#centercontent > ul > li > a
Java in Education at the Dominican Republic Java User Group td#centercontent > ul > li > a
JCP's 25th Anniversary - Twenty-five years of the Java Community Process td#centercontent > ul > li > a
JCP 2 tr > td#rightcontent > span.rightcol > a
Calendar tr > td#rightcontent > span.rightcol > a
Multimedia page tr > td#rightcontent > span.rightcol > a
Submit a new JSR tr > td#rightcontent > span.rightcol > a
JCP Community Github tr > td#rightcontent > span.rightcol > a

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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-hidden="true"]` is not present on the document `<body>`
Image elements have `[alt]` attributes
Input buttons have discernible text.
Document has a `<title>` element
Links have a discernible name
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Heading elements appear in a sequentially-descending order
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
`<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 a valid value for its `[lang]` attribute
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
`<input type="image">` elements have `[alt]` text
The document does not use `<meta http-equiv="refresh">`
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
No element has a `[tabindex]` value greater than 0
`<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.
73

Best Practices

User Experience

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLDisplayed sizeActual sizeExpected size
Java Community Process div#header > div#logo > a > img
jcp.org/images/spacer.gif151 x 811 x 1151 x 81
tbody > tr > td#rightcontent > img tbody > tr > td#rightcontent > img
jcp.org/images/global/spacer.gif150 x 51 x 1150 x 5

Browser Compatibility

Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.

Why this matters

Performance issues directly impact user engagement and conversion rates.

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
Unload event listeners are deprecated and will be removed.
Uses HTTPS
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
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
91

SEO

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

Content Best Practices

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
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`

Send Feedback