-
Notifications
You must be signed in to change notification settings - Fork 177
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
[Site]: improve static files performance #1203
Comments
I think we need to consider code-splitting first 🤔 |
I'm also trying to remove gsap, but in order to keep the original animation as much as possible, I may need to introduce other dependencies, so the exact bundle size needs to be analyzed further. |
Umm, I am pretty sure removing gsap isn't the only culprit that might speed up the website drastically, meaning the profit and loss is heavily unbalanced, less profit, more loss. I would almost prefer to say that if converting the animation's timing and spacing to what was originally the case is problematic, we are hurting the website, and making it look amateurish (you know, font sizes, animations, hierarchy etc. being off) . This is really important brand wise I mean to say, if we really don't want to use gsap, than either use framer or something, as the animations I see of today are very off and uneven in easing and timing. So, forcing to recreate the same animations in css, if seems problematic then why force yourself, it's not leading to any major gain anyways (performance wise, as was the thought goal I suppose) Plus we are losing some key interactions like the snap fix and show on scroll features in the middle section, which are like some things that stay in minds of users and make them return. All I am trying to say is we are losing on brand front here if this doesn't get fixed 😬 Also, why are we changing things like this stepwise, and that too on the live website ? I mean such drastic changes so quickly might confuse the user on whether the website is even working properly. Maybe @SkyeYoung you should work out everything separately first than push after review, just a suggestion. Sorry, for the long rant but this is something I really wanted to say. |
@1502shivam-singh I don't have the ability to make everything better in one commit, but our SEO, performance needs are obviously more pressing, so I choose to tweak the site as soon as possible rather than wait until all the issues are resolved before submitting changes. On matters such as removing GSAP and animations, you can see through my PR submission that my attention has clearly not been on those areas lately. I've recently been trying to cut up the original site to achieve some capabilities that were previously unattainable, and you can see those changes at #1225 #1218. Anyway, things will always get better, so let's stay patient together. |
What I meant was distributing similar type of changes in a single PR. If it seems unfeasible no worries, use your own work style.
Sure I get this, but let me rephrase what i said, my main concern is having difficulty in imitating exactly the animations with same spacing and timing. GSAP is just a medium through which I am trying to communicate that you can either use Framer or something more lightweight for your needs, if CSS animations seem painful for the task.
Really commend your work on this, few weeks back I was also thinking of something like this. Great work !
Sure, I am just trying to highlight the negative points here so you are aware of an overall design perspective, so i may seem impatient (Especially from the rant above 😅), but don't let it interfere with your work, okay. |
Current State
Resources Sample
TODO
return"assets/js/"
→ with CDNreturn"assets/css/
→ with CDNOther
Desired State
Description of the change you are proposing:
See Current State
Would you like to fix this issue?
No response
The text was updated successfully, but these errors were encountered: