We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Should be an optional flag.
const assets = response.html().find('[src*=""], [href*=".js"]').toArray() http.batch(assets);
The text was updated successfully, but these errors were encountered:
@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.
Sorry, something went wrong.
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.
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
tillkruss
No branches or pull requests
Should be an optional flag.
The text was updated successfully, but these errors were encountered: