Memory Leak Troubleshooting in JavaScript + Laravel
Budget: $8 – $15 USD
I have a Laravel application that displays raffle tickets in a single Blade view (raffle.blade.php). The ticket range can go from 000000 up to 999999 or 00 to 99 (the range is dynamic), meaning we could have hundreds of thousands of tickets (or even more) on the page. Right now, I’m rendering all tickets at once, which causes severe performance issues: the browser (especially Chrome desktop and mobile) becomes extremely slow or freezes.
I have important front-end logic in JavaScript within the Blade template that handles:
Selecting tickets (click to select).
Marking tickets as reserved or purchased.
Removing tickets from the selection.
Searching for ticket numbers.
A “random selection” (Machine) feature.
I need to keep this existing selection logic and user flow but load tickets in smaller chunks (via pagination, infinite scroll, lazy loading, or similar). The idea is to prevent rendering all 999,999 (or more) tickets at once, while preserving the same interactive features (highlighting, click events, etc.).
What I’m looking for:
A Laravel-savvy freelancer who can refactor my code so that tickets are loaded incrementally (not all at once).
The front-end (Blade + JavaScript) should still manage the selection, coloring, and removal of tickets exactly as it does now.
Possibly implement a “Load More” button or infinite scroll to fetch subsequent batches from the server.
Ensure my existing logic (e.g., arrays of selected tickets, highlight states) remains functional when new batches are loaded.
Essentially, I need to optimize my ticket-loading approach to handle large ranges without losing the interactive features I already built.
I have important front-end logic in JavaScript within the Blade template that handles:
Selecting tickets (click to select).
Marking tickets as reserved or purchased.
Removing tickets from the selection.
Searching for ticket numbers.
A “random selection” (Machine) feature.
I need to keep this existing selection logic and user flow but load tickets in smaller chunks (via pagination, infinite scroll, lazy loading, or similar). The idea is to prevent rendering all 999,999 (or more) tickets at once, while preserving the same interactive features (highlighting, click events, etc.).
What I’m looking for:
A Laravel-savvy freelancer who can refactor my code so that tickets are loaded incrementally (not all at once).
The front-end (Blade + JavaScript) should still manage the selection, coloring, and removal of tickets exactly as it does now.
Possibly implement a “Load More” button or infinite scroll to fetch subsequent batches from the server.
Ensure my existing logic (e.g., arrays of selected tickets, highlight states) remains functional when new batches are loaded.
Essentially, I need to optimize my ticket-loading approach to handle large ranges without losing the interactive features I already built.