[FEATURE] Performance + Accessibility Improvement of website

[akshatnema]

Why do we need this improvement?

With the addition of multiple components, pages and MD files, it's now important for us, to make the website efficient for all web + mobile users. Currently, the performance of the website has critically low numbers in both web and mobile view, which can impact the efficiency and user views in the website.

On the other hand, it's also important that we add the necessary accessibility labels to the website. Currently, with the addition of many new illustrations, we have not added label elements for these tags.

How will this change help?

The performance improvement will help the website render the contents more efficiently to the users and will drastically enhance lighthouse key metrics.

Screenshots

Some screenshots of lighthouse reports:

How could it be implemented/designed?

Following tasks need to be done in this issue:

• Make proper research + analysis on what needs to be fixed to improve performance in both mobile + web view.
• Propose the solution to improve the performance of website, at least 95% on each page.
• Search for the elements that require labels to improve accessibility.
• Create a workflow to analyse lighthouse reports for each page (not docs, blogs or any mdx rendered page0

🚧 Breaking changes

Yes

👀 Have you checked for similar open issues?

• I checked and didn't find a similar issue

🏢 Have you read the Contributing Guidelines?

• I have read the Contributing Guidelines

Are you willing to work on this issue?

None

[nikhilkalburgi]

I would like to be actively involved in addressing this performance issue and closely monitor the progress to ensure improvements in web vital metrics.

[lakshaydewan]

I would love to work on this issue, just give me a reply so i can start preparing the detailed proposal on what strategies will i be taking to solve the performance metrics. Would love to start working on this ASAP.

[29deepanshutyagi]

i would like to work on this issue , kindly assign me @akshatnema

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

[blazethunderstorm]

@akshatnema I would like to work on this issue

[patilpratik1905]

@akshatnema I would like to work on this issue if no one is working on it currently

[aeworxet]

Bounty Issue's service comment

Text labels: bounty/2025-Q4, bounty/advanced, bounty/coding, bounty/upgraded
First assignment to regular contributors: 2025-09-19 00:00:00 UTC+12:00
End Of Life after: 2025-10-31 23:59:59 UTC-12:00

@asyncapi/bounty_team

The Bounty Program is not a Mentorship Program. The accepted level of Bounty Program Participants is Middle/Senior.

Regular contributors should explain in meaningful words how they are going to approach the resolution process when expressing a desire to work on this Bounty Issue.