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

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

Start by reproducing the slow loading and API/model stream failures on the JSON Schema website in Chrome, using the browser's Network tab to identify the 404 requests. Done means internal links load promptly and the affected API calls return valid responses instead of 404 errors.