Steps to reproduce the problem

1. Open a new incognito window
2. Open the devtools
3. Turn on 3G throttling
4. go to https://qwik-service-worker-waterfalls-repro-hxnz86qkr.vercel.app/
5. Wait until all the page and chunks have been downloaded
6. Click on "click me" button
7. Observe that the next chunks are fetched on interaction at normal speed, even though 3G throttling is turned on.

Now let's see the output when it works properly:

1. Open a new incognito window
2. Open the devtools
3. go to https://qwik-service-worker-waterfalls-repro-hxnz86qkr.vercel.app/
4. Wait until all the page and chunks have been downloaded
5. Turn on 3G throttling; if it was already turned on, turn it off and start from 1 again.
6. Click on "click me" button
7. Observe that the next chunks are fetched on interaction at 3G speed. This is how it should behave.

Problem Description

Not properly throttling on user interaction can make it seem that the application is quite fast in slow network conditions, when in reality it will have delays on user interactions. As you can see in the reproduction steps, the behavior changes when the throttling is enable before or after accessing the url.

Additional Comments

I'm a core qwik.dev team member. Because of this issue we didn't realize we had an important bug in our prefetch service-worker, affecting the performance of all apps facing that bug.

Summary

Throttling ineffective on user interaction when already turned on before accessing url

Additional Data

Category: Developer Tools
Chrome Channel: Stable
Regression: N/A