🐛 Bug: Performance and API Errors on JSON Schema Website: Slow Loading and 404 API Response

[jagpreetrahi]

Describe the bug

. I wanted to bring to your attention some issues I encountered while using the JSON Schema website.

Slow Page Loading: The website takes a considerable amount of time to load, which negatively impacts the user experience.

API and Model Stream Errors: I noticed that the API and model stream are returning a "404 Not Found" error, preventing the system from successfully fetching data.

I would appreciate it if you could investigate these issues, as they are affecting the usability of the platform. Please let me know if you require any further details from my side.

Steps To Reproduce

Visit the JSON Schema Website: Open your web browser and go to the JSON Schema website.

Click on a Link and other Functionality : Click on any internal link on the page (e.g., navigation links or buttons).

Observe the Delay: Note how long it takes for the linked page or content to load. It may take an unusually long time to respond.

Check for API or Model Stream Errors: Open the browser’s developer tools (F12) and go to the "Network" tab. After clicking the link, check for failed API calls, particularly "404 Not Found" errors.

Expected Behavior

Fast Page Loading: The website should load quickly and efficiently, providing a smooth user experience without long delays.

Successful API Calls: The API and model stream should return valid responses (e.g., HTTP 200) when requested, allowing data to be fetched and displayed without errors.

Screenshots

[]()

![Screenshot (69)](https://github.com/user-attachments/assets/a06f3226-4383

-4305-971e-86c0d7783726)

Device Information [optional]

- OS:Window
- Browser: Chrome
- version:

Are you working on this issue?

Yes

Do you think this work might require an [Architectural Decision Record (ADR)]? (significant or noteworthy)

Yes

[github-actions]

Welcome to the JSON Schema Community. We are so excited you are here! Thanks a lot for reporting your first issue!! 🎉🎉 Please make sure to take a look at our contributors guide if you plan on opening a pull request.
For more details, check out the README.md file.

[iamAyushChamoli]

Hey @jagpreetrahi, about the Slow Page Loading issue, I revisited the website to confirm and did not face any such problem. Can you recheck if it was not an Internet Connectivity issue?

[jagpreetrahi]

Hii @iamAyushChamoli I hope you are doing well , I am new here , I wanna contribute here . For that I was exploring the website and got an api call issue also . Now I wanna work on any issue , so can u help me how I can start and if you are currently working on any issue , can I be a part of it .

[iamAyushChamoli]

@jagpreetrahi to start contributing you can refer to Contributing Guidlines. If you encounter an issue that you believe you can solve, you can create a pull request without @ the maintainers. Additionally, please make sure that the bugs and issues that you encounter are not a system/Internet Connectivity issue. Thanks! (PS: I'm NOT a maintainer of this repository, these are just some guidelines from one contributor to another)

[jagpreetrahi]

Ok I work on it

[benjagm]

Hi everyone. @jagpreetrahi thanks a lot for opening this issue. Please feel free to submit a PR to improve the website performance. Thanks

[29deepanshutyagi]

hey, i wamt to work on this issue @benjagm , if it's stil open

[jagpreetrahi]

Hii @29deepanshutyagi , I hope you are doing well , I just want to tell , i am working on this issue , and if u wanna be a part of this with me then i will tell u

[jagpreetrahi]

Currently I am exploring official website for understand features

[29deepanshutyagi]

Hii @29deepanshutyagi , I hope you are doing well , I just want to tell , i am working on this issue , and if u wanna be a part of this with me then i will tell u

sure