Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Client Optimization: Optimizing Assets: Smaller Chunks #1461

Open
SimoneZaza opened this issue Nov 1, 2024 · 0 comments
Open

Client Optimization: Optimizing Assets: Smaller Chunks #1461

SimoneZaza opened this issue Nov 1, 2024 · 0 comments
Labels

Comments

@SimoneZaza
Copy link
Contributor

Description

Split the assets into smaller chunks. Load them dynamically on demand (Lazy Loading).

Goal

Faster loading

Hypothesis

What is your hypothesis on the success of this Epic? Describe how success will be measured and what leading indicators the team will have to know if success has been hit.

Must have scope

  • Up-to-date frameworks: Usually newer versions are more performant and with smaller footprint.
  • Redundant frameworks: Remove the usage of redundant libraries. Properly import libraries, or use tree-shaking.

Stakeholders

Describe who needs to be kept up-to-date about this Epic, included in discussions, or updated along the way. Stakeholders can be both in Product/Engineering, as well as other teams like Customer Success who might want to keep customers updated on the Epic project.

Design

Figma file:
Comments are highly appreciated. When commenting in Figma, please also leave a note in the comments box below this issue to notify us

@SimoneZaza SimoneZaza added the Epic label Nov 1, 2024
@SimoneZaza SimoneZaza changed the title Optimizing Assets: Smaller Chunks Client Optimization: Optimizing Assets: Smaller Chunks Nov 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: New
Development

No branches or pull requests

1 participant