In evaluating NeoLoad I have noticed that pages with a lot of resources get recorded with resource requests seemingly randomly recorded as pages with seemingly random children resources. I.e. We have a page that has maybe a hundred or so js, css, font, and image resources, along with APIs called for configurations and data, and the user path for the page will get recorded with some of the css files and js files as pages, and under some of these pages, API calls and other resources, when everything should actually be a resource of the original page. Is the logic purely based on timing, and if so is there any way to adjust the threshold for requests remaining as resources of a page vs starting a new page?
↧