Describe the bug / Performance Issue
When landing on the page, the initial API request attempts to fetch 1,000 developers at once. On low-bandwidth or slow network connections, this massive payload causes heavy loading times, web browser lag, and frequently results in aborted requests (user aborted a request / network timeout errors).
Expected Behavior
The page should load a smaller initial batch of developer records rapidly so the user gets an immediate, responsive UI, followed by progressive background fetching or pagination as the user interacts with the app.
Proposed Solution
- Initial Batching: Fetch an optimal initial subset (e.g., ~500–600 records or smaller page chunks) upon landing for fast initial rendering and better Time-to-Interactive (TTI).
- Progressive/Lazy Fetching: Load remaining developer data in subsequent background requests or through progressive scrolling/pagination as the user stays on the site.
Impact
- Eliminates request abortion/timeout errors on low-speed internet.
- Significantly improves landing page load speeds and overall UX.
Describe the bug / Performance Issue
When landing on the page, the initial API request attempts to fetch 1,000 developers at once. On low-bandwidth or slow network connections, this massive payload causes heavy loading times, web browser lag, and frequently results in aborted requests (
user aborted a request/ network timeout errors).Expected Behavior
The page should load a smaller initial batch of developer records rapidly so the user gets an immediate, responsive UI, followed by progressive background fetching or pagination as the user interacts with the app.
Proposed Solution
Impact