π 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
[]()

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
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.
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?
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 .
@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)
Ok I work on it
Hi everyone. @jagpreetrahi thanks a lot for opening this issue. Please feel free to submit a PR to improve the website performance. Thanks
hey, i wamt to work on this issue @benjagm , if it's stil open
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
Currently I am exploring official website for understand features
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
Thank you @jagpreetrahi for opening the issue, I've labeled it for hacktoberfest looking forward to have you PR : )
@jagpreetrahi any luck on this ?
Hii @DhairyaMajmudar , currently my exam are going on so I am not working on this issue. If you want to close this issue from my side then I can do this
Hii @DhairyaMajmudar , currently my exam are going on so I am not working on this issue. If you want to close this issue from my side then I can do this
No need to close the issue, let's make this open for other contributors, feel free to pick an another issue.
@DhairyaMajmudar May I work on this issue ?
@DhairyaMajmudar May I work on this issue ?
Sure, assigned the issue
@DhairyaMajmudar about the Slow Page Loading issue, I revisited the website to confirm and did not face any such problem. I have also checked network tab, there is only one issue for "404 Not Found"
I think need to fix it
@DhairyaMajmudar please help me for this issue, I am not facing any error, can you explain?
Hii @techmannih , how's going on folk , Is there any issue you are facing? , how I can help you
hi @jagpreetrahi about the Slow Page Loading issue, I revisited the website to confirm and did not face any such problem. I have also checked network tab
So , as I understand , you are saying that everything is work correctly now , and there is not page loading issue at all.
@jagpreetrahi Yes, exactly! Everything is working correctly now, and there is no page loading issues at all
@techmannih can you pls. mention the browser where you are testing the website. And also if possible once try to test in chrome browser as @jagpreetrahi stated he is using chrome browser in issue description
@DhairyaMajmudar sure, Iβm currently testing the website on Microsoft Edge, but I will also check it in Chrome as @jagpreetrahi mentioned. I appreciate your input
It's true that some 404 errors occur, here are some of the common errors
- https://json-schema.org/_next/data/vd0jjF7U0TQX91bSWa25-/slack.json?slug=slack (404)
Opening some of the drafts fail to fetch some requests, for example:
- https://json-schema.org/_next/data/vd0jjF7U0TQX91bSWa25-/draft/2019-09/draft-handrews-json-schema-02.html.json
- https://json-schema.org/_next/data/vd0jjF7U0TQX91bSWa25-/draft/2019-09/schema.json There's a .html.json that doesn't exist and a schema.json that appears to fail on most draft pages
but overall this does seem to be a real issue, with some mismatched links trying to fetch data from /_next/
The issue lies with the following URL returning a 404 error: https://json-schema.org/_next/data/vd0jjF7U0TQX91bSWa25-/slack.json?slug=slack
Root Causes:
- Next.js data fetching route doesn't exist
- HTML-based redirects instead of proper HTTP redirects
- Split infrastructure causing routing issues
- Improper caching implementation
Hi @benjagm @DhairyaMajmudar
Iβd love to work on this issue Could you please assign it to me?
Assigned the issue to you @MadhavDhatrak
This issue is again available.
Hii @benjagm , I'd like to work on, can you please assign me this issue