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

Support loading all assets #5

Open
tillkruss opened this issue Jan 4, 2022 · 3 comments
Open

Support loading all assets #5

tillkruss opened this issue Jan 4, 2022 · 3 comments
Assignees

Comments

@tillkruss
Copy link
Member

Should be an optional flag.

  • images
  • css
  • javascript
  • fonts
  • favicons
  • .svg
const assets = response.html().find('[src*=""], [href*=".js"]').toArray()
http.batch(assets);
@tillkruss tillkruss self-assigned this Jan 4, 2022
@tillkruss
Copy link
Member Author

@kevinohashi Does it make sense to fetch these as well to simulate more realistic traffic? I assume 99% of this will be cached by a CDN.

@kevinohashi
Copy link

I think so, people want to see CDN performance too. The closer to reality the load test, the better imo. Having it as a flag makes sense.

@osevan
Copy link

osevan commented Jun 18, 2024

Btw consider to include full page loading flag.
One example :

Woocommerce shop or blog have 100 additonal websites/product-sites.

Wp.js or woocommerce.js should drive all these pages sequentialy or equally with flag --full-seq or --full-eq

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants