BuidlZone-Labs/zicket-web

Unoptimized Image Assets and Missing Dynamic Import Optimization

Open

#178 opened on Jul 29, 2026

View on GitHub
 (11 comments) (0 reactions) (1 assignee)TypeScript (43 forks)auto 404
Stellar Wavedifficulty: mediumfrontendhelp wantedperformance

Repository metrics

Stars
 (4 stars)
PR merge metrics
 (PR metrics pending)

Description

Category

Performance

Priority

Medium

Description

Large PNG assets in /public/images/ and /public/assets/ are loaded directly without WebP/AVIF format conversions. Swiper JS and heavy UI components are bundled statically into initial route chunks.

Proposed Solution

  1. Convert static PNG assets to compressed WebP/AVIF images.
  2. Use Next.js dynamic() lazy loading for heavy client components (EventSlider, TipTap editor, QRCode modals).

Acceptance Criteria

  • Images optimized and served in modern formats.
  • Initial bundle chunk size reduced.
  • Lighthouse Performance score improved.

Files

  • app/page.tsx
  • app/components/EventSlider.tsx
  • public/images/

Contributor guide

Research direction
Examine the current image usage and static imports in app/page.tsx and EventSlider.tsx. Research Next.js Image component and dynamic() for lazy loading. Measure the current initial bundle size using webpack bundle analyzer or Next.js bundle analysis, and check Lighthouse performance metrics before making changes.
Tech stack
typescriptreactnextjs
Domain
frontendperformance
Issue type
Performance
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitNode.jsTypeScriptReact
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65