Enatega Admin Dashboard: Coupons Page Takes Excessive Time to Load Data

Open
#2,202 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
javascript
Domain
frontend, performance

Research direction

Start by reproducing the delay in the Admin Dashboard's Coupons page and use the browser network and performance tools to identify where loading time is spent. Trace the page's data-loading entry point and confirm the behavior with a representative coupon dataset. Done means coupon data loads within the stated 2–3 second target without leaving the page stuck.

Written by the indexing model from the issue text.

Description

Describe the bug
Description:
The Coupons page is experiencing unusually long load times when accessed. After navigating to the page, users encounter a prolonged loading state before any coupon data is displayed. This issue slows down navigation and affects the usability of the coupon management feature.

Steps to Reproduce:

Log in to the Admin Dashboard.
Navigate to the Coupons page.
Observe the time it takes for the data to load and display.
Expected Result:
Coupon data should load within 2–3 seconds for a smooth user experience.

Actual Result:
The page takes 10+ seconds to load coupon data, or may appear stuck in a loading state.

Impact:

Delays in viewing, editing, or managing coupon details.
Poor user experience, especially for admins managing multiple campaigns.
May be perceived as a system lag or failure.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

OS: [e.g. Windows]
Browser [e.g. chrome, ]
Version [e.g. Windows 11 Pro]

Labels: Enatega Multivendor Admin Dashboard, High Priority, Bug

Dominant language
JavaScript
Stars
0
Forks
0
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from raymondjames090/food-ordering-system-java-eclipse

All issues in raymondjames090/food-ordering-system-java-eclipse

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.