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

[🐞] Qwik is slow when used first time #6879

Open
ziimakc opened this issue Sep 12, 2024 · 2 comments
Open

[🐞] Qwik is slow when used first time #6879

ziimakc opened this issue Sep 12, 2024 · 2 comments
Labels
STATUS-1: needs triage New issue which needs to be triaged TYPE: bug Something isn't working

Comments

@ziimakc
Copy link

ziimakc commented Sep 12, 2024

Which component is affected?

Qwik Runtime

Describe the bug

When you visit qwik website first time every action (button click, menu open) has a delay from 0.1-1 sec. Which makes qwik a slow website from user perspective.

Reproduction

https://qwikui.com/docs/styled/introduction/

Steps to reproduce

Open qwik-ui website anc click around on menu or any component, you will feel a delay. This will work only if you not visited it previously. You can try phone or tablet.

System Info

-

Additional Information

No response

@ziimakc ziimakc added STATUS-1: needs triage New issue which needs to be triaged TYPE: bug Something isn't working labels Sep 12, 2024
@wanjohiryan
Copy link

"Feels" qwik to me ;)

Can you share what device or devices you are using? iOS, PC, Tablet, Android... ?

Have you checked your network? That might be the issue 😅

@ziimakc
Copy link
Author

ziimakc commented Sep 26, 2024

@wanjohiryan it's android tablet, phone, windows linux pc. I have no problem with internet, it's super fast. Problem is that qwik doesn't prefetch components until you interact with them and for big components like menu it does like ~20 requests which of course will be visible slow and if you have a slow internet - it more noticeable. In my opinion it's a major flaw in qwik architecture.

What options do we have to solve this?

  • Prefetch component on hover
  • Give user ability to define if component should be prefetched (on page load, when it's in view and so on)
  • Bundle components data together so that one click on menu button will not trigger 20+ requests to load every single part of it like function separately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
STATUS-1: needs triage New issue which needs to be triaged TYPE: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants